Fix the org before you scale it

Every team I've taken over came with the same request attached: we need more people. Sometimes that's true. Usually it isn't. A team that isn't delivering at full capacity almost always has a structural reason, and headcount papers over it instead of fixing it.

So before I add anyone, I find out why. It's usually one of three things: ownership gaps, the wrong people, or too much noise. Teams I take over typically hit a higher gear inside the first quarter, not because they got bigger, but because the friction came out.

The setup most platform orgs get wrong

Platform groups drift into silos. Work gets handed across walls, ownership goes fuzzy at the seams, and everyone is busy while nothing moves. Then the discussion turns to headcount, because hiring feels like progress and restructuring feels like risk.

It's backwards. Adding people to an org with unclear ownership just gives you a bigger org with unclear ownership.

The two years I spent killing matrix management

When I joined Contentsquare's Data Engineering group, the culture was matrix management: people reported one way for their function and another way for their work, so nobody actually owned an outcome. Every decision needed two managers to agree, which is a polite way of saying decisions didn't happen. Interesting system. Looks collaborative on the org chart. Grinds delivery to a halt in practice.

I argued it was wrong, and I lost that argument for about two years. Then I won it. Matrix management stopped as a practice in the group, and teams got a single owner accountable for a single outcome. That fight is the whole reason I'm allergic to ambiguous ownership now. I didn't read it in a management book. I lived the failure mode, on the receiving end, as the one manager who wasn't even in the headquarters office.

What works

Start from trust and give people room early. Strong people get autonomy, scope, and cover. You watch how they handle ambiguity and what they do when something breaks, and you stay out of the way as long as the judgment holds.

Make ownership unambiguous. Every system has an owner who can explain its failure modes, its tradeoffs, and its dependencies. When ownership is clear, decision loops get short and most "we need a meeting" problems disappear.

Then guard the signal. Use authority to remove friction, not to show rank. Block outside noise so the team can think. Keep meetings to the three things that earn one (unblock a decision, resolve a conflict, align real cross-team work) and push everything else to writing.

Adding people to an org with unclear ownership just gives you a bigger org with unclear ownership.

I get involved when judgment goes weak or problems get left to drift. That's the deal: high autonomy when trust is earned, a much shorter leash when it isn't.

What this is not

This isn't a case against hiring. Strong teams need to grow, and one excellent lead is often worth more than two average hires. It's a case against hiring as the first move, against reaching for headcount before you've diagnosed why the people you already have can't run at full speed. Fix that first. Then, if you still need more people, you'll know exactly what for.