The rule of three is the empirical observation that audiences process and remember information best when it arrives in groups of three. Aristotle used it in rhetoric, Cicero made it a structural principle, and Cowan's 2001 working-memory research put a cognitive boundary on it: average working-memory chunk capacity sits at three to four items. Four claims feel complete but overwhelming; three feel definitive. The practical implication for any professional who presents, pitches, or persuades is that three is the ceiling for any single level of a structure — not a minimum.

When to use Rule of three

Apply the rule of three whenever you are structuring a recommendation, an opening, a close, or a key-point section. The cue is any moment where you have more than three supporting points and are tempted to use all of them.

Opening remarks and executive summaries
Pitches and proposals ("three reasons we should do this")
The close of a presentation
Taglines, slogans, and positioning statements
Any structured argument with more than two points

How to use it

Count your supporting points. If you have four or more, cut to three. Choosing the three strongest forces clarity and makes each point stronger by the attention it now receives.
Structure the three in an arc if possible. The most memorable arrangement is not three equivalent points but a sequence: smallest to largest, past to present to future, problem to cause to solution.
Name the three upfront. "Three things today:" signals to the listener that they can track their position in your argument. The structure is more useful when it is explicit.
Apply it at every level, not just the top. Three sections, each with three sub-points, is the Minto Pyramid with the rule of three. Four sub-points under one section breaks the cognitive rhythm.

Example

Them

Walk me through why we should make this investment.

On your HUD

Three reasons: cost, risk, and momentum.
On cost: we pay $400K annually on the current system; this costs $180K to build and $40K to run. Savings materialize in year two.
On risk: the vendor is sunsetting support in 18 months. Every quarter we wait is a quarter closer to a hard cut.
On momentum: the engineering team has already scoped the migration. The window is now — if we delay, the team context disappears.

What Kennan would surface in this moment, in the same first-person bullet format as the in-app HUD.

Common pitfalls

Forcing three when two or four is right. The rule is a ceiling for effective communication, not a mandate. If there are genuinely two strong points, use two.
Three weak points instead of fewer strong ones. Three mediocre points are worse than two excellent ones. The discipline is in the selection, not the count.
Not naming the three upfront. Making three points without announcing the structure is not the rule of three — it is three things. Name the number at the start.

Where it comes from

Aristotle · Cicero · Cowan (2001) · Carlson & Shu (2014)

In your next meeting

Kennan watches for the conversational pattern this framework addresses and surfaces a first-person line you can read off your HUD, in the same shape as the example above. Frameworks are receipts; the user-facing output is a sentence, not a citation.