Hours to Master a Skill: 80/20 Learning Curve Calculator

It depends on your target level. Josh Kaufman showed that 20 hours of deliberate practice yields basic functional competence in most skills. Professional-level competence typically requires 1,000–3,000 hours; expert level, 5,000–7,500 hours. The famous '10,000-hour rule' from Gladwell (based on Ericsson's research) applies specifically to world-class elite performance in closed domains like concert piano or chess — not general professional proficiency.

Deliberate practice, as defined by Anders Ericsson, is practice specifically targeting your weakest points, with immediate feedback and active error correction — not practicing things you already do well. Only hours of deliberate practice contribute meaningfully to skill development. Passive exposure (watching tutorials, attending lectures without active practice) builds familiarity but not performance. Casual practice can take 2–3× longer to achieve the same gains as deliberate practice.

Identify the 20% of techniques, vocabulary, or concepts that cover 80% of real-world situations in your domain. Concentrate your first hours on that core instead of following a full curriculum linearly. For a language: the 1,000 most frequent words cover ~85% of everyday speech. For programming: functions, data structures, and control flow handle almost any basic problem. This approach gets you to functional competence much sooner.

Only indirectly. The 10,000-hour figure popularized by Malcolm Gladwell is based on K. Anders Ericsson's research on elite performers reaching expert-level (roughly 99%+ mastery in elite domains). This calculator targets the far more practical 80% functional mastery threshold, which for most professional skills falls between 100 and 1,000 hours — a 10–100× smaller investment than the 10,000-hour ceiling.

Very close. The AICPA recommends 300–400 hours of study for the full 4-part CPA exam; at 10 hrs/week that's 30–40 weeks. The PMI cites 35 contact hours as minimum for PMP eligibility, but most candidates report 150–200 hours of total preparation — at 10 hrs/week, 15–20 weeks. Enter your specific target and weekly hours into the calculator to get your personalized timeline.

Significantly. The base model assumes starting from zero. If you have transferable skills, reduce your total target hours by 20–40%. For example, if you already know Python and are learning R (normally ~500 hours from zero), your programming background may cut it to 250–300 hours. In the calculator, simply enter a lower total target hours figure to account for your head start.

Research on spaced repetition and skill retention suggests that fewer than 2–3 hours per week on a new skill leads to net retention loss between sessions — you spend part of each session re-learning rather than advancing. A practical minimum is 3–5 hours/week across at least 2–3 separate sessions, allowing spaced reinforcement and sleep-based memory consolidation.

Substantially. A good mentor identifies your specific errors, provides immediate feedback, and prevents you from spending months reinforcing incorrect techniques. Ericsson's research indicates this can reduce time-to-competence by 30–50%. In practice, 5 hrs/week with a coach may be equivalent to 7–8 hrs/week of unguided practice. If you have a coach, you can reduce your total target hours by 30% in the calculator to reflect this advantage.