Individual skill

80-20-rule

Use this skill whenever the design has many features, controls, or content elements and decisions about which to prioritize matter — feature roadmaps, redesign scoping, IA decisions, dashboard design, settings page audits, marketing content prioritization, or any design with many candidates competing for attention. Trigger when the user asks "what should we focus on?", "should we add another feature?", "what can we cut?", or when reviewing a UI cluttered with rarely-used controls. The 80/20 rule (Pareto principle) is one of the foundational principles in 'Universal Principles of Design' (Lidwell, Holden, Butler 2003) and one of the most quoted across design, business, and engineering.

plugins/HDeibler/universal-design-principles/plugins/cognition-and-learnability-principles/skills/80-20-rule/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,530
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# The 80/20 Rule

The 80/20 rule (also called the Pareto principle, after Italian economist Vilfredo Pareto) is the empirical observation that, in many systems, a small fraction of inputs produces most of the outputs — roughly 80% of effects from 20% of causes. The exact numbers vary (sometimes 70/30, sometimes 90/10) but the shape — a heavily uneven distribution — recurs across economics, management, software usage, and design.

For designers, the principle's central use is *prioritization*: identify the 20% of features or content that produces 80% of the value, design that 20% well, and let the remaining 80% receive proportionally less effort.

## Definition (in our own words)

In most large systems, effects aren't distributed evenly across causes. A small minority of features account for the bulk of usage. A small minority of users generate most of the support tickets. A small minority of bugs cause most of the crashes. A small minority of tasks consume most of the time. The 80/20 rule names the pattern and suggests that designers should put their effort where it produces the most return: the critical 20%, not the trailing 80%.

## Origins and research lineage

- **Vilfredo Pareto** (1848–1923), Italian economist. Originally observed that approximately 20% of Italians owned 80% of the land. The pattern proved remarkably general.
- **Joseph M. Juran** (1951), in *Quality Control Handbook*. Generalized the pattern from economics to industrial quality control: a small fraction of defect causes accounted for most defects. Juran called this "the vital few and the trivial many," a phrasing still used.