Manager Development Spectrum

Activate when: a promoted manager is failing without clear cause; someone says 'leadership training isn't working'; a leader asks 'why can't I get to the next level'; an org wonders why its best performers plateau after promotion; a coach needs to match development intervention to a specific individual. Do NOT activate when: the issue is a skill gap (new manager needs how-to training, not stage diagnosis); the timeline is weeks (stage development takes months to years).

Overview

Most leadership programs target skill acquisition. They work for Achiever-stage leaders and are ineffective above it — not a design failure, a category error. Stage development requires transforming the interpretive logic itself, not adding capabilities within it. Rooke & Torbert's longitudinal research (2005, HBR, n=4,500) identified seven sequential Action Logics. The framework's key claim: developmental mechanisms are stage-specific — what moves an Expert toward Achiever will not move an Achiever toward Individualist.

Cross-skill composition: Use AFTER [metacognition] — accurate stage ID requires observing your own interpretive patterns from the outside. Use BEFORE or alongside [feedback-loops] — each stage's developmental move requires specific feedback structures. Use INSTEAD OF [okr-goal-setting] when "leadership isn't growing despite clear goals."

When to Use

• A high-performing manager was promoted and is now failing without clear cause
• Leadership development programs run multiple cohorts with good ratings but no observable behavioral change
• A leader is "brilliant but difficult" or "great at execution but can't develop others"
• A coach or HR leader needs to match developmental intervention to actual stage, not job title
• A leader feels plateaued — can do the job well but senses the next level requires something unnameable

When NOT to use: skill deficit (not stage mismatch); no psychological safety for honest self-assessment; timeline is weeks; goal is performance rating not development; as selection criterion without expert interpretation.

Coaching Novices (Adaptive Front Door)

• Engine mode: user has a concrete case → run The Process directly.
• Coach mode: user is unfamiliar or has no concrete case → guide step by step.

In Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.

1. "This framework maps internal logics leaders operate from — not skills, but the lens used to interpret what's happening. Each stage has a characteristic strength and blind spot. The jump requires a specific experience that exposes the current logic's limits."
2. Check fit: "Does your response sound like 'I need to win,' 'I need to be right,' 'I need to hit the target,' or 'I need to question why I framed this as a conflict'? Each is a different logic."
3. "Walk me through a situation where your leadership approach clearly didn't work — not a skill gap, but where your way of understanding the situation itself turned out to be wrong." > [WAIT — do not advance until user responds]
4. Name current stage from behavioral evidence. Then: "The move from [current stage] to the next is about noticing a blind spot you didn't know was there. Which of these feels uncomfortably close to home?" > [WAIT — do not advance until user responds]
5. "If you operated from [next stage] logic in [their specific role], what would become possible? What problems would you be able to see that are currently invisible?" > [WAIT — do not advance until user responds]

The Process

Output: Action Logic Stage Profile + Blindspot Statement + Developmental Move Plan

Stop rule: If self-reported stage and behavioral evidence diverge by >1 stage, stop and address assessment conditions first.

1. Gather behavioral evidence from responses to: (a) challenge to authority, (b) public failure, (c) expertise questioned by someone less experienced. See stage table in the Method in Action file for behavioral indicators per stage.
2. Name the stage-characteristic blindspot — it must feel slightly uncomfortable to the subject, not theoretical. (Opportunist: trust is long-run asset. Diplomat: harmony over truth. Expert: right answer is context-dependent. Achiever: hitting goals may be hitting the wrong goals. Individualist: collective action gap. Strategist: time for others to catch up.)
3. Select the stage-specific developmental move — must be concrete and schedulable. Expert → Achiever: outcome ownership where expertise alone cannot succeed. Achiever → Individualist: projects that succeed by metric but fail by meaning. Individualist → Strategist: personal development as leadership method applied to own org.
4. Design the feedback structure — must be illegible to the current stage's dismissal reflex. Experts dismiss non-experts; Achievers dismiss non-results-linked feedback.
5. Set a 90-day behavioral reassessment — look for new responses to challenge, new blind spots visible, previous-stage behaviors becoming optional. No change at 90 days = wrong mechanism, return to Step 3.

Output Template

text

