An architect is trained to design the building, and design the space. We spend years perfecting that art.
And yet if I asked you if you deliberately designed your business, I can almost certainly guess that the answer is a resounding ‘no’.
- The invoice that wasn’t sent.
- The materials schedule that needs updating.
- The fee reconciliation sitting in a spreadsheet that only the principal knows how to navigate.
- The debtor who needs a follow-up call.
- The finish selection for a bathroom that has been on the to-do list for two weeks because every time it surfaces, something more urgent arrives first.
None of this is design work. All of it is being done by someone who trained for years to do design work, at a rate that reflects the value of design, because the business was never structured to put it anywhere else. And I think this is one of the greatest problems Architects face as businesspeople.
I know this pattern from inside. I practised architecture, I worked under principals who had built this exact structure, and I’ve spent the years since then working with business owners in professional disciplines who are all managing different versions of the same problem. The skill that justifies the practice’s existence is being consumed by the administration required to keep the practice running.
I like to think of business a bit like building a ship. But in Architectural businesses, the captain is below deck, and the ship is drifting with the tides.
This article is about how to delegate better as an architect: the structures that make real delegation possible, rather than the theory of why it should happen.
The Architect Who Does Everything Is Building the Wrong Thing
The architectural profession trains principals to believe that quality requires their personal involvement. The ‘guild culture’ is real and persistent: the best work carries the principal’s hand, the principal’s eye, the principal’s judgment at every stage. This is true for some things.
It’s catastrophically untrue for most of the work that consumes a principal’s week.
The principal Architect is technically excellent. The work is good. The clients are satisfied. But they’re also stretched too thin, and trying to achieve too much. Oh! To be a simple project Architect again!
No invoicing, no payment chasing, and definitely no bills!
The designer and the businessperson are different roles, and most architectural practices ask one person to be both simultaneously, without ever acknowledging the cost of the switching.
A principal who moves from a design development conversation into an invoice dispute into a consultant fee negotiation into a materials selection into a staff performance issue across the same morning is not doing any of those things particularly well.
They’re managing the cognitive load of constant context switching while trying to maintain the standard of work that the practice’s reputation depends on.
The first delegation question is not what to delegate. It’s which role you’re primarily building the ship to sail, and what that means for where your time should actually sit.
Why Architects Keep Holding Invoices They Should Never Touch
Invoicing, payment tracking, debtor follow-up, fee reconciliation, PAYG, superannuation lodgements: none of this requires a design degree. All of it requires time, attention, and administrative precision that is entirely compatible with someone who is NOT a registered architect.
And yet the majority of architectural principals in small practices are personally involved in some or all of it, often because they started doing it when the practice was a single person and never found a clean moment to hand it over.
The time cost of financial administration in a small architectural practice is rarely calculated, but I can tell you, because it’s actually one of my roles as a business coach and fractional practice manager.
Handing off just that task alone, frees up 5-7 hours of a design director’s time – time that they can spend with their juniors, with their clients, or even with a book in a quiet corner.
An hour of principal time spent chasing an overdue invoice is not an hour that costs the hourly rate of an administrator. It costs the hourly rate of the most expensive person in the practice, applied to a task that an administrator could complete at a fraction of the cost and probably better, because for the administrator this is the job rather than the interruption.
A captain who personally inspects every part of the ship is never going to leave port. Delegation is a must – you need to trust your fellow sailors a bit more. And you already know this.
The practical step is specific: list every financial administration task that has touched the principal’s time in the last month. Assign each one either to a delegated staff member, a bookkeeper, or a practice management tool that handles it automatically. Set a review date to confirm the handover is working. The principal’s remaining financial responsibility is to review the reports, not to produce them.
What Are You Actually Doing When You Choose a Tile?
Materials selections. Finishes schedules. Fixture specifications. Product research. Supplier correspondence. These tasks occupy a significant portion of most architectural principals’ working weeks, and they generate a consistent cognitive dissonance: they feel like design work because they involve design judgment, but they are largely documentation, coordination, and decision management.
Ask yourself whether the principal is adding irreplaceable value in this process or managing it out of habit, quality anxiety, or the difficulty of articulating their standards in a way someone else can follow.
Choosing the colour of the tiles matters. But it definitely doesn’t matter at your $300/hr rate. It requires a clear brief from the captain, a junior who has been trained to execute within the design intent, and a review process that catches the things that drift outside the brief before they become site instructions.
Most principals can’t delegate materials selections not because juniors are incapable but because the principal has never made their design standards explicit enough for a junior to apply them independently. The standard exists entirely in the principal’s head, arrived at through years of experience, and communicated through corrections after the fact rather than through a framework at the beginning. That is not a people problem. It is a documentation problem, and it has a solution.
This is just an example of how Architects are hogging the entire design process. If you want to have more free time, you need to decide which decisions are most important for the time you’re actually spending.
How to Delegate Better: Build a Design Framework, Then Let Go of the Drawing
This is the delegation insight that most architectural principals have never been given permission to act on: if you codify your design intent, you can hand over the drawing.
I’m talking about taking what is currently ‘instinct’, and actually taking some time to turn it into ‘objective design’.
A design framework is not a style guide and not a brand document. It is a working record of the principles, preferences, constraints, and non-negotiables that define how this practice approaches its projects.
The material palette that the practice returns to and why. The spatial relationships that the principal considers resolved and those that always require their specific judgment. The quality thresholds for documentation, for specification, for consultant coordination. The things that are always done, the things that are never done, and the things that depend on context.
A ship’s drawings are the delegation tool. A principal who has documented their design intent gives the crew a set of plans to build from. Without the drawings, every junior is guessing at the design. The guesses are sometimes right and sometimes wrong, and the principal ends up below deck correcting work that could have been right from the beginning if the brief had been clear.
And you need to use juniors – they’re the only ones who can cost-effectively do the work.
The framework takes time to build the first time. It is also, unlike most administrative investments, directly productive; the process of making design standards explicit forces a clarity of thinking that improves the principal’s own work as well as making it delegable. It enriches your own design as you go.
Once the framework exists, juniors can take real ownership of design tasks within it. Not unsupervised production, but creative ownership within a defined intent. That is a different kind of contribution than redrawing the principal’s sketch, and it produces a different kind of development in the junior architect.
The principal’s role shifts from producing the work to setting the intent and reviewing the result. That is the correct use of a principal’s design expertise, and it is the only version of an architectural practice that the principal can sustainably run.
How to Delegate Better: Writing the Brief That Actually Works
Any architect knows that the construction documentation phase is where most projects succeed or fail. The design is the exciting part. The documentation is where the elegant sketch either becomes a building or becomes a series of variations.
Delegation in an architectural practice works identically.
Deciding to hand something over is the concept sketch. Writing the brief is the documentation phase, and it’s where most architectural delegation fails. Have you ever considered documenting your delegation?
A delegation brief for an architectural task contains specific information. The design intent: what this element is trying to achieve, spatially and experientially, and what the client has expressed about it. The constraints: the structural engineer’s latest coordination drawing, the council requirement, the budget threshold, the existing conditions that have to be respected. The quality standard: what done looks like, what review stage it will be checked at, and what the escalation path is if something can’t be resolved within the brief. The format and date required.
That’s right – we’re talking about operations manuals. But not pretty ones that sit on the shelf gathering dust. Delegation starts with highly actionable and sequenced delegation, in the form of a written brief.
The Delegation Test for Architectural Practices
If the principal took two full weeks off during the documentation stage of a live project, what would stall?
Not what would be imperfect, or what would require a decision when they returned.
What would actually stop?
Where would the team hit a wall they couldn’t get past?
That list is the delegation to-do list. Each item on it represents either a task that hasn’t been properly briefed and handed over, a decision-making framework that hasn’t been documented, or a relationship that has never been given to anyone else to manage. Each one is a place where the ship needs the captain at the wheel and shouldn’t.
The delegation test isn’t run once. It’s run progressively, with each cycle revealing the next constraint, until the practice reaches the point where the principal’s absence for two weeks produces a temporary absence of their specific design judgment. That is the only thing that should require them to be present.
A seaworthy vessel doesn’t need the captain at the wheel every hour. The crew knows the heading. The charts are on the table. The watch system runs without instruction. That isn’t luck, and it isn’t a particularly large crew. It’s what the ship was built to do, because someone thought carefully about how to build it that way before the voyage began.
If you’re an architectural principal who recognises this pattern and would like a structured view of where your practice is consuming time it shouldn’t need from you, a 15-minute discovery call is the right first conversation. No commitment, no proposal; just a direct conversation about whether the work I do fits what you’re dealing with.
