Pareto Principle in Engineering

Also Known As

TL;DR

Explanation

Vilfredo Pareto observed that 80% of Italy's land was owned by 20% of the population. The pattern appears everywhere in software: 80% of crashes come from 20% of bugs, 80% of page load time from 20% of resources, 80% of user value from 20% of features. The engineering application: profile before optimising (find the 20%), focus testing on high-defect modules, and build the 20% of features that deliver 80% of user value first. The ratio is illustrative, not precise.

Common Misconception

Why It Matters

Common Mistakes

• Optimising code before profiling — guessing the slow 20% is almost always wrong.
• Treating the 80/20 split as precise — it is a heuristic, not a law; the actual ratio varies.
• Using it to justify ignoring edge cases — the 80% long-tail matters for reliability.
• Applying it to team effort without data — identify the high-value 20% empirically, not by assumption.

Code Examples

// Optimising without profiling — wrong 20%:
function generateReport(): string {
    // Developer 'felt' the string formatting was slow — optimised it:
    $output = '';
    foreach ($rows as $row) {
        $output .= implode(',', $row) . "\n"; // Was already fast
    }
    // Actual bottleneck: the SQL query fetching $rows — never investigated
    return $output;
}

// Profile first, then optimise the real 20%:
// $ php -d xdebug.mode=profile script.php
// Result: 94% of time in UserRepository::findAll()
// Fix the actual bottleneck:
function findAll(): array {
    // Add index, add cache, reduce columns — 80% faster
    return $this->cache->remember('users', fn() => $this->db->query(...));
}

References

• ↗ https://en.wikipedia.org/wiki/Pareto_principle

Tags

Related Terms