Full Stack Leadership
Most leaders drift to where they feel comfortable.
Into the weeds, building and fixing things themselves. Or up into the strategy, removed from the reality of what delivery actually involves. Both feel like leadership. Neither works particularly well in a world where teams are smaller and more self-sufficient.
The weeds leader becomes a bottleneck. Every decision routes through them. The team learns to wait rather than act.
The ivory tower leader becomes irrelevant. They translate progress to the board without understanding what's actually happening. When things go wrong, they're the last to know.
What changes when teams get smaller
In large organisations, the layers of management create a kind of distributed load-bearing. Senior leaders can afford to stay at altitude because there are directors, managers, and leads between them and the work. The system absorbs the distance.
Smaller, more autonomous teams don't have that structure. There are fewer people, fewer layers, and more direct accountability for output. The team needs to move without constant hand-holding, but the leader still needs to maintain enough proximity to ask useful questions, spot problems early, and translate what's happening into something the rest of the organisation can act on.
Neither pure altitude nor full immersion works. You need range.
Borrowed from engineering
I've been thinking about this as full stack leadership — borrowed from the engineering concept of a full stack developer.
A full stack engineer doesn't do everything at once. They don't write frontend code all day and also manage the database and handle the infrastructure simultaneously. What they can do is move across the layers when the work needs it. They understand the whole system. They can go deep in one area when that's what's required, and pull back when it's not.
Leadership in smaller teams needs the same range.
Close enough to the work to ask the right questions. Far enough back to let people actually do it. Available without hovering. Coaching without directing. Translating progress to the board without losing the thread of what's actually happening.
The practical shape of it
The teams don't need you in the detail. They need you across the layers.
That means knowing when to go deep and when to pull back — and being honest with yourself about whether you're doing it because the work needs it, or because you're more comfortable in one mode than the other.
Most leaders who end up in the weeds are not doing it because they assessed the situation and decided that was where they were needed. They're doing it because it's familiar, it feels productive, and it's less ambiguous than sitting at a higher level with less clear feedback on whether you're adding value.
The same goes for the altitude-seekers. Strategy feels important. Frameworks feel like leadership. But if you can't describe what your team is actually working on this week, or explain why a specific decision got made the way it did, you've drifted somewhere that isn't useful.
Not a new framework
Full stack leadership isn't a new model of management. It's just what good leadership looks like when the team doesn't need rescuing.
In organisations with enough structure, average leaders can succeed because the system compensates for their gaps. In leaner organisations, the gaps show up fast.
The leaders who navigate smaller, faster-moving teams well tend to have one thing in common: they're comfortable operating across the range, and they've done the work of figuring out which mode the situation actually calls for.