The 80/20 Rule: focus your own effort and your team's

It is Monday morning and the team’s list for the week has forty items on it. Several are flagged as urgent. By Friday everyone will have worked hard, and the project will have moved about as far as three or four of those items allowed.

Anyone who has run projects for a while knows the pattern: a small part of the work decides most of the outcome, and the rest fills the calendar. The 80/20 rule names that pattern and, used with care, helps us decide where our own effort and our team’s should go.

The Pareto principle, or 80/20 rule, observes that in many situations a small share of the causes accounts for a large share of the effects. The numbers are shorthand: the split may be 90/10 or 70/30, and since the two figures measure different things, they do not need to add up to 100.

Where the 80/20 rule comes from

The usual story says that the economist Vilfredo Pareto discovered the rule and gave it his name. Neither half is quite accurate.

Pareto studied how income and wealth were distributed and built mathematical models to describe their inequality. His best-known figure is that roughly 80 percent of the land in Italy belonged to about 20 percent of the population. He was describing an economic distribution, not a general law about effort and results.

The generalization came from Joseph Juran, an engineer who devoted his career to quality management. In the 1920s he noticed that a few types of defect caused most of the defective output, and later saw the same pattern in absenteeism, car accidents and management problems. He called it “the vital few and the trivial many.” While preparing the first edition of his Quality Control Handbook, published in 1951, he needed a short name and used Pareto’s, since Pareto had found the same imbalance in wealth.

In a 1974 paper, The Non-Pareto Principle; Mea Culpa, Juran admitted that he had “mistakenly applied the wrong name,” but the name had already stuck. He also came to prefer “the vital few and the useful many,” so that nobody would read the rest as worthless.

A rule of thumb, not a law

The 80/20 ratio holds often enough to be worth checking, and it misleads when it is treated as a law. In projects it tends to appear in familiar places: a handful of defect types cause most of the rework, a few requirements carry most of the value, and the final polish on a deliverable takes far more effort than its share of the result.

None of those proportions is guaranteed, and in some projects the effects are spread so evenly that there is little to concentrate on. The rule tells us to look for imbalance, not where it is or how large, and it is no reason to abandon the rest. The useful many still have to be done, in the right order.

Find your vital few with data

Intuition tends to favor the loudest tasks. A simple Pareto analysis uses numbers instead:

1. List the items to compare: defect types, requirements, tasks or sources of delay.
2. Measure each one in the same unit, such as hours, cost or incidents.
3. Sort the list from largest to smallest.
4. Add a column with the cumulative percentage.
5. Draw a line where the cumulative curve starts to flatten. The items above it are your vital few.

The effort side depends on effort records you can trust. In ITM Platform, project managers estimate the hours each task needs, per person or per professional category, and team members report the time they actually spend through their timesheet, so the two figures can be compared, as explained in effort management: estimated, actual and accepted.

Weigh value against effort

Effort is half of the picture; the other half is what each piece of work contributes to the project’s goals. An effort-value table puts both side by side:

Value / effort	Low effort	High effort
High value	Do first	Plan carefully
Low value	Fit in when convenient	Challenge before starting

The top-left cell is where the 80/20 rule pays off. High-value, high-effort items are usually the core of the project and need planning rather than postponement. The bottom-right cell often holds requests added along the way and never questioned, so it deserves an open discussion.

Value is best scored by the team and the sponsor together, on a simple scale tied to the project’s objectives. The effort column is only as good as its estimates, so they deserve a consistent method, such as those in how to estimate the duration of a task.

Keep the team’s attention on the few

The same applies to our own week: unless the two or three items that matter most get time blocked early, meetings and small requests take it first.

A team spread across too many fronts gives the vital few the same fragmented attention as everything else. Before adding work to someone’s week, check what they already carry. The weekly workload view in ITM Platform shows each person’s estimated effort and actual time per day on every project and service, compares the total with their capacity and flags overallocation. From there, a project manager can redistribute estimated effort in the project’s team.

The same reasoning for the portfolio

Choosing which projects to fund is the same exercise one level up: estimate each project’s value against the organization’s goals, compare it with its cost and select the combination that delivers the most value within the budget. In ITM Platform, programs support this with business goal prioritization, project scoring against those goals, a value versus cost chart and an efficient frontier, with alternative selections kept as scenarios.

When the 80/20 lens misleads

The rule can do harm when it is applied without judgment:

• Mandatory work. Compliance, safety and contractual commitments may score low on value and still be non-negotiable.
• The last stretch. Testing, documentation and handover are often what make the rest of a deliverable usable.
• Dependencies. A low-value task may be a prerequisite for a high-value one.
• Delayed value. Training or paying down technical debt scores low and gets postponed indefinitely.

Talking trade-offs with sponsors

The rule is most useful when a project cannot deliver everything that was asked with the time, budget and people available, and the conversation with sponsors or clients turns to cutting functionality, moving a deadline or reducing cost.

The effort-value table shows which few items carry most of the value and what they cost, and which could be postponed or simplified with the least loss, so the sponsor decides with the same information as the team. Sometimes most of the remaining effort must still go to items with little visible value, because they are mandatory or other work depends on them. It is better to say so at the start than near the deadline.

Next steps

• Try ITM Platform and sort last month’s tasks by actual hours to see where your team’s effort went.
• Read strategic alignment: selecting the most valuable project portfolio to weigh value against cost for whole projects.
• See how strategic alignment works in ITM Platform, from prioritizing business goals to selecting projects.