The Pareto principle in IT: 20% of causes create 80% of problems

Some things in a company you fix once and have peace for years. Others nag you every single week. The Pareto principle says this is no coincidence: most problems, costs and stress come from a small group of causes. Find that group and you fix a lot with very little. And in IT this can be done systematically.

What the Pareto principle is

At the end of the 19th century the Italian economist Vilfredo Pareto noticed that 80% of the land in Italy was owned by 20% of the people. Later the same imbalance showed up almost everywhere: 20% of customers bring 80% of revenue, 20% of products make 80% of turnover, 20% of the carpets in a house take 80% of the wear.

The numbers are neither exact nor sacred - sometimes the ratio is 90/10, sometimes 70/30. The essence is simple: causes and effects are not distributed evenly. A small minority of things has a huge impact. The practical conclusion follows: do not treat everything equally, find the minority.

What it looks like in IT

In IT the Pareto principle shows up with almost unpleasant reliability. From our practice:

80% of outages are caused by a few devices. In a company with twenty computers there are usually two or three machines that break down over and over: the oldest laptop, the overheating case under a desk, the disk that has been reporting errors for a year. The rest of the fleet runs for years unnoticed. We covered which parts fail most often in what breaks in computers.

80% of security incidents come from a few omissions. Postponed updates, one password used everywhere, missing two-factor authentication and careless clicking on e-mails. No exotic attacks - it is the same short list every time. We wrote a separate article about the 80/20 rule in cybersecurity.

80% of support time is eaten by a few recurring problems. The printer that “does not work” every Monday. The program that needs reconfiguring after every update. The meeting-room wifi. Solve these regulars properly instead of repeatedly firefighting and the time saved is enormous.

80% of the value comes from 20% of the features. Companies often pay for software with dozens of modules of which three are actually used. When choosing tools, it pays to ask: what do we really need every day?

How to find “your 20%”

The Pareto principle is useless if you do not know which minority matters. You need three things:

1. An inventory. A list of devices with age, configuration and failure history. Without it, decisions are made by gut feeling, and gut feeling usually lies - a loud problem is not necessarily a frequent problem.

2. An incident log. A simple table is enough: date, what happened, who was affected, how much time it cost. After six months, look at what repeats. It is usually surprising how few distinct causes keep coming back.

3. Monitoring. Watching disks, backups, service availability and temperatures reveals problems before they become outages. Why this pays off even for a small business is covered in why a company needs IT support.

The result is a list of hotspots sorted by impact. Work it from the top: replace the two most failure-prone machines, permanently fix the most frequent problem, automate the biggest time sink.

What it means for costs

Pareto is above all a tool for targeted investment. Instead of “we replace everything this year” or “we buy nothing this year”, you invest where it has the biggest effect: in the machines causing downtime and in prevention that avoids expensive disasters.

It works the other way too - what IT support costs for a small business is usually a fraction of what a single serious outage costs in downtime and lost data. Prevention is cheap precisely because it focuses on the critical 20%.

Where 80/20 does not apply: security and backups

One important warning. The Pareto principle is great for prioritising, but it is not an excuse to leave things 80% done. Two areas demand completeness:

• Backups. A backup covering 80% of your data is, for the remaining 20%, just as much a disaster as no backup. How to do it properly is in how to back up data correctly, and what to do when the worst happens in the disaster recovery plan.
• Security of critical systems. An attacker needs a single hole. Here the 80/20 rule helps you choose where to start, not where to stop.

How we see it

When we take over a new company’s IT, the first weeks are always about finding the 20%: we go through the devices and the problem history and deploy monitoring. The list of hotspots tends to be short, and fixing it turns daily chaos into calm operations. We apply the same logic to websites - which small share of pages brings most of the visits is covered in the Pareto principle and website traffic.

Conclusion

The Pareto principle is not a textbook curiosity but a practical tool: find the small group of causes behind most of your IT problems and fix it properly. You need an inventory, an incident history and monitoring - and the will to stop extinguishing the same fire over and over. Just remember that 80% is never enough for backups and security.

This article is part of the overview Business and IT.