The Principal Bottleneck

Every architecture practice has the same problem. It just doesn't talk about it.

Everything routes through one person.

The one who knows

The principal. The one whose taste the whole operation is built around. Every important decision — every client call that matters, every design direction, every moment where something could go wrong — it waits for them. Because they're the only one in the room who knows how things should be done.

This isn't ego. It's reality. The knowledge is real. The taste is earned. Fifteen, twenty years of looking at buildings, understanding what makes them work, developing instincts about proportion and material and light that can't be written down in a brief or a process document. That knowledge lives in one person's head. And so everything that requires it has to route through that one person.

The practice scales in headcount. It doesn't scale in judgment.

What I watched

I watched this for fifteen years from inside a studio. The principal would be in three conversations at once, briefing a technician while fielding a client call while reviewing drawings that came back wrong because the brief hadn't been clear enough. Not because anyone was incompetent. Because the knowledge that should have been in the brief was in a head, not in a system.

The bottleneck isn't the principal's fault. It's a structural problem. The tools didn't exist to hold that knowledge anywhere other than a person.

Now they do.

What changes

Not a document repository. Not a project management tool. Something that actually holds how the practice thinks — the material language, the design instincts, the way the firm approaches a residential brief versus a commercial one, the specific quality of space they always reach for. Encoded. Queryable. Available to everyone in the practice without the principal having to be in the room.

The brief goes out to a contractor and it's complete. Not because the principal had time to make it complete. Because the system knew what complete looks like for this practice.

The technician produces a render and it looks right. Not because they have the principal's taste. Because the tool they're working with holds the principal's taste and they're working from that.

The client presentation lands and it feels coherent. Not because someone spent a week making it coherent. Because coherence is already baked into every output the practice produces.

The radius expands

The bottleneck doesn't disappear. The principal still matters — more than ever, actually. Their judgment is the source material. But the radius of that judgment expands. It stops being limited to what they personally touched that week. It becomes the operating logic of the whole practice.

That's not automation. That's institutional knowledge, finally held somewhere it can be used.

Dave Mattu is the founder of Skalm — AI for architecture practices that holds your style, your voice, and your way of working.