The Dreyfus Model of Skill Acquisition

Definition

The Dreyfus model (Hubert and Stuart Dreyfus) holds that skill development moves through five distinct stages — Novice, Advanced Beginner, Competent, Proficient, and Expert — that differ not just in "how much" someone knows but in how they perceive the problem, what kind of guidance helps them, and whether they can self-correct. Crucially, the model is per-skill, not per-person: "you are neither 'expert' nor 'novice' at all things; rather, you are at one of these stages in some particular skill domain."

In the Book

Hunt walks through each stage's defining trait: novices need context-free recipes ("whenever X happens, do Y") because they lack the experience to judge when a rule doesn't apply; advanced beginners can act on their own but reject the "big picture" as irrelevant; competents can troubleshoot and plan deliberately but still can't self-correct; proficients make the key leap — they can reflect on past performance and revise, and they can absorb maxims (context-dependent proverbs like "test everything that can possibly break") rather than needing rigid rules; experts work from intuition, not conscious reasoning, and often can't articulate why they made a call — like a doctor who diagnoses a patient because "he didn't look right."

The book's central cautionary example is what Hunt calls "herding racehorses and racing sheep": in a Dreyfus study, expert airline pilots were asked to write rules for novices — and those rules helped the novices. But when the same experts were then forced to follow their own rules, their own performance got measurably worse. Forcing uniform process onto a team punishes experts (dragging them to novice-level performance) while under-supporting novices thrown into ambiguous situations without guardrails ("racing sheep"). Hunt also cites the "Unskilled and Unaware of It" research (Kruger and Dunning) — the lemon-juice bank robber who believed the juice made him invisible to cameras — to show why novices are especially prone to overconfidence.

Why It Matters

This concept reframes "give everyone the same process" as a category error: process, methodology, and tooling that helps a novice can actively cripple an expert, and vice versa. It gives you a diagnostic question to ask before prescribing any rule, checklist, or standard: what stage is this person (or team) actually at, on this specific skill — and does this intervention match it? That question generalizes past software teams to onboarding, coaching, regulation, and any setting where uniform procedure is mistaken for fairness.