How the best organisations keep producing leaders, generation after generation
An enterprise does not become enduring because it develops good leaders. It becomes enduring because every generation learns to inherit the enterprise, strengthen it, and prepare it for those who will follow.
A few years ago I started noticing something that didn't fit the usual leadership-development story.
Some organisations produce capable leaders decade after decade, almost as a matter of course. Others invest just as heavily — sophisticated competency models, well-funded executive programmes, careful succession charts — and still end up dependent on one or two exceptional individuals, with nothing much behind them when those individuals move on.
The instinctive explanations don't quite hold up. It isn't simply better executive education, because plenty of organisations with excellent programmes still run dry. It isn't simply culture, however much culture matters. Something else is going on — something that has less to do with how good the people are, and more to do with how the enterprise itself is built.
That's the idea this piece is about: leadership as something an organisation is architected to produce, rather than something it merely develops in the people lucky enough to be identified early. It comes in three parts. The first looks at the enterprise as the real unit of analysis. The second looks at the mechanism — what actually does the developing. The third looks inside that mechanism, at what changes a person rather than just adding to what they know.
None of this is really new. It draws on decades of research into how executives actually develop (I'll point to some of it at the end), and on a fair amount of watching organisations up close over the years. What I've tried to do here is strip it down to plain common sense — the kind you'd recognise immediately if you've ever watched one colleague transform under pressure while another, equally talented, simply got more experienced at the same thing.
The enterprise is the real unit of analysis
When organisations talk about leadership, the conversation almost always drifts toward individuals. We identify high-potential managers, define competency frameworks, commission programmes, build succession plans, argue over who's ready for the next role. All of this matters. But it rests on an assumption worth questioning: that leadership is fundamentally something individuals possess and organisations develop.
Flip that assumption around, and a more interesting question appears. Why do some enterprises keep producing capable leaders across generations — sometimes across a century or more — while others can't sustain even one? The gap can't be fully explained by talent management sophistication, because it doesn't track with it. There's something deeper: certain enterprises have built an enduring capability to keep renewing leadership as conditions change. Others stay dependent on whichever strong individuals happen to be around.
Leadership, in other words, may not simply be something an organisation develops. It may be something an organisation is architected to produce.
That distinction matters more now than it used to, because the enterprise itself has changed shape. A lot of what still governs leadership development was designed for a world where business models evolved gradually, technology diffused over years rather than months, and a manager could genuinely optimise within a fairly self-contained function or business. Complexity, in that world, was mostly a matter of scale.
Today's enterprise doesn't work that way. Markets, regulation, technology, AI, customer expectations, reputation and capital markets behave less like separate levers and more like one interconnected system — a decision in one corner ripples quickly through the rest. Competitive advantage now depends on integrating multiple capabilities at once, not perfecting any single one in isolation. If the enterprise has become this kind of living system, leadership has to change with it.
There's a promotion everyone recognises as significant: moving from managing a function to leading a business. There's a second one, quieter and arguably more consequential, that gets far less attention — the move from leading a business well to holding the whole enterprise in trust. It isn't a bigger version of the same job. Business leaders are rightly judged on growing revenue, improving productivity, delivering results within their domain. Enterprise leaders have to hold all of that and something else at the same time: the long-term health of the institution itself. Growth against resilience. Innovation against governance. Speed against risk. Present performance against future capability. These aren't problems with clean answers — they're tensions to be carried, year after year, without ever fully resolving them.
Somewhere in that shift, a leader stops thinking primarily as the representative of a business and starts thinking as a steward of an institution. Executive programmes can expose people to bigger ideas and harder problems, and that exposure genuinely helps — but exposure alone doesn't explain why some leaders make that shift and others, just as capable, never quite get there. Which suggests we may have been looking in the wrong place. The more useful question isn't what does this person need to learn — it's what has this organisation built that makes this shift possible at all.
That's where purpose, strategy, governance, organisational design, culture and continuous learning come in. Purpose gives continuity beyond any one career. Strategy determines which capabilities the enterprise will need tomorrow rather than which ones it's rewarding today. Governance shapes how authority and judgement actually get exercised. Structure determines which relationships leaders are exposed to and which tensions they're forced to reconcile. Culture teaches, silently, what good leadership looks like long before any formal programme starts.
No single one of these creates enterprise leadership on its own. Together, they create the conditions under which it becomes possible — the way roads don't create economic activity by themselves, but make many kinds of activity possible. Programmes, coaching and succession planning don't disappear in this view; they simply stop being the architecture and become expressions of it.
And this is why leadership can't stay the concern of the HR function alone. If it's genuinely an enterprise capability, its architecture runs through strategy, governance, business design, capital allocation and the daily decisions senior leaders make — every one of which either strengthens or quietly erodes the enterprise's future capacity to produce leaders. The task, then, isn't to develop better leaders one at a time. It's to build an enterprise that keeps producing them.
Assignments are the real curriculum
If leadership is an enterprise capability rather than an individual trait, the obvious next question is: how does an enterprise actually build that capability? Why do some organisations, despite modest formal development budgets, keep turning out remarkable leaders — while others with sophisticated programmes and well-funded academies don't?
Here's a possibility worth sitting with: leaders aren't primarily created by programmes. They're created by the cumulative experiences an enterprise deliberately — or accidentally — puts someone through across an entire career.
If that's true, it changes quite a lot. Leadership development stops being a sequence of classroom interventions and becomes a developmental journey stretched across years, where individual programmes are episodes within a much bigger system rather than the system itself. The real curriculum isn't in the classroom. It's distributed across assignments, decisions, relationships, failures and transitions that gradually reshape how someone understands both their business and the enterprise as a whole.
That also explains something that puzzles a lot of talent committees: why two executives with near-identical résumés — same technical strength, same qualifications, same years of experience — end up such different leaders. One accumulated experiences that steadily widened perspective and judgement. The other accumulated years of successful execution inside progressively bigger versions of essentially the same role. Experience by itself isn't developmental. It becomes developmental only when it changes how someone sees, interprets and acts in genuinely more complex situations.
Seen this way, the enterprise becomes the designer of leadership, whether it means to or not. Every meaningful assignment is a developmental intervention, not just a staffing decision. A transfer across businesses, functions or geographies exposes a future leader to different customers, different operating models, different institutional realities. Even the difficult assignments — a turnaround, an acquisition, a regulatory crisis, launching something genuinely unfamiliar — carry a different meaning once you see them this way. They're not just organisational necessities to be staffed and survived. They're where judgement gets exercised under conditions no classroom can replicate.
This also changes how “potential” itself should be understood. Most organisations invest heavily in identifying high-potential people — assessment centres, psychometrics, competency frameworks, calibration sessions — all trying to answer one deceptively simple question: who has the greatest potential for future leadership? But potential isn't sitting there waiting to be discovered, like a mineral deposit. It isn't a fixed trait you can measure once and confidently extrapolate.
Potential is revealed through development, not discovered before it.
Someone who looks entirely ordinary in a stable role may come alive the moment they're handed genuine ambiguity. Someone regarded as an outstanding performer in a predictable environment may struggle the moment scale or complexity increases. What talent reviews usually identify isn't potential itself — it's evidence that someone has responded well to the specific opportunities they've had so far. Future potential depends as much on the experiences still to come as on the qualities already on display.
That has real implications for how careers get planned. The task shifts from selecting the best people to building the richest developmental pathways — from asking who deserves the next opportunity, to asking what sequence of experiences would actually prepare someone for responsibilities they haven't yet encountered. Careers, in this frame, stop being simply upward progression through bigger roles. They become journeys through which perspective steadily widens, where the destination isn't a more senior title but a genuinely different capacity for judgement.
Which is why assignment planning deserves a far more central place in leadership strategy than it usually gets. Most organisations pour enormous energy into manpower plans and succession charts while treating actual assignment decisions as routine staffing calls. But assignments may be the single most powerful developmental lever available — they determine the problems executives wrestle with, the stakeholders they have to manage, the trade-offs they learn to carry. In effect, assignments are the curriculum.
None of this makes formal executive education less important — if anything, it becomes more valuable once it's tied to lived experience. Ideas land differently when a participant has already run into the situation that makes those ideas necessary. Coaching matters more when it accompanies an actual transition rather than existing as a stand-alone intervention.
Which brings us to the real distinction worth holding onto: succession planning asks who is ready for the next role. Leadership creation asks what experiences would make more people ready for roles the enterprise doesn't even know it will need yet. One manages continuity. The other builds capability. And once you see it that way, the responsibility clearly doesn't sit with HR alone — business leaders become architects of development simply by virtue of the assignments they hand out, and senior executives become teachers not through classroom instruction but through the judgement they model and the responsibility they're willing to entrust.
What actually changes a person
Even once you accept that experience — not programmes — creates leaders, a harder question follows. Not every experience is equally developmental. Some genuinely accelerate growth. Others just accumulate time. What is it that makes one experience transformative and another merely time served?
Organisations tend to assume development is mostly a function of exposure: give someone a bigger role, rotate them across businesses, send them to a good programme, assign a mentor, and — fingers crossed — leadership capability will show up. There's truth in that. But exposure alone explains surprisingly little. Two executives can go through the identical transformation, attend the identical programme, report to the identical leader, and come out the other side very differently. One undergoes something like a real shift. The other simply becomes more experienced without becoming fundamentally different. The difference isn't in what happened to them. It's in what happened within them.
This is where the distinction between learning and development earns its keep.
Learning enlarges what you know and can do. Development changes how you interpret situations, exercise judgement and carry responsibility.
One adds capability. The other transforms it. Early in a career, more technical knowledge and broader business understanding genuinely move the needle. Past a certain point, progress depends less on acquiring more knowledge and more on changing how complexity itself gets perceived — the capacity to hold multiple, often conflicting, realities at once without collapsing them prematurely into a simple choice. That capacity can't be handed over as information. It builds gradually, and usually only once someone's existing way of making sense of the world stops being sufficient for what they're facing.
Which means the purpose of a genuinely developmental experience isn't just to expose someone to complexity — it's to put them somewhere their existing frame no longer fully explains what's happening. An unfamiliar business, a transformation that's going badly, conflicting stakeholder demands, leading across functions without formal authority — these create a kind of productive disequilibrium. They force people to rethink assumptions that had served them perfectly well up to that point. Development doesn't start when experience piles up. It starts when the old patterns of thinking stop working and new ones have to be built.
That's also why the developmental power of an assignment has less to do with its size than with the quality of the questions it forces someone to confront. A bigger version of the same job can add responsibility without changing perspective at all. A lateral move into an unfamiliar business, or accountability for reconciling genuinely conflicting interests, can change how someone understands the whole organisation. What matters isn't stretch for its own sake. It's whether the experience actually changes how someone thinks.
Executive education fits into this differently than it's often imagined. Its real value rarely lies in transferring knowledge — it lies in giving people better ways to interpret their own experience. Good programmes don't just supply answers. They enlarge the questions a leader is capable of asking. The same logic explains why coaching and mentoring matter as much as they do: the best coach rarely solves the problem in front of someone. They change how the person understands the problem in the first place.
There's a sequence to all this. Executives first learn to lead themselves and their immediate teams. Then they learn to run functions and businesses. At some point, if the architecture and the assignments are right, they hit another transition entirely — the enterprise itself becomes the object of their leadership. Success stops being defined by the performance of their own patch and starts being measured by the strength of relationships across the whole system, the quality of institutional judgement, the capacity to sustain something well beyond their own tenure.
That last shift isn't just cognitive. It's relational. The enterprise stops being the context in which someone does their work and becomes something entrusted to their care. Decisions start getting judged not only by their immediate outcome but by what they mean for institutional trust and for the leaders who'll come after. Stewardship shows up less as a new competency to acquire and more as a different orientation toward the enterprise itself — and, tellingly, the most powerful developmental experiences often leave no obvious artefact at all. No certificate, no measurable skill uptick. Just a quiet, gradual change in how someone listens, frames a problem, and carries authority.
Bringing it together
Three questions, really, sit underneath everything above:
1. What kind of enterprise are we trying to build?
2. How does that enterprise keep creating leaders?
3. What experiences will actually shape those leaders, rather than simply keeping them busy?
An organisation that can answer all three has moved past leadership development as an HR activity. It has started treating leadership creation as one of the defining capabilities through which the enterprise keeps renewing itself — not because it develops good leaders, but because it has built something that keeps teaching each generation how to inherit the enterprise, strengthen it, and hand it on.
--------------------------------------------------------------------------------------------------------------------------
A note on where these ideas come from: this piece is written as plain common sense, but it leans on real research. The learning-versus-development distinction and the idea of “productive disequilibrium” echo Robert Kegan's work on adult development and Ronald Heifetz's writing on adaptive challenges. The case for experience — specifically assignments — as the real curriculum draws on Morgan McCall's long-running research on the “lessons of experience” and the 70:20:10 tradition it helped establish. And the underlying sense of judgement deepening with the complexity of what a role demands owes a debt to Elliott Jaques's work on levels of work and time-span of discretion — a framework I keep returning to, in this piece and elsewhere. None of that scholarship needs to be visible for the ideas to be useful day to day, but it's there if you want to go further.
