The Hiring Problem

When a studio decides it's time to grow, the first hire is almost always another architect. A junior, usually. Sometimes someone mid-level if the budget allows. The decision feels natural, because more work coming in means more design capacity is needed, and design capacity means architects. The mental arithmetic happens quickly and the search begins, and within a few months the studio has added a person and the work continues.

What's less often noticed is what didn't change. The principal is still answering every operational question. Still scheduling meetings. Still chasing payments, signing off attendance, sending the project status updates the team can't yet send themselves. The new architect is busy, the projects are getting done, and the principal is just as buried as before, sometimes more so, because now there's another person whose work needs to be coordinated. The bottleneck moved, but not in the direction anyone expected.

This is the hiring problem, and it sits underneath almost every growing studio. The pressure to grow shows up as a need for more hands. The hands that get hired are designers. The work that needed help wasn't only design.

Part of what's happening is that hiring is rarely a structural decision. It's a response to a feeling. The studio is overwhelmed, the inbox is full, the timeline is tight, and the principal looks at the next project on the calendar and thinks, we need another person to handle that. The mental image is of someone sitting at a desk doing design work, because that's what the studio is, a place where design gets done. So the hire that gets made is the hire that matches the mental image. The other kinds of work, the operational layer that has been quietly growing alongside the design work, doesn't trigger the same instinct to staff up, because it doesn't feel like the practice. It feels like overhead.

This is the part most architects haven't quite faced. Beyond a certain size, a studio is not only a design practice. It is also a small business that pays salaries, signs contracts, manages cash, tracks deliverables, handles clients, files compliance, and supports a team of people whose work needs structure. The design is what the principal entered the profession to do. The rest is what arrived when they opened a studio. Most principals carry the second part personally, year after year, because they have not yet thought of it as a separate set of work that someone else could be doing. So when growth happens, the new hire reinforces the design side and leaves the other side exactly where it was, on the principal's plate.

The honest version of this gets harder, not easier, when a principal does see it. Because the natural next thought, "I need to hire someone to handle the operations," runs into a real problem. Good operational people are not cheap, and in many cases they cost more than the junior architects the studio was originally planning to hire. They also do not stay long in small studios if the role isn't taken seriously, if their work is treated as administrative support rather than as the operational backbone of a growing practice. A small studio looking at the salary of a competent operations hire often does the math and decides the cost outweighs the benefit, and so the principal continues to do the work, and the studio either stays where it is or grows into a kind of low-grade chaos that nobody quite called.

There is no clean answer to this. Some studios genuinely should stay small, and that is a legitimate choice, especially when the operational load can still be carried by one person without it costing them their life. Others should grow, and growing well means making peace with the fact that operational hires are real hires, with real salaries, that change what the studio is. A practice that adds an operations person isn't the same practice with one more chair filled. It's a practice that has admitted, quietly, that running the studio is its own kind of work, deserving of a person whose only job is to do it.

What's worth resisting is the version of growth where another architect is hired, the work piles up, and the principal carries on the way they always did, hoping the additional design capacity will absorb the operational load. It rarely does. The design gets done faster. The operational load grows in proportion, because more projects means more clients, more invoices, more deliverables, more people to coordinate. And the principal who hoped to free themselves through hiring finds they have hired their way into a slightly larger version of the same situation.

The studios that have come through this well usually did one of two things. Some hired operations early, when the cost felt high but the studio was small enough that the new person could shape how things worked from the start. Others stayed deliberately small, kept their headcount tight, and built systems that allowed the principal to carry the operational load without it consuming them. Both are legitimate. Both require the principal to have looked at the practice honestly and decided what they actually wanted it to be.

This is what we think about at Projectsmate. Some of the operational work that has historically required a person can now sit inside a system that does it without one. That doesn't replace the operational hire when one is needed, but it changes the math, especially for small studios that have been carrying everything on the principal's back because the alternative felt out of reach. The hiring problem doesn't go away. It just becomes a more honest question, asked at the right size, with a clearer view of what's actually getting hired and what's actually being asked to do.