The Pareto Principle, observed by economist Vilfredo Pareto in 1896, holds that roughly 80% of outcomes come from just 20% of inputs. A handful of customers drive most revenue. A few features drive most usage. A small set of tasks drive most of your results. The exact ratio varies, but the shape is remarkably consistent: outputs are not evenly distributed across inputs.
It works because effort and impact are rarely correlated. Treating every task, customer, or feature as equally important spreads you thin across work that barely moves the needle. Naming the vital few lets you pour disproportionate energy where returns are highest, and consciously ignore the trivial many.
A founder uses it when the task list has forty items and paralysis sets in. Instead of grinding through all forty, you ask which three actually drive the outcome, and you do only those today. The same lens applies to your product: if three of your twenty features drive 85% of daily usage, you stop polishing the other seventeen and double down on the three that matter.
Common mistake
People treat 80/20 as a license to ignore everything else permanently, when the trivial many often still need maintenance and the split shifts over time. They also guess the vital 20% from intuition instead of actually measuring which inputs drive the outcomes.
How to use it
Three ways to put it to work.
Everyday life
Your monthly budget feels tight but you cannot see why
Export three months of statements and sort every expense from largest to smallest. The top few categories - rent, the car payment, a creeping delivery habit - drive roughly 80 percent of spending, while the forty tiny coffees you guilt over are the trivial many. Renegotiate or cut just those vital few. Cancel the delivery subscription tonight and book a call to refinance the car.
Tech
Your app is slow and the bug backlog has sixty tickets
Pull the performance traces and error logs instead of working tickets top to bottom. Three endpoints account for about 85 percent of total request time and two crash types cause most user-facing errors. Those are the vital few; the other fifty-five tickets barely move the needle. Assign the team to fix only those three endpoints and two crashes this sprint and freeze the rest.
Small business
Your cafe menu has fifty items and prep is chaos
Pull the last quarter of POS data and rank every item by units sold and margin. Roughly ten drinks and pastries generate about 80 percent of revenue, while the long tail of specialty syrups and rare sandwiches eats prep time and creates waste. Cut the bottom thirty items and reorder around the vital ten. Print the trimmed menu for tomorrow.
Reckon · Thinking tool
Pareto Principle
Vilfredo Pareto, observed 1896; popularized by Joseph Juran
What it is
Roughly 80% of outcomes come from 20% of inputs. Identify the vital few and ignore the trivial many.
When to use it
When your task list has forty items and you feel paralyzed. Find the three that drive most of the outcome and do only those today.
Work through it.
Print this (use the Save as PDF button up top) and fill it in on paper. Find the 20% of inputs driving 80% of your results and concentrate everything there until the list gets shorter.
01
THE DOMAIN: Name the area where you feel spread too thin or uncertain what to focus on (revenue, tasks, customers, features, channels).
02
THE INVENTORY: List every item in that domain. Do not filter yet.
03
THE MEASUREMENT: Next to each item, write the actual output it produces: revenue, usage, time spent, leads generated. Use real numbers, not gut feel.
If you do not have numbers, estimate. The order of magnitude matters more than precision.
04
THE VITAL FEW: Sort by output and circle the top 20%. These are the items that carry the system. Name them explicitly.
05
THE STOP LIST: Write what you will stop doing, reduce, or hand off from the bottom 80% starting this week. One action per item is enough.
Reckon · reckon.report · flip for the working template
Reckon · Working template
Pareto Principle
Print double-sided. Read the how-to on the front; do the work here.
Every input / cause
List them all, write the output each drives, then circle the few that drive most of it