01Overview
The Dunning-Kruger effect is the cognitive bias where people with limited knowledge in a domain overestimate their competence, while people with genuine expertise tend to underestimate theirs. Novices don't yet know enough to know what they don't know. Experts know exactly how much they still don't know.
For designers, this operates in two directions simultaneously: new practitioners overestimate how well they understand users; experienced practitioners may be too tentative in the face of genuine expertise. Both distort the quality of design decisions.
02Detailed explanation
Kruger and Dunning's 1999 study tested participants on logic, grammar, and humour. Those who scored in the bottom quartile estimated their performance at the 62nd percentile. Those in the top quartile estimated themselves at the 75th percentile — below their actual rank. The less people knew, the worse their metacognition: they lacked the skill to recognise their own deficiency.
- The "peak of Mount Stupid" — the moment of maximum unwarranted confidence just after learning enough to feel fluent — is a real and predictable phase in skill development.
- Genuine expertise often produces more uncertainty, not less: experts know the edges of their knowledge and the complexity of the domain, so they hedge more carefully than novices.
- In design: a person who has read one book on UX and attended one workshop is likely to be more confidently certain about design decisions than someone with ten years of practice and a hundred user studies under their belt.
03Why it exists
Accurately assessing your own ability requires the same skills as performing the ability well. If you're not good at logic, you can't accurately evaluate a logical argument — including your own. The deficiency in the skill is also a deficiency in the metacognitive ability to notice the deficiency.
You need competence to accurately judge competence. Novices lack the framework to notice what they're getting wrong. Experts have that framework — which is why they see the complexity and hedge where novices charge ahead.
04Effects on users
- Users who are novices with a product often don't know what they don't know — they won't think to ask for help because they don't yet understand what competent use of the tool looks like.
- In onboarding, this means that user-reported satisfaction ("this is easy!") from novices can be misleading — they may not yet have encountered the complexity that will eventually trip them up.
- Users who overestimate their skill level may skip documentation, tutorial prompts, or contextual help — assuming they already know enough to proceed without it.
- Expert users, conversely, may request more control, more transparency, and more edge-case handling — and be dissatisfied with a product that was designed only for the novice mental model.
05Effects on designers & teams
- Junior confidence vs. senior doubt: the most confident voices in a design critique are sometimes the least experienced. Seniority in design often produces more careful, hedged language — not because experts know less but because they know more about what they don't know.
- Research interpretation: teams with limited research experience may treat three user interviews as sufficient data to make sweeping design conclusions. Experienced researchers know three is a starting point, not a sample.
- Stakeholder pushback: non-designers who have "strong opinions on design" are often at the peak of Mount Stupid — confidently wrong in ways that are difficult to counter without sounding defensive.
- Hiring: the most confident portfolio candidates aren't necessarily the most skilled. Measuring actual practice (problem framing, research rigour, iteration) matters more than presentation confidence.
06Practical takeaways
- Create structured evidence requirements: require that design decisions reference specific user research findings — this surfaces the difference between "I think" and "we observed."
- Build calibration rituals: before releasing a design, explicitly ask "what are we least sure about?" — expert teams surface genuine uncertainty; novice teams surface overconfidence.
- Teach metacognition: helping designers understand the stages of skill development reduces false confidence in early-career practitioners and imposter syndrome in experienced ones.
- Separate confidence from correctness in critiques: the most confident voice in a design review is not the most reliable. Create processes where all voices are weighted by evidence, not volume.
- Design for the novice's unknown unknowns: users won't tell you what they don't know they need. Observe their behaviour; don't only ask their opinions.
07Design examples
The three-interview conclusion
A junior researcher conducts three user interviews and presents a confident synthesis: "users need X." An experienced researcher would treat this as an initial directional signal, not a conclusion — they know that three participants is the threshold for starting to see patterns, not for confirming them.
The confident non-designer
A product manager who has read "Don't Make Me Think" presents a strong opinion about why a specific design is wrong — and is almost impossible to reason with. The design team, who have spent a year researching the problem, are more uncertain. The Dunning-Kruger effect has inverted the confidence-to-expertise relationship.
The self-reported expert
A user marks themselves as "experienced" in an onboarding questionnaire — so the product shows an advanced interface immediately. But the user was confident, not competent; they've now been dropped into a complex view with no scaffolding. Self-reported skill level is not a reliable signal.
Volume vs. substance
In a design review, the loudest feedback comes from the team member with the least UX experience. Their critique is confident but based on personal preference, not evidence. Senior designers hedge more — and are heard less, because the room interprets hedging as uncertainty rather than expertise.
08Ethical risks
In product teams, the Dunning-Kruger effect can cause overconfident designers to ship decisions that harm users without adequate research validation. When confidence substitutes for evidence, the people most affected — the users — have no voice in a decision being made by someone who incorrectly believes they already know the answer.
Confidence is not a measure of correctness. In design, the most ethical response to uncertainty is to acknowledge it — and then test your way to knowledge rather than assert your way there.
10Suggested reading
Suggested reading is temporarily unavailable. Please check back later.