Skip to content
Writing

8 June 2026

The Agency Couldn’t, So They Called Me

Some problems are a shortage of the right judgement, not a shortage of hands. Why throwing a bigger team at a stuck build often makes it worse, not better.

Some problems don’t get solved by adding people, and adding people often makes them worse. The most expensive failures I get called into aren’t a shortage of hands — they’re a shortage of the right call, and no amount of headcount fixes a wrong direction; it just gets you to the wrong place faster and more expensively. That’s why a single senior person sometimes succeeds where a capable team stalled. Not because the team was bad. Because the problem was never the kind that more people solve, and somebody kept treating it as if it were.

I want to argue that carefully, because it sounds self-serving coming from a solo consultant, and the lazy version of it — “lone genius beats team” — is nonsense I don’t believe. Teams are how most software gets built and the right answer most of the time. But there’s a specific class of problem where throwing bodies at it is precisely the wrong instinct, and recognising that class is worth more than any amount of capacity.

The default reflex: stuck means understaffed

When a build stalls — over budget, behind schedule, quietly on fire — the reflex is almost always to add resource. More developers, a bigger team, another agency, longer hours. The reasoning feels obvious: it’s behind, so it needs more force, so add more people pushing.

That reasoning quietly assumes the problem is throughput — that the work is understood and there’s simply too much of it for the hands available. Sometimes that’s true. But the builds that actually stall rarely stall for that reason. They stall because something underneath is wrong: the architecture won’t hold what’s being asked of it, the thing being built isn’t the thing that was needed, a few decisions made badly eighteen months ago are now load-bearing and rotten. None of those are throughput problems, and every one of them gets worse when you add people, because now more hands are building on the broken foundation, faster, and there’s more work to unwind when someone finally names what’s actually wrong.

More people raises the cost of being wrong about the problem

Here’s the mechanism the add-resource reflex misses. The cost of building the wrong thing scales with how many people are building it. One person going the wrong direction is a small, recoverable mistake. Ten people going the wrong direction, coordinated, confident, and fast, is a catastrophe — more wrong code, more wrong infrastructure, more decisions cemented around the wrong assumption, more to tear out when the diagnosis finally lands.

So when a build is stuck because the problem is misunderstood, scaling the team doesn’t help you toward the solution. It accelerates you away from it. The bigger the team you point at a misdiagnosed problem, the more committed everyone becomes to the misdiagnosis, because now there’s a lot of work and a lot of people invested in it being right. That’s why some stalled builds keep getting bigger and more stuck at the same time — every attempt to fix it by adding force makes the underlying wrongness more expensive to admit. What that situation needs first isn’t more hands. It’s one person who can stop, look at the whole thing without a stake in the existing plan, and say plainly what’s actually wrong.

Why one senior person can break the logjam

This is the work that’s genuinely better done by one experienced person than a team, and it’s a specific kind: the diagnosis, the hard call, the unpopular sentence nobody inside the project can say.

A team in motion has momentum and politics. Everyone is busy, everyone has a stake in the current direction, and the person who’d have to say “we’re building the wrong thing” is usually the person who’d look worst for saying it. So it doesn’t get said, and the build keeps going. One senior person from outside has none of that. No stake in the existing plan, no momentum to protect, no career cost to naming the real problem. They can look at the architecture, the scope, and the decisions, find the actual fault, and say it — and then make the call about what to do, which is the thing that was missing the whole time. That’s not about being smarter than the team. It’s about being able to see clearly and say plainly, which is exactly what a team mid-momentum structurally can’t do for itself. The fix is usually a decision, not a sprint — and decisions don’t need headcount, they need judgement and the standing to make them.

Where the team is the right answer, and I’ll say so

I’ll concede the limit hard, because it’s the honest line and it’s also the whole shape of how I work. Plenty of problems genuinely are throughput. Once the direction is right, the architecture is sound, and the thing being built is the thing that’s needed, then the constraint really is capacity, and a team really is the answer — and one person becomes the bottleneck, not the solution. Building and running a real product over years is team work. Pretending otherwise would be its own version of misdiagnosing the problem.

So the pattern isn’t “consultant instead of team.” It’s diagnosis and the hard call first, from one senior person who can see clearly — then, once the direction’s right, the team to execute it. Get those in the wrong order and you scale a mistake. Get them in the right order and the team is building the right thing on a sound footing, which is the only time more people actually helps.

What this means for you

If something you’re building is stuck and your instinct is to add people, stop and ask the harder question first: is this actually a shortage of hands, or is something underneath wrong that more hands will only make more expensive? Be honest about which one it is, because the answer changes everything. If it’s throughput, scale up. If it’s direction, architecture, or scope, no team will fix it until someone names the real problem — and that’s a job for one person who can see it clearly and say it plainly, not a bigger push in the same direction.

That’s the shape of what I do, and it’s also where the honest handoff lives. I’m the right call when the problem is the diagnosis and the decision — when you need one senior person to find what’s actually wrong and tell you straight what to do about it. Once the direction is right and what you need is a standing team to build and run it properly over time, I’m the wrong shape, and that’s exactly what my agency, Digital Royalty, is for — the same standards with the team and the process behind them. The fact that I run it is why I can tell you honestly which one your problem actually needs.

This is one of my essays — simplicity is the senior move is the same judgement-over-machinery instinct aimed at how things get built, and the hidden cost of renting your operations is about fixing the real problem rather than the visible one. If your build is stuck and you’re not sure why, how to rescue a stalled build is the procedure, and project rescue is what hiring me for it looks like.

If something’s stalled and you want one straight read on whether it’s a hands problem or a direction problem, tell me about it.