A project manager stood in the doorway with a question about a reimbursable markup on a client’s request. It wasn’t complicated, the firm had handled similar situations dozens of times, but the answer lived in the principal’s head, not anywhere the project manager could check. So she asked. The principal paused, answered in under a minute, and went back to work.
It happened again an hour later. A different person, a different question, the same pattern. By day’s end, she’d fielded a dozen of these; each quick, each reasonable, none requiring more than a minute or two. But the minutes added up, and so did the interruptions to everything else she was supposed to be doing.
This had always been how the firm worked. At six people, it was efficient, she knew every project, every client quirk, every fee arrangement, and answering directly was faster than writing anything down. Now there were eighteen people, and the same model that once felt like good leadership had quietly become the firm’s biggest constraint.
The Misdiagnosis
Most principals in this position assume the problem is time management; protect the calendar better, delegate more deliberately, answer faster. So they try to be more efficient with the interruptions.
The interruptions keep coming anyway.
The real issue isn’t how the principal spends her time. It’s that the firm’s institutional knowledge, fee policies, markup thresholds, decision authority, how to handle a client’s scope request, still lives in one person’s head instead of anywhere the team can access independently. Every question that reaches the principal is a symptom of information that was never made portable.
At five or ten people, this isn’t a problem. It’s actually efficient, one person holding all the context and dispensing it directly is faster than any documented system would be. But the model doesn’t scale. Past a certain size, the same behavior that built the firm starts quietly working against it.
One firm sensed something was off but couldn’t name it, so they brought someone in to help diagnose the problem. Over time, the pattern became clear: the firm was operating at the project level, with principals functioning as de facto project managers instead of leading studios. Once that was visible, the firm began shifting toward a studio structure, where staff were more integrated into shared teams. Growth became more achievable, and far more consistent.
Where the Cost Actually Hides
The obvious cost is the principal’s own time, the accumulated hours spent answering questions that, in theory, should already have an answer somewhere accessible. That adds up to real money. But it’s not the most expensive part.
The deeper cost shows up as inconsistency. Without a shared reference point, every senior staff member applies their own judgment to similar situations. One project architect writes a tight, well-bounded scope of services. Another leaves it loose because the client seems easy to work with. One project manager tracks additional services diligently and raises change orders when warranted. Another lets it slide because raising it feels awkward.
None of this shows up clearly on any single project report. But across a portfolio, the pattern emerges: some projects consistently hit margin, others consistently don’t and the difference often has less to do with the project than with who happened to be managing it.
At one firm, two principals ran projects differently. One operated systematically and consistently hit strong margins. The other, working in a different market segment, consistently struggled to hit profitability targets. It would have been easy to attribute the gap to market differences alone. Looking closer, the real difference was approach. One principal had built consistent habits around scope and fee tracking; the other was relying on instinct project by project. That’s not a talent gap. It’s the absence of a shared operating logic that lets good judgment travel beyond the person who has it.
Why the Model Persists Longer Than It Should
The pull toward staying the same isn’t laziness, it’s rooted in reasonable instincts that are hard to release.
Principals are usually genuinely good at this. Fast, accurate decisions built the firm’s reputation, and there’s real satisfaction in being the person who knows. Keeping information centralized also feels like a safeguard for quality and control. The moment decisions start moving elsewhere, there’s a real period where things might go sideways, and that discomfort often outweighs the abstract cost of staying centralized.
Documenting how the firm actually operates can also feel like handing over trade secrets, not just losing time. It becomes something to do “when things slow down.” Things rarely slow down, and the cost of not building it keeps compounding quietly in the background.
What Actually Changes the Pattern
The firms that move past this don’t answer questions faster. They make the underlying knowledge available without requiring the principal to be in the room.
This usually starts small, not a polished manual, but a plain answer to the handful of questions that come up most often: how the firm handles scope changes, fee structures and markup policies, who has authority to decide what and within what boundaries. Once the most common questions have a documented answer, a meaningful share of daily interruptions simply stop arriving.
The second shift is building light checkpoints into the project process, a fee review at set milestones, a scope check before each phase begins, not bureaucracy, but a way to catch margin problems while they’re still small, rather than discovering them at closeout.
The third shift is in how delegation happens. Handing someone a task without context just relocates the uncertainty, they’ll guess or come back and ask anyway. Handing someone the boundary and the reasoning, “here’s how we typically approach this, here’s where the line sits, use your judgment inside it,” is what actually lets a decision move without the principal’s direct involvement.
None of this happens overnight. Reforming habits, verifying information, reviewing work as new standards take hold all takes real time upfront. But firms that stay with it see transitions get smoother, references get stronger, and delivery become more consistent as the new operating logic settles in.
What This Actually Protects
The firms that sustain healthy margins through growth, market shifts, and leadership transitions aren’t the ones with the most talented principals. They’re the ones that stopped depending on a single person to hold the entire operating model together.
A principal’s knowledge and instincts are real assets. But when they’re only accessible by asking directly, they become a single point of failure, one that limits how fast the firm can grow and how easily it functions if that person is out for even a week.
What to Notice
Over the next few weeks, keep a simple count of the questions that land on your desk. Notice which ones repeat; the same category, from different people, week after week.
That repetition is the signal. It’s not telling you your team needs more oversight. It’s telling you exactly where your firm’s knowledge is still trapped in one place and where building it into something the whole team can reach would return the most time.