The leadership meeting was scheduled for an hour. Ninety minutes in, they were still discussing the same staffing question that had come up two weeks earlier. Who should lead the new civic project? The conversation circled through the same concerns, capacity, client relationships, development opportunities, without landing anywhere.
Someone suggested tabling it until next week when they’d have better information. Everyone agreed, relieved to move on.
The following Tuesday, the question was back on the agenda. Same concerns, slightly different framing, no new information. Another hour disappeared into discussion that felt productive but produced nothing.
If you’re a principal in an architecture firm, this pattern is probably familiar. Not the specific question, but the shape of it; important decisions that require endless conversation, alignment that never quite solidifies, meetings that feel necessary but don’t actually resolve anything.
At some point, alignment stopped being something your firm produces and became something you endlessly pursue.
The Misdiagnosis
Most firms experiencing this assume the problem is communication. People aren’t talking enough, or they’re talking past each other, or the right voices aren’t in the room. So they add more meetings, expand who’s included, create more opportunities for input.
The meetings multiply. The conversations continue. And nothing fundamentally changes.
The real problem isn’t communication. It’s that firms are using meetings to compensate for structural clarity that doesn’t exist.
When decision authority isn’t explicit, meetings fill the gap. When information doesn’t flow systematically, meetings become the delivery mechanism. When accountability isn’t clear, meetings turn into checkpoints to confirm that work is actually happening.
The meeting isn’t the problem. It’s the symptom of architecture that was never built.
Where Architecture Firms Get This Wrong
Architecture is a collaborative profession. Coordination is in the DNA. But many firms quietly confuse the process of alignment with the outcome of alignment.
Leadership teams talk extensively. Priorities get discussed. Challenges are surfaced. Perspectives are shared. And because the conversation feels engaged and thoughtful, it creates the impression that alignment is happening.
But conversation without structure doesn’t create alignment. It creates the need for more conversation.
There are firms where principals spend fifteen hours a week in “alignment meetings,” leadership team check-ins, project reviews, strategic discussions, and coordination sessions. They leave those meetings feeling like they’re staying connected to the work. What they don’t see is that the rest of the firm is waiting for clarity that never quite arrives because the meeting ended without actually deciding anything.
The firm mistakes the meeting for the mechanism.
The Hidden Cost
The obvious cost is time. Six people in a two-hour meeting at billing rates of $150/hour is $1,800. Weekly, that’s nearly $100,000 annually. Multiply across recurring meetings and the number becomes difficult to ignore.
But the more damaging costs are invisible.
Decisions stall while consensus is sought. Teams wait for direction instead of moving forward. Principals become bottlenecks without realizing it, not because they’re controlling, but because nothing can move until they’ve been in the room to discuss it.
Design momentum erodes. Opportunities pass while they’re still being discussed. Talented people grow frustrated not because they lack autonomy, but because exercising it requires navigating an unclear maze of who needs to be consulted about what.
Over time, leaders feel busy but ineffective. Teams feel involved but uncertain. And alignment becomes something everyone works at constantly instead of something the firm naturally produces.
What’s Actually Missing
Firms that don’t drown in alignment meetings aren’t better at communicating. They’ve built structure that makes most of those meetings unnecessary.
Not through elaborate systems or rigid hierarchies, but through clarity about three things: who decides what, how information moves, and what accountability actually means.
When decision authority is explicit, meetings stop being negotiation sessions. A project manager knows they can approve scope adjustments up to a certain threshold without convening a discussion. A design lead knows where their authority over design direction ends and where principal involvement begins. Business development knows what they can commit to in pursuit conversations.
The boundaries aren’t perfect for every scenario, but they’re clear enough that routine decisions don’t require meetings to happen.
When information flows systematically, meetings stop being status updates. When information like project health, financial performance, staffing capacity, pursuit pipeline, is visible without explanation, meetings can focus on decisions rather than reporting.
Many firms use meetings as their primary information delivery system. Someone verbally updates the group on project status. Someone else reports on business development activity. Twenty minutes disappears into information transfer that could have happened asynchronously.
The firms that avoid this don’t have more sophisticated tools. They’ve just made basic information, what’s the project status, where are we on budget, who’s available, what’s in the pipeline, accessible without requiring a meeting to surface it.
When accountability is structural, meetings stop being check-ins. Many principals have fallen into the pattern of using meetings to verify that work is progressing. Not because they distrust the team, but because without systematic visibility, the meeting becomes the only way to know.
This creates a cycle. Leaders feel they need to check. Teams interpret checking as micromanagement or lack of trust. But the real issue isn’t trust, it’s that accountability was never made concrete enough to be visible without asking.
A firm I knew had weekly scheduling meetings that gradually absorbed project review discussions. Principals started using the time to verbally confirm that projects were on track, not because they distrusted the team, but because there was no other systematic way to know. The meetings stretched beyond their scheduled time, but felt necessary.
Once they separated scheduling from project review and established simple reporting rhythms (project managers updated a shared dashboard weekly, principals reviewed asynchronously, meetings happened only when decisions were needed) the pattern changed. Scheduling meetings returned to their original timeframe. Project reviews dropped from weekly to monthly.
The accountability didn’t decrease. The surveillance did.
Why This Pattern Persists
Meeting-heavy alignment rarely happens by choice. It emerges from reasonable concerns that never get resolved structurally.
On high-stakes projects, leaders are cautious about miscommunication and talking feels safer than deciding. Later they discover that everyone understood something differently.
Leaders are skeptical of systems due to past failures with tools or reporting. The traditional face-to-face confirmation feels more reliable than trusting information that might be outdated or incomplete.
There’s also a belief, in some firms, that good collaboration means bringing more people into the room. It sounds right, but decisions that need speed end up getting consensus instead.
I watched a firm try to increase buy-in on strategic direction by expanding who participated in planning discussions. The intent was good; more voices, more ownership. What followed wasn’t clarity but diffusion. Too many perspectives, too little shared context, and strategic decisions that should have taken weeks stretched into months. The firm eventually narrowed the group again, not because they valued input less, but because they’d learned that alignment doesn’t scale through addition, it scales through structure.
What to Notice
Over the next few weeks, pay attention to which meetings in your firm exist primarily to create alignment.
Not the meetings where decisions get made or problems get solved, but the ones that exist because people need to “get aligned” or “stay coordinated” or “make sure everyone’s on the same page.”
Notice what those meetings are actually doing. Are they compensating for unclear decision authority? Are they serving as an information delivery system because systematic visibility doesn’t exist? Are they functioning as accountability check-ins because leaders don’t have another way to know work is progressing?
Those meetings aren’t the problem. They’re revealing where your firm is using conversation to compensate for structure that was never built and how much leadership capacity is disappearing into gaps that clarity could close.