LEADERSHIPDays to result

The Four Development Levels Model

Map competence and commitment to unlock the right support approach

Problem it solves

ineffective leadership

Best for

Managers diagnosing why a team member is struggling or excelling on a specific task

Not ideal for

Situations requiring assessment of general personality or cultural fit rather than task-specific performance

Overview

Why this framework exists

The Four Development Levels Model provides a diagnostic lens for understanding where an individual stands on any given task by evaluating two dimensions: competence (demonstrated transferable knowledge and skill) and commitment (a combination of motivation and confidence). The four levels form a predictable progression: D1 (Enthusiastic Beginner) has low competence but high commitment—they are excited but do not yet know what they do not know. D2 (Disillusioned Learner) has developed some competence but commitment has dropped as the reality of difficulty sets in. D3 (Capable but Cautious Contributor) has moderate-to-high competence but variable commitment, often lacking confidence despite having skill. D4 (Self-Reliant Achiever) has both high competence and high commitment. Understanding this progression helps leaders anticipate predictable performance dips and respond appropriately.

Core principles

5 total
  1. Competence and commitment are the two essential dimensions of development
  2. Development follows a predictable but non-linear progression
  3. The D2 dip in commitment is normal and expected, not a sign of failure
  4. Development level is always task-specific and goal-specific
  5. People can be at different development levels on different tasks simultaneously

Steps

4 steps
  1. Identify the Specific Task or Goal
    Narrow your focus to one particular goal, task, or responsibility. Development level is meaningless in the abstract—a person might be D4 at financial analysis and D1 at public speaking simultaneously. Precision in identifying the task ensures accurate diagnosis and prevents unhelpful generalizations about the person.
    Pro tipBreak large projects into component tasks and diagnose each separately for more granular support
  2. Assess Competence Through Evidence
    Evaluate demonstrated knowledge and transferable skills through observation of actual performance, not self-report alone. Look for evidence of knowledge (can they explain it?), skill (can they do it?), and transferability (can they apply it in new situations?). Competence is factual and observable, not a matter of opinion or potential.
    Pro tipUse behavioral examples rather than ratings—ask for demonstrations or review recent work products
    WarningDo not confuse enthusiasm or confidence with competence—D1s are often very confident despite lacking skill
  3. Assess Commitment Through Conversation
    Gauge motivation (enthusiasm, interest, willingness to learn) and confidence (self-assurance, feelings of capability) through direct conversation. Ask open-ended questions like how are you feeling about this project or what concerns do you have. Commitment is more subjective and requires trust and honest dialogue to assess accurately.
    Pro tipWatch for nonverbal cues—body language and energy often reveal commitment levels more honestly than words
  4. Plot the Development Level
    Combine your competence and commitment assessments to identify which of the four levels best describes the person on this task. D1: low competence, high commitment. D2: low-to-some competence, low commitment. D3: moderate-to-high competence, variable commitment. D4: high competence, high commitment. Use this as the starting point for choosing your leadership approach.
    Pro tipValidate your diagnosis by sharing it with the person and getting their perspective
    WarningRemember that development is not strictly linear—people can regress under stress or when task parameters change

Checklist

Saved in your browser

Examples

1 cases
Software Developer Learning a New Language

A senior developer (D4 in Python) begins learning Rust. Despite deep programming experience, they are D1 on Rust—excited but making basic mistakes. After a month of frustrating compile errors, they hit D2—some syntax knowledge but declining motivation. Their manager recognizes the pattern and shifts from initial hands-off delegation to active coaching with pair programming sessions.

OutcomeDeveloper pushes through D2, reaches D3 competence within three months, and achieves D4 proficiency by six months

Common mistakes

3 traps
Treating Development Level as a Personality Trait
Labeling someone as always a D2 turns a situational diagnostic tool into a judgment. Everyone is at different levels on different tasks, and levels change over time with experience and support.
Ignoring the D2 Dip
Managers who do not expect the natural drop in commitment that comes with early learning often interpret it as a character flaw or wrong hire, when it is actually a predictable phase that requires coaching and encouragement.
Over-Relying on Self-Assessment
D1 enthusiastic beginners often overestimate their competence while D3 capable contributors underestimate theirs. Relying solely on self-report without behavioral evidence leads to misdiagnosis and mismatched support.

Origin story

How this framework came to be

The development levels model emerged from Blanchard and colleagues' observation that new employees almost always follow a predictable emotional and skill trajectory when taking on new responsibilities. The initial excitement of starting something new (D1) reliably gives way to discouragement as the learning curve steepens (D2). Those who persist develop skill but often doubt themselves (D3) before finally achieving mastery and confidence (D4). This pattern was consistent enough across thousands of organizational observations that it became a core diagnostic tool within the SLII framework.

Source

Traced to primary
Source · BOOK
Leadership and the One Minute Manager
Ken Blanchard · 2013
Open source →

Related frameworks

Browse all Leadership →