Skip to content

Blog

Time management4 min read

The Pareto Principle in a Small Business: Where the 80/20 Rule Helps and Where It Misleads

The 80/20 rule is a rule of thumb about uneven distributions. It becomes useful once you count revenue, complaints or working time in your own business.

  • #zeitmanagement
  • #produktivitaet
  • #organisation
  • #kmu
  • #pareto-prinzip
Updated

AI-assisted · editorially reviewed Details

Text size
Also asMarkdownJSON

The 80/20 rule is usually told like this: 20 per cent of the work produces 80 per cent of the results, so drop the rest and you are done. It is not that simple. The Pareto principle is a rule of thumb about uneven distributions, and it is most useful where a business can actually count that distribution in its own figures.

Where the rule comes from

In 1906 the Italian economist Vilfredo Pareto observed that roughly 20 per cent of the population in Italy owned about 80 per cent of the land (Wikipedia: Pareto principle). He was not making a claim about working hours. The step into management came later, through the quality expert Joseph M. Juran, who from 1941 onwards noticed that a large share of quality problems traced back to a small number of causes. Juran later preferred to speak of "the vital few and the useful many", because calling the rest "trivial" suggested it had no value at all.

Two misunderstandings are hard to shake:

  • The numbers do not have to add up to 100. The 80 and the 20 measure different things: one is the result, the other the effort. Real cases can look more like 90/10 or 70/30.
  • It is not a law of nature. The rule describes what people often find when they count. Whether it holds in a particular case only becomes clear once you have counted.

Where counting pays off in a business

The principle becomes useful as soon as there is data to sort. In a small business that data usually exists already:

  • Revenue by customer: Most accounting or invoicing software can export annual revenue per customer. Sort it in descending order, add up a running total, and you see how many customers make up half or three quarters of your turnover.
  • Complaints by cause: Anyone who logs complaints or rework, even roughly in a spreadsheet, often finds two or three causes that keep coming back. That is exactly Juran's original use.
  • Products by contribution margin: In a shop or workshop, sorting shows which items fill the stockroom and which ones bring in the money.
  • Support requests by topic: If the same five questions keep coming in by phone, an answer on the website takes less time to write than twenty more calls.

In business administration this kind of sorting is called ABC analysis. How to apply it to your own task list is covered in the post on ABC analysis for time management.

Your own working time is harder to measure

In time management the rule is often reduced to "find the 20 per cent of your tasks that produce 80 per cent of your success". The trouble is that the success of an individual task can rarely be attributed as neatly as one customer's revenue. Bookkeeping brings in no money, but skipping it leads to trouble with the tax office. A phone call with a regular customer appears in no report, yet it may secure the next job.

A smaller approach is more honest. For two weeks, write down what your time actually goes on, roughly in half-hour slots. Then ask three questions of the list:

  1. Which activities led directly to an order, an invoice or a satisfied customer?
  2. Which activities are mandatory, even though they earn nothing?
  3. What is left, and what would happen if it stopped?

The third group is the candidate for dropping or handing over. The second is not: mandatory work does not disappear through prioritisation. At best it can be simplified, batched, or passed to a tax adviser or service provider.

For the activities in the first group, it helps to reserve fixed times in the calendar before appointments and requests fill the day. The post on time blocks in Google Calendar shows how.

Where the rule does harm

The Pareto principle fits badly when the parts of a result depend on each other. A quote that is 80 per cent finished cannot be sent. A roof missing its last 20 per cent leaks. This is a standard objection from project management: reading the rule as permission to leave things half-done only pushes the work further down the line.

Customers call for caution too. If a few large customers bring in most of the revenue, that is first of all a dependency and only secondly an opportunity. Writing off the many small customers makes the business more vulnerable if one of the big ones leaves. A better question is whether small jobs can be handled with less effort, for example with fixed package prices or a template for quotes.

Finally, a count only shows what was counted. A new customer who brings in little today sits at the bottom of the list. Whether they will be at the top in three years is something the analysis cannot tell you.

A worked example, clearly an assumption

Suppose a business has 40 customers a year. After sorting, it turns out that eight of them together account for 70 per cent of revenue. That would be a 70/20 split, close to the rule of thumb. It does not follow that the other 32 customers are superfluous. What follows is that the eight deserve particularly good care, and that among the rest it is worth checking which jobs cost more time than they bring in. With real figures from your own accounts the result may look quite different, which is exactly why the counting is worth doing.

Responsible: Yusuf Senel. Written with AI assistance and editorially reviewed after publication. How wischtig.de works

Read next