P.R.E.A.M

I. The Ratio

The Pareto principle is the observation that outputs are not distributed evenly across inputs. A minority of the inputs produces most of the output. A small share of customers produces most of the revenue, a small share of contributors produces most of the working code, and the same shape turns up across systems that have nothing else in common. The figures are rarely exactly 80 and 20, and the asymmetry is the reliable part rather than the numbers.

It takes its name from Vilfredo Pareto, who recorded in 1896 that about 80 percent of the land in Italy was held by about 20 percent of the population. Joseph Juran generalised it half a century later and gave it the name, calling the high-impact minority the vital few.

It is worth being clear that this is a description of how things tend to be distributed, not advice about how to live, which is mostly what it gets used as.

II. Where I Noticed It

I found it in my late twenties, working in the blockchain space, and I was not looking for a principle at the time. I was going back over what I had actually shipped across a stretch of that work, trying to account for the results, and the shape of the answer was hard to miss. A small fraction of what I had done accounted for almost all of the impact. The rest was motion.

There was nothing subtle about it in hindsight, which is the part that stayed with me. It did not arrive as an insight so much as something I should have been able to see the whole time and had been too busy to notice. Most of the hours had gone into work that, measured against results, may as well not have happened, and a few decisions and a few pieces of work carried everything else.

Once you have seen the shape you start looking for it, and it keeps turning up. I ran the same sort on what I was reading, on which parts of a system were worth maintaining, and on where my attention was actually paying off. Each pass returned time, and the returns are what pull you into running it on the next thing.

III. Where It Fails

The rule holds while it is pointed at things with numbers attached to them, and it breaks on things without.

It can only read what can be counted, and it files everything uncounted as zero rather than as unknown. So it is precise on things that are countable, repeatable and reversible, which tend to be low stakes, and silent on everything else, which tends not to be. The dangerous part is that outside its range it does not stop returning an answer. It returns the answer it always returns, which is to cut.

There is a second failure inside the countable range. The high-impact fraction is often not identifiable in advance. A maintenance task, a slow relationship or a redundant step can read as trivial right up until the thing it was quietly holding up comes down. Cutting it also cuts the margin, and margin is what absorbs a shock, so the efficiency and the fragility arrive together. Anyone who has watched an over-optimised system fail once does not need this explained twice.

IV. Why It Matters More Now

The rule has come to matter more to me over time rather than less, and the reason is a change in altitude.

In the early years the work was mostly grunt work, and the ratio was a way to spend my own hours better. That is a real use but a narrow one. As I stepped back from the day to day and started running a small team, it stopped being a personal habit and became most of the job. Management is allocation. A team has a fixed amount of effort, and almost all of the return comes from a small share of what that effort could be pointed at. Choosing which share, and keeping the team off the rest, is close to the whole task.

That is where the lever finally reads correctly. Pushing hard on the work is grunt work, and the leverage was never in the pushing. It is in the placement, in choosing the load and setting the fulcrum, which is exactly the part that becomes your responsibility once you stop being the one doing the pushing. The rule was useful when I was grinding. It is central now that the job is mostly deciding where other people grind.

The way I use it now is narrow and deliberate. I run it hard on anything with numbers attached, at the level of my own work and the team's. I do not run it on relationships, on health, or on anything that does not reverse. The title is borrowed from a group out of Staten Island and is half accurate. The ratio governs a fixed part of what I do, and the rest of it is left alone.