 |
| Conceptual image generated using AI under author's direction |
If design management is essential to project delivery, why is it still treated as an informal responsibility?
In my recent ArchitectureLive! article, The All-Nighter Is a Governance Failure, I argued that the recurring late night in an architectural office is rarely just a deadline problem.
It is often the visible end of something that began much earlier: an unsettled brief, a delayed appointment, an unrecorded decision, an unresolved interface, an unrealistic promise or a change whose consequences were never fully examined.
The architectural team eventually absorbs these accumulated uncertainties because the drawings become the place where everyone else’s information must agree. What appears to be a production crisis is frequently a governance failure.
But that diagnosis leads to another question.
If projects need someone to manage decisions, information, interfaces, change and design-stage readiness, why does architecture still struggle to recognise design management as a distinct professional role?
The responsibility exists even when the job title does not
Design management is already happening on almost every complex project. The problem is that it is often happening informally, partially or too late.
A project architect may maintain the consultant programme. A senior architect may chase client decisions. A BIM coordinator may identify clashes. A project manager may track deliverables. A technical lead may review compliance. A director may intervene when an issue becomes critical.
Each person is addressing part of the design-management problem, but no one may be explicitly responsible for seeing the design-delivery system as a whole.
That fragmentation matters.
When responsibility is distributed without clear ownership, gaps become difficult to see. The programme records when drawings are due but not whether the decisions required to complete them will be available. Consultant appointments identify disciplines but not always the interfaces between them. Design meetings generate discussion, but actions may not be linked to accountable owners, consequences and decision dates.
The project appears organised because it has meetings, programmes, models and reports. Yet its unresolved dependencies continue to accumulate beneath that visible administration.
Design management is not the existence of more project information. It is the disciplined conversion of that information into timely, coordinated and traceable decisions.
A design manager is not simply another name for a project manager
One reason the role remains poorly understood is that design management is frequently absorbed into adjacent job descriptions.
It is not the same as project management, although the two must work closely together. Project management typically governs the wider obligations of time, cost, procurement, contracts, stakeholders and delivery. Design management concentrates on whether the design itself is sufficiently defined, coordinated, reviewed and evidenced to move safely from one stage to the next.
It is not the same as BIM management. BIM provides a digital environment for creating, exchanging and coordinating information. Design management determines what information is required, why it is required, who must provide it, what decision it supports and whether the project is ready to rely on it.
It is not identical to the lead architect’s role. The lead architect may be responsible for design quality, architectural resolution and the integrity of the design intent. The design manager protects the conditions under which that intent can be translated across disciplines, approvals, procurement and construction.
Nor is design management simply technical coordination. Coordination is one of its central functions, but the role begins before clashes appear and continues after drawings are issued. It includes the structure of the brief, decision authority, stage deliverables, review gates, change control, interface ownership, risk escalation and the relationship between design maturity and project commitments.
The distinctions are not territorial. They are necessary because modern projects are too interconnected for critical responsibilities to remain implicit.
The role sits at the point where authority and information meet
Architecture now operates within dense networks of specialist knowledge.
A seemingly small change to a hotel room can affect the operator’s requirements, structure, fire strategy, accessibility, services, acoustics, finishes, procurement, cost and programme. A façade decision can alter waterproofing, energy performance, structural support, maintenance access and consenting evidence. A ceiling coordination issue may reveal not a drawing error but a chain of unresolved spatial and engineering decisions.
Someone must see those relationships before they become late-stage emergencies.
That is the design manager’s distinctive field of attention.
The design manager asks:
Is the brief sufficiently resolved for the stage being entered?
Are decision-makers identified, and do they understand when their decisions are required?
What information must be available before a design package can be completed?
Which interfaces carry the greatest delivery risk?
Are changes being assessed for their downstream consequences?
Has each discipline worked to a compatible level of design maturity?
Is there adequate time for coordination, checking and approval before issue?
Does the evidence support the project’s claim that the design is ready to proceed?
These are not administrative questions. They determine whether the design can survive the journey from intention to construction.
Design management should make uncertainty visible
A well-managed project is not one without uncertainty. Architecture cannot eliminate uncertainty, because design develops through iteration and projects respond to changing technical, commercial and human requirements.
The objective is to prevent uncertainty from becoming invisible.
An unresolved matter should have an owner, a required decision date and a clearly stated consequence. A change should be understood not only as an instruction but as an intervention in a connected system. A stage review should establish whether the project is ready to advance, rather than merely confirm that a scheduled date has arrived.
This is where design management differs from bureaucracy.
Bureaucracy can record that a meeting occurred. Design management asks whether the meeting produced the decisions the project needed.
Bureaucracy can list deliverables. Design management tests whether those deliverables are coordinated, sufficiently mature and suitable for their intended use.
Bureaucracy can circulate a change. Design management makes its effect on other disciplines, approvals, cost, programme and completed work visible.
The purpose is not to create more control for its own sake. It is to prevent creative and technical effort from being consumed by avoidable rework.
The profession needs a clearer job description
Many architectural employment structures still move from architect to senior architect, associate and director, with specialisation recognised mainly through design, technical or commercial leadership.
Design-management capability often sits between those categories. It may be expected from senior staff but neither explicitly defined nor adequately supported. On contractor- and client-side teams, the title is better established, although its scope can still vary widely. Within architectural practices, it is often mistaken for diary management, document control or meeting coordination.
That understates both the expertise and the authority the role requires.
A meaningful design-manager job description should include responsibility for:
design-planning and information dependencies;
brief and deliverable alignment;
consultant scopes and interfaces;
decision schedules and responsibility structures;
design reviews and stage-readiness assessments;
change-impact evaluation;
coordination and technical-risk escalation;
design-quality assurance across issue cycles;
connections between design maturity, procurement and construction; and
organisational learning from repeated delivery failures.
The role also needs sufficient authority to challenge an issue date, escalate an absent decision or identify that a design package is not ready. Accountability without authority merely creates another person who can be blamed after the event.
From an informal craft to a professional discipline
I have been developing these ideas through a wider body of work provisionally structured as a Design Manager’s Manual.
The purpose is not to reduce architecture to checklists or to suggest that every project can be controlled by a universal procedure. It is to articulate the recurring governance questions that arise across the life of a project—from the formation of the brief and appointments through design development, coordination, approvals, procurement, construction and eventual learning.
The emerging framework examines design delivery across successive project stages and treats it as a control loop: establish requirements, allocate responsibility, coordinate information, test readiness, record decisions, manage change, verify outcomes and carry lessons forward.
The manual is therefore less about prescribing one way to design and more about protecting the conditions required for good design to reach the built outcome.
Architecture already teaches design history, representation, technology, professional practice and construction. It now needs a more explicit understanding of design management: not as an inconvenience imposed after design, but as a discipline that connects design intent with collective delivery.
Better design management is not less architecture
Some resistance comes from the fear that naming this role will make architecture more managerial and less creative.
The opposite is more likely.
When architects spend their most valuable hours reconstructing decisions, locating missing information, correcting unmanaged changes or resolving interfaces that should have been addressed earlier, creativity is not being protected. It is being taxed by disorder.
Good design management does not decide what architecture must become. It ensures that the people responsible for designing it have a credible brief, coordinated inputs, visible constraints and enough time for judgement.
It also creates a fairer professional culture. Teams should not have to compensate through private sacrifice for risks that were visible at project level. If a deadline depends on unresolved decisions, inadequate resources or incomplete information, those conditions should be surfaced while leaders still have choices—not transferred silently to the people producing drawings at midnight.
Name the role before the next crisis
The design manager will not eliminate every difficult deadline. Unexpected site conditions, urgent approvals and genuine opportunities will still demand extraordinary effort.
The test is whether extraordinary effort remains extraordinary.
When late working becomes predictable, the profession should stop treating it as evidence of commitment and examine the system that made it necessary. That examination requires more than general calls for better communication. It needs a person with a defined responsibility to connect decisions, information, interfaces and design-stage readiness.
Architecture already relies on design management. It is time to stop treating it as an unnamed extra carried by whoever happens to notice the gap.
The recurring all-nighter tells us that the responsibility exists.
The next step is to recognise the discipline, define the authority and name the job.
This essay accompanies “The All-Nighter Is a Governance Failure,” published by ArchitectureLive! Read the original article here: [ARCHITECTURELIVE ARTICLE LINK].
No comments:
Post a Comment