Day (2001) established the foundational theoretical distinction between leader development, improving the capability of individual people, and leadership development, building the organizational capacity to produce leadership capability systematically and continuously. Organizations at the lowest maturity levels may invest in individual development activities, even expensive and well-designed ones, but have not developed the organizational systems, cultural conditions, or measurement infrastructure that make leadership capability a predictable organizational output rather than an outcome dependent on exceptional individual effort. This distinction has immediate practical implications: individual development investments in low-maturity organizations produce substantially smaller returns than equivalent investments in higher-maturity organizations, because the organizational context that would make individual development stick does not yet exist at lower maturity levels.
McCauley, DeRue, Yost, and Taylor (2010) articulated the development climate concept as the organizational-level analogue to individual feedback orientation: the degree to which the organizational environment supports, expects, and rewards ongoing leader development activity. Organizations with strong development climates produce higher development returns from equivalent individual development investments than those with weaker climates, because climate variables, including manager investment in development conversations, recognition of development behavior, and accountability for developing others, create conditions within which individual development investments persist and compound across time. The investment in organizational development climate is therefore not a soft cultural initiative but an economic prerequisite for the productivity of the individual development investments the organization makes within that climate.
The practical organizational significance of the individual-versus-organizational distinction is that the diagnosis of whether a leadership development problem is primarily an individual capability problem or primarily an organizational system problem determines what intervention is warranted. An organization with strong development systems and a current leadership capability gap needs individual development investment. An organization with weak development systems and high individual capability in its current leaders is one whose capability advantage will not be preserved across leadership transitions, because the systems that would replicate and extend current individual capability do not exist. Both diagnoses require investment, but in categorically different things, and the intervention for one problem will not address the other.
The five-level staged structure this framework applies to leadership development is not a metaphor borrowed loosely from software engineering; it reflects a pattern that recurs across multiple domains of organizational capability research. Paulk, Weber, Curtis, and Chrissis's (1995) original Capability Maturity Model, developed to assess software development organizations, established the core insight this framework extends: organizational capability in a complex domain develops through identifiable stages, each characterized by qualitatively different structural and cultural conditions, and organizations cannot skip stages because each stage's practices are prerequisites for the practices that define the stage above it. Cooke-Davies's (2004) subsequent application of staged maturity assessment to project management organizational capability found the same structural pattern in a substantially different domain, organizations without disciplined baseline project practices could not benefit from the more sophisticated portfolio-level practices that define higher maturity levels, regardless of how much they invested in those more sophisticated practices directly.
This cross-domain recurrence matters for leadership development specifically because it suggests the staged structure reflects something genuine about how organizational capability accumulates, not an artifact specific to software process improvement. An organization attempting to install level 4 measurement and accountability infrastructure for leadership development without first having established the level 3 systematic and consistent development processes that infrastructure is meant to measure is repeating the exact failure pattern Cooke-Davies documented in project management maturity: sophisticated capability cannot be installed directly onto an immature foundation, because the higher-level capability's actual function is to refine and hold accountable the lower-level practices, and there is nothing yet in place at the lower level for that refinement and accountability to act on.
Level 1 organizations, reactive or heroic, are those whose leadership effectiveness depends primarily on the particular individuals who happen to occupy key roles at any given time. Development is unplanned, reactive to crises, and concentrated on a small number of high-visibility individuals rather than systematically applied across the management population. Succession is informal and typically discovered to be inadequate only when a key leadership vacancy occurs. The characteristic organizational experience at level 1 is high variance in leadership quality across units, with islands of excellence in units led by exceptionally capable individuals surrounded by units led by people who have received minimal development investment and who lack the organizational support that would enable them to perform above their current individual capability.
Level 3 organizations, systematic, have established defined competency frameworks describing what good leadership looks like in their organizational context, structured development processes applied consistently across their management population rather than selectively for high-visibility individuals, formal succession planning processes with identified candidates for key roles and explicit development plans connecting those candidates to the experiences they need, and some mechanism for tracking development activity across the leadership population over time. The characteristic level 3 limitation is that development processes are designed and delivered as organizational activities rather than as genuine development experiences: competency frameworks describe what good looks like without reliably producing it, succession processes identify candidates without substantially developing their readiness, and development activities are measured by completion rather than behavioral impact.
Level 5 organizations, adaptive, update their development systems continuously based on measured outcomes, allocating investment toward modalities and programs demonstrating measurable behavioral change and away from those that do not. They have feedback loops between leadership capability measurements and development program design, allowing the system to improve its own effectiveness over time as evidence accumulates about what produces behavioral change in their specific organizational context. The characteristic feature of level 5 organizations is that leadership development is a learning system rather than a program portfolio: it is designed to improve itself based on evidence about what is and is not producing the behavioral and organizational outcomes that justify continuing development investment at the levels the organization commits to sustaining.
Charan, Drotter, and Noel's (2001) leadership pipeline framework identified a structural feature of leadership development that the maturity model incorporates directly but that deserves more direct examination: leadership development is not a single, undifferentiated capability but a series of qualitatively distinct passages, from managing self to managing others, from managing others to managing managers, and upward through the levels that culminate in enterprise leadership, each passage requiring the leader to let go of skills that made them successful at the prior level and develop genuinely different skills the new level actually requires. Organizations that treat leadership development as a single, general capability to be built through generic leadership training are missing the passage-specific nature of what Charan, Drotter, and Noel's research identified as the actual developmental challenge, and this is precisely the gap that separates level 3 organizations, which have competency frameworks and succession processes, from level 4 and 5 organizations, which have passage-specific development calibrated to what each transition actually requires.
Conger and Fulmer's (2003) research on leadership pipeline practice reinforced a related finding directly relevant to maturity assessment: organizations that identify high-potential candidates for key roles but fail to provide passage-specific developmental experience, cross-functional exposure, genuine stretch assignments with real accountability, rotation through roles that expose gaps a current role does not reveal, produce succession plans that name candidates without actually developing their readiness for the roles those candidates are named for. This is the specific failure mode the maturity framework's level 3 description identifies: succession processes that identify candidates without developing readiness are formally present but functionally incomplete, and an assessment that only checks whether succession plans exist, without examining whether the development experience behind them is passage-specific, will systematically overrate an organization's actual succession readiness.
Hollenbeck, McCall, and Silzer's (2006) critique of competency-model practice adds a further diagnostic consideration relevant to level 3 assessment specifically: many organizational competency frameworks, however well documented, describe generic leadership qualities disconnected from the specific strategic and operational context the organization actually operates in, producing frameworks that are comprehensive without being diagnostically useful for identifying what this organization's leaders specifically need to develop. A maturity assessment that finds a documented competency framework in place should still examine whether that framework reflects genuine organizational specificity or has been adapted from a generic template, since the latter satisfies the formal requirement of level 3 without providing the diagnostic foundation level 3's other practices, development planning, succession candidate evaluation, are meant to be built on.
Assessing organizational leadership capability maturity requires methods sensitive to the structural and cultural characteristics that distinguish maturity levels, rather than simply measuring the volume of development activity the organization conducts. An organization investing substantially in executive coaching and training programs while lacking the performance feedback infrastructure, development conversation norms, and succession planning discipline that characterize level 3 is at level 2, not level 3, regardless of development budget size. The diagnostic question is not what development activities exist but whether those activities are embedded in an organizational system that produces consistent development outcomes across the full leadership population.
The most diagnostically valid maturity assessment approaches combine document review of development program designs, succession processes, and competency frameworks with structured interviews probing actual development behaviors at the manager and director levels, and with analysis of development outcome data including promotion rates from internal candidates, multisource feedback patterns over time, and retention rates for high-potential employees. These methods together capture the difference between an organization that has designed effective development systems and one that actually uses those systems consistently and rigorously, a distinction that document review alone cannot reveal and that interview alone cannot reliably assess without the corroborating evidence that behavioral outcome analysis provides.
The practical utility of capability maturity assessment lies in its ability to redirect organizational development investment from activities that are visible and organizationally comfortable to the structural investments that would produce the greatest capability improvement at the organization's current maturity level. An organization at level 2 that invests in more development program content without addressing the feedback and accountability infrastructure that would sustain behavioral change from that content is investing in the wrong thing. Maturity assessment reveals what that wrong thing is and what the right investment would be instead, providing the diagnostic specificity that general development program benchmarking and satisfaction surveys cannot approach.
| From level | Primary investment needed | What this unlocks |
|---|---|---|
| L1 to L2 | Define competency framework; establish basic consistent processes | Assessment against common standard; consistency across units |
| L2 to L3 | Formalize succession; extend consistent development to full population | Reliable identification of capability gaps; succession pipeline |
| L3 to L4 | Measure outcomes; quantify pipeline; create developmental accountability | Evidence for investment decisions; predictable capability production |
| L4 to L5 | Build improvement loops; update practices from evidence | System learns from itself; returns compound over time |
The maturity framework generates specific investment sequencing recommendations for organizations at each level, reflecting the research finding that certain development infrastructure investments are prerequisites for others rather than parallel alternatives. Organizations at level 1 most need investment in the foundational infrastructure of level 2: defining what good leadership looks like in their context, establishing the minimum consistent processes for identifying and developing management talent across the organization rather than selectively, and creating the basic succession awareness that connects current development investment to future organizational needs. These investments will produce greater capability returns than individual development programs applied within a level-1 system context.
Organizations at level 2 transitioning to level 3 most need investment in the consistency and quality of developmental processes across their full management population, rather than in the sophistication of programs available to a subset of high-visibility individuals. The level 2 to level 3 transition is fundamentally a transition from selective to systematic development: from development as an exceptional resource available to identified high-potentials to development as a standard organizational process available to all managers as part of normal organizational operation. This transition requires significant cultural investment alongside structural investment, because it changes the organizational meaning of development from a reward for exceptional performance to an expectation of organizational membership.
Organizations at level 3 transitioning to level 4 most need investment in the measurement and accountability infrastructure that distinguishes managed from systematic development. Level 4 requires explicit outcome measurement, pipeline quantification that provides specific head-count and readiness estimates for key role categories, and performance management accountability for development behavior at the manager level. These investments are organizationally uncomfortable because they make the productivity of development investment visible in ways that reveal both the programs and the managers that are not producing development outcomes. Organizations whose leaders are willing to make that productivity visible and to act on what it reveals are the organizations that successfully transition from level 3 to level 4 development system maturity.
Organizations at level 4 transitioning to level 5 face a qualitatively different challenge than the transitions below: level 4 has already established measurement, so the level 5 transition is not about beginning to measure but about building the organizational discipline to act on what measurement reveals, reallocating investment away from programs and modalities the outcome data shows are not producing behavioral change, even when those programs are well-established, well-regarded, or personally championed by influential leaders. This transition is less a structural investment than a governance one: establishing genuine authority, typically vested in a development governance function with real standing, to make reallocation decisions based on outcome evidence rather than program tenure or internal politics. Organizations that reach level 4 but never make this governance investment tend to plateau there, continuously measuring outcomes without the organizational will to act on what the measurement shows.
DeRue and Myers's (2014) broader review of leadership development research raised a caution directly relevant to how maturity assessment results should be interpreted: leadership development, examined empirically across organizations, does not always progress through clean, linear stages in practice, and organizations can display characteristics of multiple maturity levels simultaneously across different functions, business units, or leadership populations, a large organization might have level 4 development discipline in its corporate function while a recently acquired business unit remains at level 1. A maturity assessment that produces a single organization-wide score risks obscuring this internal variation, treating an average across genuinely different sub-populations as if it described a single coherent state.
The practical implication is that maturity assessment is most diagnostically useful when applied at the level of the specific population or business unit whose development system is actually being evaluated, rather than assumed to generalize uniformly across a large, structurally diverse organization. An assessment that reveals level 2 characteristics in one division and level 4 characteristics in another is providing more actionable information than a single blended score would, because the investment sequencing recommendations this framework generates are themselves population-specific: what a level 2 division needs is not what a level 4 division needs, and treating the organization as a single entity for assessment purposes risks recommending level 2 foundational investment to a division that has already made it, or level 4 governance investment to a division that has not yet built the level 3 systematic practice that governance is meant to hold accountable.
The cumulative argument this monograph has developed is that leadership capability maturity is most useful when treated as a diagnostic tool for sequencing investment, not as a rating that positions an organization relative to others. An organization's maturity level score has limited value on its own; what makes the framework diagnostically powerful is its capacity to identify which specific structural or cultural investment, foundational competency definition, systematic process consistency, measurement and accountability infrastructure, or outcome-based governance, would produce the greatest capability improvement given where the organization, or the specific population within it, currently stands. Two organizations at the same nominal maturity level can have arrived there through different combinations of strength and gap, and the investment sequencing that follows from an assessment should reflect that specific combination rather than a generic prescription attached to a numeric score.
This diagnostic orientation also explains why the staged model, borrowed originally from a different domain entirely, has proven durable across the decades of maturity-model research this monograph has reviewed: staged frameworks succeed not because organizational capability literally progresses through discrete, universal stages in every context, DeRue and Myers's (2014) research is a caution against exactly that overreading, but because the stages name a genuine, recurring pattern in what kind of investment becomes possible once a prior kind of investment has actually taken hold. Used this way, capability maturity assessment functions less like a scorecard and more like a map of what an organization's next real investment should be, which is precisely the diagnostic function that distinguishes a genuinely useful organizational assessment from one that is merely descriptive of where things currently stand.