What Is Vertical Development in Leadership?

What Is Vertical Development?

Vertical development is a family of theories about changes in how adults make meaning, coordinate perspectives, handle ambiguity, and understand their own place inside a larger system.

It is different from learning more facts or skills. It is also different from personality, intelligence, seniority, confidence, eloquence, or leadership worth.

A person can gain expertise without changing the structure used to interpret a problem. A person can also change how the problem is framed, which tradeoffs are visible, and how many perspectives can be held at once.

Horizontal development adds capability at the current frame

Horizontal development expands what someone knows or can do. A product manager learns pricing. An engineer learns a new language. A founder improves cash forecasting. A leader learns a better meeting practice.

These gains matter. They can produce excellent performance and prepare someone for broader work.

Vertical development asks a different question. Can the person see the assumptions behind the current frame? Can they coordinate competing systems without reducing the problem too early? Can they treat their own identity and preferred answer as parts of the situation rather than the center of it?

flowchart LR
    A["Horizontal growth"] --> B["More skills, knowledge, and practiced behavior"]
    C["Vertical growth"] --> D["A changed way of framing and coordinating complexity"]
    E["Personality"] --> F["Relatively stable patterns and tendencies"]
    G["Job performance"] --> H["Results in a specific role and context"]

The categories can interact. They should not be collapsed into one ladder.

There is no single vertical-development theory

The phrase gathers several research traditions.

Constructive-developmental theory examines how a person moves from being embedded in a way of knowing to being able to examine it. Ego-development research describes increasingly differentiated and integrated ways of understanding the self and others. Action-logic work applies developmental ideas to leadership. Integrative-complexity research examines differentiation and integration in language. Hierarchical-complexity and dynamic-skill theories model the coordination of tasks and skills.

A review in The Leadership Quarterly examined the use of constructive-developmental theory in leadership and also identified research needs. Readiness Engine's methodology cites several of these lineages as the research beneath its product.

Shared themes do not make every stage label, scoring rule, or instrument interchangeable.

The Center for Creative Leadership’s explanation of horizontal and vertical development offers a current practitioner framing: horizontal work adds knowledge and skills, while vertical work changes how a leader interprets complexity. That is useful orientation from a leadership-development provider. It is not independent validation of any particular stage model or assessment.

More complex is not always better

A wider frame can help with ambiguous, cross-boundary work. It can also become slow, abstract, or detached from action when the situation needs a clear decision.

Practical leadership depends on the fit among the person, role, task, team, authority, resources, time, and environment. A development model should not become a universal ranking of human value.

The useful question is what complexity the role actually requires. A person should not be described as not ready merely because an assessor prefers a more elaborate answer.

Readiness Engine's current site uses a climb metaphor and reports Ready Now, On the Path, or Not Yet. Its methodology also says a read should be reported as a center of gravity, range, and growth edge rather than false precision.

Those labels are company interpretations. They need evidence for the exact use.

Language can reveal structure and introduce confounds

Open-ended language contains evidence about perspective, assumptions, tradeoffs, time, and self-correction. Researchers have long coded written and spoken material for constructs such as integrative complexity.

Language also reflects fluency, culture, disability, education, professional training, interview comfort, status, topic knowledge, fatigue, code switching, and the quality of the prompt.

An assessment must show that it is reading the target construct instead of rewarding verbal polish or a familiar leadership story.

Readiness Engine says accent, eloquence, and storytelling style are excluded as scoring evidence and that verbatim excerpts anchor ratings. That is the claimed design. Independent reliability, subgroup performance, accommodations, rater agreement, and validity evidence determine whether the design works as intended.

Development over time is not guaranteed by a score

A developmental theory says change can occur. It does not guarantee that a report produces change.

Growth can depend on challenge, support, reflection, role demands, psychological safety, feedback quality, practice, and time. Repeating an assessment after six months may show a different result. That difference could reflect development, context, topic, measurement error, model change, rater change, or a better performance in the interview.

A useful development program separates measurement from intervention and later outcome. It records what changed, what practice occurred, and whether work behavior improved.

Vertical development is not personality

Personality models describe tendencies. Vertical-development models describe structure in meaning-making or complexity. A person can be introverted or extraverted at many developmental levels. A conscientious person can still struggle to coordinate perspectives. A creative person can still treat feedback as an identity threat.

Readiness Engine's current site describes a signal stack that includes Big Five personality, behavioral analytics, and developmental readiness. Keeping those layers separate is conceptually cleaner than presenting one total leadership score.

The evidence still needs to show that each layer contributes unique, decision-relevant information.

The construct and the instrument need separate trust

A research tradition can be credible while a new tool remains early. A useful vendor report can exist before the evidence supports consequential selection. A buyer should evaluate both levels.

For the construct, ask how it is defined, which theory is being used, what alternatives exist, which populations have been studied, and what developmental claim the evidence supports.

For the instrument, ask how responses are elicited, who scores them, how raters agree, how uncertainty is reported, what changes across versions, which groups were evaluated, what outcomes were studied, and whether the tool is validated for the intended use.

Readiness Engine currently says it is in an initial validation phase and is not validated for selection. That disclosure is more important than a general claim that the theory has decades of research.

Vertical development can be a useful lens for leadership growth. It should not become a diagnosis, hidden status hierarchy, or shortcut around evidence about actual work.

The [[Can Coachability Be Measured|coachability analysis]] applies this distinction to feedback and learning. [[How to Evaluate an AI Leadership Assessment|The assessment buyer guide]] explains the evidence a language-based instrument must earn.

AI assisted with research organization and drafting. Dalton Anderson remains responsible for the explainer, source boundaries, and publication decision.