Subject / Context: [name or role, org type, tenure] | Assessment date: [date]
Evidence basis: [behavioral observations / interview / 360 — be specific]

Current Action Logic: [stage name]
Evidence: [3 specific behavioral observations] | Confidence: [High / Medium]

Stage-Characteristic Blindspot: [1–2 sentences specific to this person's role — must sting slightly]

Developmental Move:
  Target stage: [next stage] | Mechanism: [1 concrete, schedulable action]
  Feedback source: [specific person or structure]
  Success at 90 days: [observable behavioral change, not attitude change]

What This Framework Does NOT Address: [skill gaps, motivational issues, performance problems]

→ Method in Action: Abraham Lincoln's Trajectory from Opportunist/Diplomat to Strategist (1834–1865)

Action Logic Domain Packs

• Founder / startup: Watch for Expert → Achiever mismatch — technical founders who mistake expertise for leadership. Series B often forces Achiever → Individualist involuntarily; frequently misdiagnosed as a communication style problem.
• Large org / mid-to-senior manager: Achiever dominates at VP/SVP. Individualist transition blocked by reward structures that punish visible assumption-questioning. Requires Strategist-stage sponsor or sanctioned assumption-questioning environments.
• Professional services / knowledge workers: Expert-stage entrenchment is the dominant blocker. Move to Achiever requires exposure where client outcomes — not expert correctness — is the success metric.

Applying It Well

• Behavioral evidence only. Self-report, job title, and 360 "presence" ratings are unreliable. Observe responses to challenge — especially public failure and challenges from below.
• Stage is not rank. An Alchemist in a junior role has higher developmental stage than an Opportunist CEO.
• The Individualist transition is most painful and most misread. Individualists questioning org goals look like "not a team player." Organizations that fire Individualists lose their most likely future Strategists.
• Time compression is not possible. A three-day retreat will not move a stage. Design developmental environments, not just individual diagnoses.

→ Primary sources: references/sources.md

Common Rationalizations

[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.

Fake move	Reality
[D] "I sent them to a leadership program, so they're being developed."	Programs teaching Achiever skills to Achiever-stage managers produce better Achievers. Stage development requires assumption-exposure — which most programs avoid.
[D] "They're self-aware, so they must be at Individualist or above."	Self-awareness is a trait, not a stage. Achievers can be highly self-aware about performance while unexamined on whether their goals are the right goals.
[D] "They always talk about systems, so they're at Strategist."	Talking about systems is Expert-stage using Strategist vocabulary. Strategist stage means redesigning systems the leader created and benefits from.
[D] "We promoted our best performers, so we have strong leadership."	Best performers at IC/manager level are typically Expert or Achiever. Promotion without stage assessment is the most common organizational leadership failure mode.
[D] "We got them an executive coach, so that covers development."	Most executive coaches provide Achiever-skill refinement. A coach whose mandate surfaces goal assumptions — and is undismissable — provides an actual stage mechanism.
→ Add [O] entries here after each real use — paste the actual failure pattern	What went wrong and why

Red Flags

• Self-reported stage 2+ levels above behavioral evidence — low-safety conditions or Diplomat compliance
• Developmental move "in progress" 12+ months with no observable change — mechanism is wrong, not timeline
• Org uses stage labels as performance ratings — immediately collapses diagnostic value
• Assessor has not examined their own Action Logic — Expert-stage assessors misidentify Achievers as Experts
• Developmental move selected is comfortable — true moves produce resistance; comfort = wrong mechanism
• Presenting symptom framed as personality — blocks stage diagnosis, leads to style coaching

Verification

• Behavioral evidence from ≥2 high-stakes challenge situations before assigning a stage
• Blindspot stated specifically enough to feel uncomfortable — behavioral, not theoretical
• Developmental move concrete and schedulable — specific experience, named source, defined cadence
• Feedback structure cannot be dismissed by the current stage's characteristic dismissal reflex
• Assessment explicitly names what the framework does NOT address
• 90-day behavioral reassessment checkpoint scheduled with specific observable change as success indicator
• Stage label not shared with manager or HR in a way that could function as a performance rating

---

Part of deciqAI Knowledge Skills — open-source thinking skills that make rigor executable for AI agents. Built by deciqAI · https://deciqai.com · Contributions welcome — see the template at the repo root.