What you'll understand by the end of this lesson
- What the Pareto Principle is and why the 80/20 ratio shows up across so many domains
- How to identify the 20% of pages or friction points driving 80% of your drop-off
- Why fixing three major friction points usually moves more than fixing twenty minor ones
- How to use the principle to ruthlessly prioritise your optimisation backlog
The principle in plain English
In 1896, Italian economist Vilfredo Pareto noticed that roughly 80% of land in Italy was owned by 20% of the population. He found the same unequal distribution in his own garden — 20% of the pea pods produced 80% of the peas.
This 80/20 pattern — where a small minority of causes produces a large majority of effects — turns out to appear across an enormous range of systems. Not because of a law of physics, but because complex systems naturally produce unequal distributions.
In CRO and conversion work, this means: most of your drop-off is happening at a small number of steps. Most of your revenue is coming from a small segment of users. Most of your conversion impact will come from a small number of changes.
The implication is not to ignore the 80% — it's to start with the 20%.
A simple example
A SaaS product has a six-step onboarding flow. The team maps drop-off at each step and finds:
- Step 1: 4% drop-off
- Step 2: 6% drop-off
- Step 3: 38% drop-off
- Step 4: 5% drop-off
- Step 5: 7% drop-off
- Step 6: 3% drop-off (reaches activation)
Step 3 is doing more damage than all the others combined. If the team spends equal effort on every step, they're optimising 80% of the flow that accounts for 20% of the problem.
The Pareto Principle says: fix Step 3 first. Don't just fix it — understand it deeply. What happens at Step 3? What is the user being asked to do? What do session replays show? Once Step 3 is fixed, re-map and find the next 20%.
How Pareto thinking changes CRO prioritisation
Funnel mapping reveals the vital few
Most digital funnels have a small number of catastrophic leak points and a larger number of minor ones. The mistake is to treat all pages and steps as equally worth optimising.
Funnel analysis — looking at drop-off rates at each step rather than averaging them — reveals the concentration of the problem. Once you can see where the 80% of drop-off lives, you know where to focus.
Before building a testing roadmap, map your funnel and rank each step by drop-off volume — not percentage. A step with 10% drop-off on a step that 10,000 users reach is more impactful than a step with 20% drop-off on a step that 100 users reach. The absolute number matters more than the rate when prioritising.
The danger of optimising everything evenly
Teams with a large backlog of "nice to fix" items often work through them in order of effort, recency, or whoever shouted loudest. This distributes effort across the 80% of issues that account for 20% of the impact.
Pareto prioritisation means constantly asking: "Is this the most impactful thing we can work on right now?" If a landing page has poor mobile layout and also has a broken trust signal, the trust signal problem may be worth five mobile fixes.
Revenue concentration in your user base
The Pareto Principle applies to customers too. In most businesses, a small proportion of customers — often 20% — drives most of the revenue.
This is useful for CRO in two ways. First: personalisation and special treatment for your top-revenue segment often delivers higher ROI than broad campaigns. Second: if you lose a high-value customer segment through a poor experience, the revenue impact is disproportionate to their size.
The 80/20 ratio is a heuristic, not a precise law. Your actual distribution might be 70/30 or 90/10. Don't get attached to the exact numbers — the principle is about unequal distribution, not a specific ratio. Use it to direct attention to concentration, not to predict exact proportions.
The CRO audit
Look at your funnel and optimisation backlog and ask:
1. Where is 80% of your drop-off actually concentrated?
If you don't have funnel step data, get it before prioritising. Optimising without knowing where users leave is like fixing a leak without knowing which pipe is broken.
2. What does your current testing roadmap look like?
If it has 30 items and they're distributed roughly evenly across pages and steps, apply Pareto logic. Which three items, if fixed, would account for the majority of potential impact? Start there.
3. Have you mapped your revenue by customer segment?
If 20% of your customers are driving 80% of revenue, your top-segment experience deserves disproportionate optimisation attention. A friction point that affects this segment has asymmetric impact.
A checkout funnel has five steps with the following drop-off rates: Step 1: 5%, Step 2: 8%, Step 3: 42%, Step 4: 6%, Step 5: 4%. Applying Pareto thinking, where should the team focus first?
You know how to find the vital few. But what happens when users simply can't find what they're looking for? Next — why features and content that users love still go unused, and how discoverability shapes adoption.