The 80/20 rule: find the few tasks that matter most

You've been busy all week. You've ticked off a pile of jobs: tidied the files, answered every message, renamed the folders, tweaked the logo again. But the side project you care about is exactly where it was on Monday. Lots of ticks, very little movement.

The 80/20 rule, also called the Pareto principle, offers a useful question: are a few of those jobs likely to do much more for your goal than the rest? Often the answer is yes. The rule isn't a precise formula, and the split is rarely exactly 80/20, but the idea is simple to use: look for the few jobs that matter most, and start with one of them.

The 80/20 rule at a glance

• What it says: in many situations, a small share of causes accounts for most of the results.
• In a to-do list: look for the jobs that could make a disproportionate difference to a particular goal.
• The numbers: "80/20" is shorthand. Real splits vary, and you don't need to measure them to use the idea.
• How to use it: for each job, ask what it would change; start with one of the few that would change the most.
• The catch: the rest still matters. The rule tells you where to start, not what to throw away.

What the Pareto principle actually says

The clearest statement comes from Joseph Juran, the quality-management pioneer who gave the principle its name. In a short 1974 paper, he described it as the phenomenon that "in any population which contributes to a common effect, a relative few of the contributors account for the bulk of the effect." He called those the "vital few" and the "trivial many".

Notice what that sentence doesn't say. It doesn't say 80 and 20. "80/20" is a familiar shorthand, not a ratio to expect every time. In real life the split might be 70/30 or 90/10, or there might be no strong pattern at all. The Institute for Healthcare Improvement, which teaches the idea as a quality tool, describes it the same way: "a relatively few contributors account for the majority of the effect."

×

Where the name comes from

Vilfredo Pareto was an Italian economist who studied how unequally wealth and income were distributed. He didn't set out a general "80/20 rule" for everything.

It was Juran who, in his Quality Control Handbook of 1951, applied Pareto's name to the general idea of the vital few. Years later he wrote that paper with the frank subtitle "Mea Culpa": he'd realised Pareto's work was about the economy, not a universal principle, and that he had "mistakenly applied the wrong name". As he noted, the confession changed nothing. The name had stuck.

How to apply the 80/20 rule to your to-do list

You don't need data or a chart. You need one honest question.

1. Pick one goal or project. The rule works best when you're asking "the few jobs that matter for what?" A side project, a work goal, getting the house ready for guests.
2. List the jobs on it. Everything that's on your list for that project, big and small.
3. Ask of each one: what would this change? If you did only this job this week, how much closer would you be? Be honest about the ones that feel productive but change little.
4. Mark the few. Mark any jobs that look likely to do substantially more for the goal than the others. They're often bigger, less fun or less clear than the rest, which is why they've been waiting.
5. Start with one of them. Not all three. One. Break it down until the first step is obvious, and do that first.
6. Let the rest wait their turn. The other jobs still get done, later. They just don't go first.

Try it on one project before you plan your week, and come back to it when priorities change.

A worked example

Here's a made-up side project: a small app, and the goal this month is to get first feedback from real users. The list looks like this:

• Polish the logo
• Rename the project folders
• Tweak the colour scheme
• Read two more articles about pricing
• Fix the sign-up bug
• Send a usable draft to three people who said they'd try it

Ask of each: what would this change? The logo, folders, colours and reading would all feel productive, but none of them gets anyone using the app. Fixing the sign-up bug and sending the draft both lead directly to feedback, and the draft can't go out until people can sign up. So the few are those two, and the first one to start is the bug.

That's a judgement, not a measurement. After you've done the work, check what actually changed: did the feedback arrive? If it didn't, or it pointed somewhere unexpected, revise your few.

Busywork isn't useless

It's tempting to read the 80/20 rule as "only do 20% of your work". That's not what it means. The small jobs often still need doing: messages need answering and folders do need tidying. The point is the order. Busywork is easy to start and satisfying to tick off, so it tends to go first. The few important jobs are harder, so they slip.

The rule is a way of noticing that and putting them back at the front. Move the busywork aside, not into the bin.

A few signs you're spending the week on the trivial many:

• You've ticked off lots of jobs, but your main project hasn't moved.
• The job you'd say matters most has been on your list for weeks.
• You keep "getting ready" to start it: researching, tidying, reorganising.

Strengths and limitations

Strength	Limitation	What to watch for
Helps you spot the jobs that matter	The 80/20 split isn't a law of nature	Use it as a question, not a formula
Works on any list, no tools needed	"What would this change?" is a judgement call	Ask it per goal, not across your whole life
Explains why busy weeks can feel empty	Can be misread as "skip most of your work"	The rest still gets done, just later
Pairs well with other methods	Doesn't tell you when to do the work	Book time for the few

The 80/20 rule and other methods

The 80/20 rule helps you choose which jobs matter. Other methods help with the next steps. Time blocking gives one of the few a time in your calendar. Most important tasks (MITs) turns the few into today's top three. And if you're not sure whether a job is important or just urgent, the Eisenhower matrix helps you sort them.

Finding the few in dypt

dypt can't tell you which jobs matter; that's your call. But it makes the few easy to mark, find and start.

• Keep each goal as a parent task. Put a project's jobs under it as subtasks, so you can look at them together and ask what each would change.
• Write the answer down. Add a short note to a job saying what it would change. It's a quick check that keeps "feels productive" honest.
• Mark the few as high priority. Give the jobs that would change most a high priority. Open All tasks and filter by high priority to find them across projects, or sort by priority to put them first. If you want a label that's just for this, a custom tag such as vital few works too.
• Break the first one down. Important jobs often wait because they're vague. Nest the first steps underneath, or let AI task breakdown suggest them, until the first action is obvious.
• Make the weekly question a habit. A repeating task such as "Find this week's few" each Monday keeps you asking before the busywork fills the week.

Find your few today

Pick one project that's been busy but stuck. List its jobs and ask of each: what would this change? Circle the two or three that would change most. Then pick one, write down its first small step and do that before anything else.

If you'd like a place to list the jobs, mark the few and break the first one down, try it in dypt, free to start.

Further reading

• Joseph Juran: The Non-Pareto Principle; Mea Culpa (1974)
  Juran's own account of the principle and how it came to carry Pareto's name.

• Institute for Healthcare Improvement: Pareto chart
  How the principle is used as a practical tool for finding the biggest causes of a problem.