The client called on a Wednesday afternoon with changes to the entry canopy. The project was already in construction documents, details were coordinated, consultants had signed off, the contractor was pricing. But the client had seen something at another building and wanted to explore it.
The project architect said yes. They’d figure it out.
Three weeks later, the structural engineer’s revised fee arrived. The added scope had triggered coordination changes across multiple consultants. By the time the full cost became visible, the project budget had no room for it. The principal looked at the project architect, “Why didn’t you check with me before committing to this?”
The project architect looked back, “I thought I was supposed to manage client relationships.”
Both were right. And both were frustrated because no one had ever made clear where client accommodation ended and financial exposure began.
The Assumption Most Firms Make
Architecture firms assume that authority and accountability travel together, that the person responsible for an outcome naturally has the authority to make decisions that affect it, and vice versa.
In practice, they rarely align that cleanly.
A project manager is accountable for schedule and budget but may not have authority to approve overtime or reject scope changes. A design director has authority over design direction but isn’t accountable for whether that direction fits the fee. A principal remains accountable for profitability and client relationships regardless of who made the day-to-day decision.
This isn’t dysfunction. It’s the reality of professional practice, where technical, financial, client and team implications layer across multiple roles.
The problem emerges when firms don’t make these boundaries explicit. When people aren’t sure what they’re allowed to decide, two things happen: either no one acts, or everyone does. Both create friction.
Where the Gaps Usually Show Up
Authority gaps don’t announce themselves. They surface as patterns that feel like communication problems or judgment failures but are actually structural.
Scope changes are the most common. A client asks for something additional. Someone on the team says yes, assuming it’s minor or keeping the client happy is their job. Weeks later, the cost implications surface and no one can agree on who had authority to make that call.
Design sign-off is another. A project manager thinks design is approved and moves to documentation. A principal reviews the work later and redirects it. The team absorbs the rework, frustrated that direction wasn’t clear earlier, but no one had explicitly said at what point design was locked.
I watched a firm where the design director would step in with changes to presentation materials the project manager had already approved. The team would scramble to incorporate them, deadlines would slip, and the impact of the changes was often marginal. The issue wasn’t design judgment, it was that no one had ever clarified whether the design director’s authority extended to work the project manager had already signed off on, or whether stepping in at that point was actually overriding a decision that had already been made.
Resource allocation creates similar confusion. Can a project manager pull someone from one project to another when a deadline compresses? Or does that decision require principal approval? The answer varies by firm, sometimes by project, and often it’s never been explicitly stated.
When Authority and Accountability Don’t Match
The mismatch isn’t inherently a problem. In fact, separating them thoughtfully can create useful tension.
A design director has authority to approve a design approach. A project manager is accountable for delivering it within budget and schedule. If the design choice introduces schedule risk, the tension between those two perspectives forces a better conversation, design ambition meeting delivery reality.
The problem is when that tension is unspoken.
When a project manager raises a concern about a design decision and the design director interprets it as overstepping, or when a principal questions a budget call and the project manager feels undermined, it’s usually because the interaction between authority and accountability was never made explicit.
A principal at one firm kept saying “we’ll need to make it work” when project managers raised budget concerns about design decisions. The project managers heard this as dismissal of their accountability. The principal meant it as acknowledgment that profitability was ultimately their responsibility, not the project manager’s but because that distinction had never been named clearly, the phrase could have created resentment.
What Happens When Boundaries Aren’t Clear
Unclear authority doesn’t create dramatic failures. It creates slow erosion.
Decisions take longer because people aren’t sure whether they can make them. Escalation happens more often than it should, not because teams lack capability but because they lack confidence about where the boundaries are. Principals get pulled into more decisions, not because they want control but because no one else is certain they’re authorized to act.
Work slows. Trust thins. People start playing it safe, checking before moving forward on things they should be handling independently.
Consider a project architect who stopped making client commitments entirely after getting pulled into a tense conversation about a scope decision they thought fell within their authority. It didn’t, but no one had told them where the line was until after they’d crossed it. From that point on, they escalated everything, which created a different problem: the principal became the bottleneck for decisions that should have been resolved at the project level.
The firm didn’t gain control. It lost speed.
What Clarity Actually Requires
The firms that avoid this don’t have simpler projects or clearer roles. They’ve just made decision boundaries explicit enough that people can act with confidence.
Not through elaborate policy manuals or rigid approval hierarchies, but through shared understanding of where authority sits for the decisions that come up most often.
A project manager can approve scope adjustments up to a certain threshold or complexity level, not because it’s written in a job description, but because that boundary has been discussed, tested, and reinforced enough times that everyone knows where it is. A senior designer owns design direction within parameters that have been made visible. A principal stays involved in major client commitments and strategic decisions, but steps out of the routine calls that don’t require that level of authority.
When someone isn’t sure, they know who to ask and what criteria will guide the answer, not because every scenario is documented, but because the logic is consistent enough to be predictable.
A project team started clarifying at project kick-offs. They didn’t create a manual. They just began naming explicitly: “Here’s what decisions live at the project team level, here’s what requires principal involvement, here’s the threshold where exposure means we need to pause.” The conversation took fifteen minutes. The reduction in escalation and confusion was immediate.
What to Notice
Over the next few weeks, pay attention to where decisions in your firm stall or create tension.
Notice when someone makes a call they thought they had authority to make and later discovers they didn’t. Notice when people escalate decisions they should probably be handling themselves, not because they lack judgment but because they’re uncertain whether they’re allowed to decide.
Notice when accountability lands on someone who never had the authority to prevent the outcome; when a project manager is held responsible for budget performance but couldn’t control the design decisions that drove the cost, or when a principal absorbs financial exposure from commitments made by others without their knowledge.
Those moments don’t usually indicate bad intentions or poor judgment. More often, they reveal places where authority and accountability were never explicitly aligned and where your firm is paying the cost of that ambiguity in time, trust, and friction that didn’t need to exist.