A client comes to the studio because of one person. They saw a house that architect designed, or a friend worked with them, or they read something the architect wrote, and what they want is that specific sensibility applied to their own project. This is true of most small practices, and it is not a weakness. It is the whole basis of the work. People don't hire a ten-person firm for its process. They hire an architect whose judgment they trust, and they want that judgment on their building, which means they want the architect.

So the practice is built, sensibly, to deliver exactly that. Every project passes through the principal's hands, because the principal is what was promised. They set the concept, they approve the drawings, they catch the thing the junior missed, they sit in the meeting that matters. The studio can have other people in it, and usually does, but they work in orbit around one person's eye. Nothing important leaves the building without that eye on it. This is not ego. It is the studio keeping its promise to the client, which was that they would get this architect, not a version of the work with the architect's name loosely attached.

And it works, until it becomes the thing holding the studio in place. Because a practice arranged so that everything runs through one person can only ever be as large as that person can personally touch. The principal is the source of the studio's value and also its ceiling, and the two are the same fact seen from different sides. Every project that makes the practice more sought after also makes the one person more of a bottleneck. The studio succeeds its way into a constraint it cannot grow past, because the thing clients are buying is the one thing that does not scale.

What makes this genuinely hard, rather than just a matter of learning to delegate, is that the two ways out both feel like giving up the thing that works. Growing means handing real work to someone else, and not the peripheral work, the actual design decisions, the judgment calls, the parts clients came for. Every one of those handed over is a small dilution of the promise. The studio gets bigger and becomes, by degrees, less the thing people were hiring. And the principal can feel it happening, can see the project that went out with somebody else's decision in it, and knows it isn't quite what they would have done. So delegation, the textbook answer, runs directly into the reason the studio exists.

The other direction is worse. Stepping back, working less, letting the practice run on its own, sounds like the reward for having built something. But a studio that is one person doesn't run on its own, it stops. There is no version of the principal stepping away that leaves the studio intact, because the studio was never a separate thing from the principal. It was them, arranged into a business. Take the person out and what remains isn't a smaller version of the practice. It's a set of unfinished projects waiting for the only person who can move them. So rest, too, feels like loss, and the principal stays in the middle of everything, because both alternatives ask them to give up the exact quality that made the studio worth building.

This is the bind, and it is worth being honest that it does not have a clean exit. The value really is the person. Their taste cannot be extracted and installed in someone else, and a studio that tried to fully systematise one architect's judgment would be automating away the thing it sells. Anyone promising to turn a taste-driven practice into a self-running machine is selling something that would hollow out the practice in the process. The principal being central is not a bug to be fixed. It is what the studio is.

But there is a difference worth seeing between the things that genuinely need the principal and the things that only ended up there because that is where everything ends up. The design judgment needs them. The concept needs them. The taste needs them, that is the whole point. What does not need them is the memory of why a decision was made on a project eighteen months ago, or the record of what was agreed with a client, or the history of how a drawing reached its current version. Those sit in the principal's head too, not because they require that specific person, but because nothing else in the studio was holding them. And so the principal ends up being the bottleneck not only on the work that is truly theirs, but on a large amount of work that is simply information nobody wrote down.

That is the part worth changing, and the only part that can be. Not the centrality of the principal's judgment, which is the studio, but the accidental centrality of everything else. When the context of the work lives somewhere other than one person's memory, the principal stops being the single point of failure for every question that isn't actually a design question. They are still the one who sets the concept and catches what the junior missed. They are no longer the one person who can say what the client agreed to in March. It doesn't resolve the bind, because the bind is real and permanent. It just stops the one person from being the bottleneck on the ninety percent of studio life that was never about their taste in the first place, so that what they carry is the work only they can do, and not the whole practice by default.