The Pareto Principle (80/20)

Overview

In most real systems, a small fraction of inputs produces the majority of outputs. The pattern — heavy-tailed distribution where the vital few dominate the trivial many — is empirically robust across operations, software, and revenue. Pareto (1896) documented the distribution; Juran (1951) coined "vital few and trivial many." Key hazard: different outputs have different vital fews, and asserting "80/20" without measuring is folk reasoning.

Compose: first-principles to identify what outcome you are driving; aarrr-pirate-metrics to instrument which inputs produce which outputs; probabilistic-thinking to test the split is real and not a small-sample artifact.

When to Use

Use: team treating many items as equally important; resources spread thin; prioritization needed; you suspect a heavy-tailed distribution that hasn't been measured; deciding where to concentrate AI capex / AI adoption effort when most pilots stall and a few use cases capture the value (which AI bets to fund vs. cut against AI-native competition).

When NOT: only a few items total; safety-critical or long-tail-strategic items where the residual matters; the split is trivially obvious; using it to abandon a strategically valuable long tail.

Coaching Novices (Adaptive Front Door)

• Engine mode: user has data and wants vital few identified — run The Process directly.
• Coach mode: vague situation or signals unfamiliarity — guide step by step.