Dreyfus Model

The Dreyfus Model of Skill Acquisition — Cognitive Change from Novice to Expert

1. Overview: A Growth Model Defining a 5-Stage Path of Skill Acquisition from Novice to Expert

    flowchart LR
    A["Rule-dependent<br/>novice stage<br/>Following instructions<br/>without context"] --"Accumulating experience,<br/>deepening context"--> B["Intuitive judgment<br/>expert stage<br/>Grasping the whole<br/>situation instantly"] --"Systematizing<br/>organizational capability"--> C["Optimized talent<br/>development &<br/>training design"]

    style A fill:#E3F2FD,stroke:#1976D2,color:#000
    style B fill:#1E3A5F,stroke:#1E3A5F,color:#fff
    style C fill:#E8F5E9,stroke:#388E3C,color:#000

Definition: A theory of skill acquisition developed by brothers Stuart Dreyfus and Hubert Dreyfus, describing how an individual’s cognitive approach shifts from rule-dependent thinking to intuitive expert judgment as they pass through five stages when acquiring a skill: Novice → Advanced Beginner → Competent → Proficient → Expert.

Characteristics: (Qualitative change) Each stage is distinguished by a qualitative change in how rules are used, how situations are perceived, and how decisions are made. (Intuitive, instant judgment) Experts don’t explicitly follow rules; they perceive a situation holistically and judge intuitively and instantly. (Applied to talent development) Used in software engineering, instructional design, talent development, and team composition to allocate roles and design tailored support.

2. Core Components of the Dreyfus Model

A. Structure of the 5-Stage Skill Acquisition Model

    flowchart LR
    L1["Stage 1<br/>Novice"]
    L2["Stage 2<br/>Advanced Beginner"]
    L3["Stage 3<br/>Competent"]
    L4["Stage 4<br/>Proficient"]
    L5["Stage 5<br/>Expert"]

    L1 --> L2 --> L3 --> L4 --> L5

    style L1 fill:#f5f5f5,stroke:#ccc,color:#555
    style L2 fill:#E3F2FD,stroke:#1976D2,color:#000
    style L3 fill:#FFF3E0,stroke:#F57C00,color:#000
    style L4 fill:#F3E5F5,stroke:#7B1FA2,color:#000
    style L5 fill:#1E3A5F,stroke:#1E3A5F,color:#fff

Characteristics of Each Stage in Detail

Stage	Use of Rules	Situational Awareness	Decision-Making Style	IT Role Example
1. Novice	Follows explicit rules only	Perceives isolated elements without context	Mechanical, rule-based execution	A new hire who only works from the install manual
2. Advanced Beginner	Recognizes some exceptions	Begins to spot patterns from repeated experience	Acts by criteria but struggles to prioritize	Resolves familiar error messages from past experience
3. Competent	Can set long-term goals	Can plan and set priorities	Deliberate analysis and planning before acting	Manages a project systematically against a plan
4. Proficient	Perceives the whole situation over rules	Grasps the situation holistically	Intuition from experience plus analytical judgment	Proposes an optimal design by seeing the whole code flow
5. Expert	Rules are internalized, not consciously followed	Grasps the essence of a situation instantly	Fully intuitive, instant judgment	Spots a latent bug or design flaw at a glance

B. Application to Organizational Capability Management and Talent Development

    flowchart TD
    subgraph R1["　"]
        direction LR
        A1["Stage-tailored training<br/>Novice: provide clear rules/procedures<br/>Competent: case/scenario learning<br/>Expert: autonomous, challenging work"]
        A2["Optimized role allocation<br/>Novice: repetitive, well-defined tasks<br/>Proficient: design/review roles<br/>Expert: architecture/mentoring"]
    end
    subgraph R2["　"]
        direction LR
        A3["Team composition strategy<br/>1 expert + 2 proficient<br/>+ 3 competent structure<br/>Knowledge-spread/mentoring system"]
        A4["Assessment/growth path<br/>Set capability assessment criteria<br/>based on Dreyfus stages<br/>Clear promotion roadmap"]
    end

    style A1 fill:#E3F2FD,stroke:#1976D2,color:#000
    style A2 fill:#F3E5F5,stroke:#7B1FA2,color:#000
    style A3 fill:#FFF3E0,stroke:#F57C00,color:#000
    style A4 fill:#E8F5E9,stroke:#388E3C,color:#000
    style R1 fill:none,stroke:none
    style R2 fill:none,stroke:none

Optimal Training/Support Strategy by Stage

Stage	Learning Need	Effective Training Method	Manager’s Role
Novice	Clear rules/procedures/checklists	Step-by-step manuals, 1:1 coaching	Detailed instructions, immediate feedback
Advanced Beginner	Accumulating experience of situational patterns	Case studies, pair programming	Explain context, expose exceptions
Competent	Goal-setting and planning ability	Project-leading experience, retrospectives	Grant autonomy, support goal-setting
Proficient	Developing intuition, gaining a holistic view	Mentoring, tackling complex problems	Delegate decisions, encourage reflection
Expert	Verbalizing tacit knowledge, knowledge transfer	Teaching, writing, open-source contribution	Assign a role spreading knowledge across the org

Applying the Dreyfus Model to IT Roles

IT Role	Novice Benchmark	Expert Benchmark
Software Developer	Can write code to spec	Instant judgment on architecture/code review
DevOps Engineer	Follows standard CI/CD procedures	Intuitively diagnoses and responds to incidents
Security Specialist	Runs the OWASP checklist	Instantly spots a breach pattern in code/logs
Data Analyst	Uses SQL query templates	Instantly derives business insight from data patterns

3. Expected Benefits and Practical Application of the Dreyfus Model

Category	Key Expected Benefit	Practical Application
Tailored training	Improved learning efficiency by moving from one-size-fits-all to stage-optimized training	Design new-hire onboarding as a novice-tailored manual plus a mentor
Team design	Mixed-stage teams naturally produce knowledge spread and mentoring	Have one expert review the whole team’s code to grow novice capability
Capability assessment	Clear stage criteria enable objective capability assessment and promotion standards	Use the 5 Dreyfus stages as the basis for job levels (junior to principal)
Knowledge management	Converts expert tacit knowledge into explicit knowledge as an organizational asset	Share expert knowledge via internal tech blogs, talks, and documentation

Psychological Safety Brooks' Law