20/80 Rule Reloaded

The 20/80 Rule Reloaded

A short thought occurred to me.

Many people know and possibly apply the 20/80 rule (the whole Agile framework is based on it!), which, when generalized, goes something like this: “20% of our actions generate 80% of the results.” In other words - “roughly 20% of what we do makes sense.” It’s a strong statement, isn’t it? Simple?

Incredibly difficult! Because we are accustomed and conditioned to fill our time - to have the feeling that we are always doing something.

But that’s not what I wanted to write about. I wanted to point out that many people (I don’t want to use the word “majority,” though I wouldn’t be wrong by much) incorrectly interpret this statement.

It does not mean that once we reach 80%, we shouldn’t put any more energy into further work (project, release, functionality, task, whatever)… in fact, by then it’s too late! We would have already wasted a tremendous amount of our precious time. Because what good is 80% if it’s just crap, a cotton candy of tasks or functionalities?

The above principle means: find the 20% worth focusing on and, once you find it, put 200% energy and commitment into it. The rest can be dismissed, preferably by renegotiating the completion of “the rest.”

Business-wise: instead of creating a large system with 100 features, it is better to ask yourself what will really be useful and what will be used, and create those 20 features.

P.S.

In Domain-Driven Design (DDD), we call it the Core Domain! Always be aware of what your core is! :) Always ask yourself what is the Core in the system, module, or even functionality that you are working on.

(Text translated and moved from original old blog automatically by AI. May contain inaccuracies.)