This is Part 2 of a series. Read Part 1 — Why Architects Aren’t Seeing Pay Rises — And What Actually Needs to Change — here.
The first part of this piece laid out a difficult truth: the reason architects aren't seeing pay rises isn't primarily due to the market, fees, or difficult clients. It's that most practices are running a delivery model that quietly bleeds time and money on every single project — and then trying to solve a margin problem by winning more work.
If you're a firm owner or work in AECO/the built environment, I know you will recognise it immediately. The harder question is what comes next.
This blog is our answer to that.
Not with a list of software to buy or a framework with a catchy name, but with a direct look at what actually changes when firms fix this — and where to start.
Most practices can't tell you, with any precision, where their time goes. They have fee projections and invoice records. They have a rough sense that certain project types or certain clients are "hard work." But the actual data — which stages lose time, which tasks create the most rework, which projects consistently underperform — tends to live in directors' heads rather than in any system.
You can't fix what you can't see.
The first step isn't automation, AI, or new software. It's getting visible. That means tracking time in enough detail to understand where it's actually going. Not to police people, but to identify the structural losses: the rework loops, the coordination gaps, the stages that consistently run over because something upstream wasn't resolved when it should have been.
This doesn't have to be onerous. A simple, consistently applied time-recording discipline — even for a single month — will usually surface the biggest problems quickly. Most practices discover the same things: a disproportionate amount of time is lost in late-stage rework caused by issues that were present at the start of the project; coordination between disciplines is creating far more back-and-forth than anyone had formally acknowledged; and a handful of tasks that recur on every project have never been standardised, so they're reinvented each time.
The data is almost always clarifying. And it removes the need for uncomfortable gut-feel conversations about performance, because the evidence speaks for itself.