I built the Leadership Capability Stack because I was tired of watching good people get blamed for bad architecture. A leader gets sent on a course to fix a problem the course can't touch, nothing changes, and everyone concludes the leader was the problem. They weren't. The structure was. That's the whole reason this framework exists.
Here's my actual position: leadership isn't a set of skills you develop. It's a system you build. Skills sit at the top of that system — they're the last thing that matters, not the first. Most organisations start at the top, wonder why nothing sticks, then buy more of the same training and wonder again. I stopped doing that with my own clients years ago, and the Leadership Capability Stack is the diagnostic I built instead — five layers, Strategic Intent at the base up through Leadership Architecture, Decision Systems, Capability Standards, to Culture Output at the top, each one entirely dependent on the integrity of the layer beneath it.
The point isn't the taxonomy. The point is what it does to your diagnosis. When leadership breaks down — decision paralysis, cultural drift, inconsistent execution — the fault is almost never in the layer where the symptom shows up. It's lower. Usually two layers lower. The Stack exists to stop you treating symptoms and start you tracing causes, and I've watched that reframe alone save clients from years of wasted training spend.
Most organisations build leadership through workshops, executive coaching, and competency frameworks — and still wonder why performance stays inconsistent across the enterprise. I'll say the quiet part plainly: the fundamental issue isn't skill acquisition. It never was. It's structural architecture, and no amount of coaching fixes a structure that was never designed on purpose.
The Five Layers of the Leadership Capability Stack
- Strategic Intent: The foundation. What the organisation is actually trying to achieve — clear enough to guide a daily decision, stable enough to create predictability, adaptive enough to move with the market. Not a lobby poster.
- Leadership Architecture: The structural blueprint built on top of intent — how leadership roles, levels, and responsibilities are designed, and where accountability lives.
- Decision Systems: How authority, decision rights, and escalation are structured so strategic intent actually converts into action instead of stalling in ambiguity.
- Capability Standards: What good leadership looks like at each level — meaningful only when it's wired to the structure beneath it, otherwise it's a generic competency list.
- Culture Output: The top of the stack. Behaviour and culture are what the four layers beneath produce — an output you engineer indirectly, never a lever you pull directly.
What is the Leadership Capability Stack?
The Leadership Capability Stack is a five-layer model for diagnosing why leadership performance varies across an organisation. I borrowed the metaphor deliberately from how software runs: applications sit on a technology stack of interdependent layers, and a failure low in the stack takes down everything built on top of it, regardless of how well the top layer was coded. Leadership capability behaves the same way, and once you see it, you can't unsee it in every failed transformation programme you've sat through.
Leadership performance isn't developed; it's built. That distinction matters more than it sounds like it should — "developed" implies you're growing something that's already there. "Built" implies architecture, sequencing, and things that have to exist before other things can. The five layers, from the ground up:
- Strategic Intent — what the organisation is actually trying to achieve, with enough clarity to guide daily decisions.
- Leadership Architecture — how leadership roles, levels, and responsibilities are designed.
- Decision Systems — how authority, decision rights, and escalation are structured so intent becomes action.
- Capability Standards — what good leadership looks like at each level, connected to the structure above.
- Culture Output — the behaviour and culture that the layers beneath produce. The top of the stack, not the starting point.
Culture sits at the top deliberately. It is an output, not an input. You don't fix culture by talking about culture — you fix the structural layers that produce it. I've never once seen a culture initiative succeed when the layers beneath it were broken, and I've seen plenty of culture problems dissolve on their own once Strategic Intent and Decision Systems were repaired.
Why does leadership development fail without the Stack?
Leadership development fails when it targets the wrong layer. Most programmes operate only at Capability Standards — the skills layer — while the fracture sits in Strategic Intent or Decision Systems below it. I've reviewed dozens of these programmes and the pattern is nearly identical every time: beautifully designed curriculum, well-run workshops, glowing feedback scores, and zero change in actual organisational performance six months later.
Send a capable leader on a course to fix a problem that's actually caused by unclear decision rights, and nothing changes. The skill was never missing. The structure was. This is why the same leadership problems resurface after every training cycle — the intervention never reaches the layer that's actually broken. You can retrain the same cohort three years running and get the same complaints in the engagement survey each time, because the survey is measuring an output, and nobody touched the inputs.
Instead of asking "How do we develop better leaders?", the Stack forces a sharper question first: "Have we built the structural foundations that let leadership excellence emerge at all?" That reframe is the entire value of the diagnostic. It points you down the stack, toward the cause, instead of up at the symptom. It's uncomfortable, because it usually means the fix isn't a training budget line — it's a conversation with the executive team about whether strategic intent is actually clear, and most executive teams would rather buy training.
What is the foundational layer of the Stack?
Strategic Intent is the foundational layer — and the one most organisations assume is solid when it isn't. It answers a deceptively simple question: what is this organisation actually trying to achieve?
This isn't a mission statement framed in the lobby. Strategic Intent is crystallised clarity about where the organisation is heading, why that destination matters, and what success looks like when you arrive. Specific enough to guide a daily decision. Stable enough to create predictability. Adaptive enough to move with the market.
Without it, every layer above becomes unstable. Leaders can't make aligned decisions without knowing the priorities. They can't allocate resources without knowing which capabilities matter most. The result is what I call leadership drift — capable people working diligently toward individually sensible but collectively divergent goals. The most talented leaders in the world cannot overcome an architectural failure at this level. I say this to clients who are convinced their problem is a talent problem: you could hire the best leadership team on the planet and drift would still happen, because drift isn't a competence failure. It's a coordination failure, and coordination requires shared intent to coordinate around.
Strategic Intent isn't a statement you write once and frame. It's the gravitational centre that keeps all leadership activity in orbit around shared purpose.
How does Leadership Architecture sit on top of intent?
Leadership Architecture is the structural blueprint built on Strategic Intent — how leadership roles and responsibilities are designed across the organisation. Solid intent gives this layer something to align to; without it, the architecture is just an org chart.
This layer asks the structural questions. How many leadership levels exist? What's the unique value contribution at each one? Where do responsibilities overlap and create duplication? Where do gaps open up and create accountability vacuums?
Most organisations inherit their leadership architecture rather than designing it — that is the trap. They've accumulated layers across decades of growth, acquisition, and reorganisation — each one adding complexity without clarity. The Stack makes that accumulated mess visible, so it can be redesigned on purpose rather than endured by default. This is the core of leadership capability architecture — designing the structure deliberately instead of letting it form by accident. In practice, this is often the layer where I find the most expensive dysfunction: three people quietly owning the same decision, or nobody owning it at all, and everyone assuming somebody else has it covered.
How do you use the Stack to diagnose a leadership problem?
You diagnose by matching the symptom to its likely layer, then working downward until you hit the real cause. The symptom you see is rarely where the fracture is.
- Decision paralysis or chaos — usually a Decision Systems failure: unclear authority and escalation.
- Role confusion and duplication — a Leadership Architecture problem.
- Initiatives pulling in different directions — Strategic Intent isn't clear or hasn't cascaded.
- Inconsistent leadership behaviour — Capability Standards aren't connected to the structure above them.
- Cultural dysfunction — almost never a behaviour problem; it's an output of the foundational layers.
Then a rule that saves a lot of wasted money: work the stack from the bottom up. Investing in Capability Standards while Leadership Architecture is broken just builds skills the structure can't use. Fix the foundation first. Quick wins in Decision Systems can build momentum while the deeper work proceeds — but the order matters. Diagnosis before design. Design before development.
That's the discipline the Stack enforces. It stops you redecorating the top floor when the foundations have shifted — and it relates directly to the capability and capacity a leadership system can actually sustain.
The distinction I want you to take from this
If you remember one thing, remember this: leadership problems are architecture problems wearing a behaviour costume. Every time I've been called in to fix "a culture issue" or "a leadership gap," the actual work has started two or three layers below where the client pointed. That's not a coincidence and it's not a coaching trick — it's what happens when you insist on tracing a symptom to its structural source instead of medicating the symptom directly.
I'll go further than most people in this field are willing to. Coaching individual leaders without first checking the architecture around them is, more often than not, a waste of a good leader's time and the organisation's money. Not because coaching doesn't work — it does, when the structure can hold what it produces. But pour a well-coached leader back into a system with unclear decision rights and no strategic intent, and you haven't solved anything. You've just made one person briefly more self-aware inside a broken machine, and burned out that person a little faster in the process.
This is why I sequence every engagement the same way, without exception: diagnose the stack before you design any intervention, and design the intervention before you spend a penny on development. Organisations that skip straight to development get a temporary lift and a familiar relapse. Organisations that do the diagnostic work first get something durable, because they're finally building on ground that holds weight.
So when someone asks me what the Leadership Capability Stack actually is, my answer isn't the five-layer diagram — that's just the tool. My answer is the discipline behind it: stop asking people to be better, and start asking whether you've built a structure in which better is even possible. Most of the time, you haven't. That's not a leadership failure. It's an architecture failure, and architecture is fixable — you just have to be willing to look below the floor you're standing on.