Skip to main content

The Tight Five

Why do the strongest compression patterns always stop at five?

The Cognitive Anchor​

The number five is not arbitrary. It sits at the precise edge of what the mind can hold under load.

George Miller's 1956 study established that working memory holds 7±2 chunks. Nelson Cowan's 2001 refinement showed that under cognitive load — pressure, fatigue, novelty — effective capacity drops to 4±1. The Zeigarnik effect adds a third constraint: 5–7 open loops is where cognitive overload begins under stress.

Five sits safely between Cowan's floor and the Zeigarnik ceiling. Four is too thin — you lose coherence. Six starts to leak under pressure. Five holds.

The Tight Five is not a framework you adopt. It is a constraint you discover under load.

See: Miller's Number, Working Memory, Zeigarnik Effect

Three Properties​

A Tight Five is not a five-item list. The count is not the point. The binding is.

Bound​

Remove one element and the loop collapses. The five are interdependent — each element feeds the others. A five-item checklist lets you skip item three and still finish. A Tight Five does not. Remove Principles and Performance becomes guesswork. Remove Platform and Process becomes friction. The structure holds because every element is load-bearing.

Polished​

Each element earns its place. No redundancy survives rehearsal. A stand-up comic's "tight five" is five minutes rehearsed until every word is necessary — no fat, no filler. The discipline is the same: if two elements can be merged without losing signal, the five is not yet tight.

Incompressible​

You cannot run it with four and get the same result. This is the test. If the fourth and fifth elements feel redundant, you have not yet found the real fifth. The incompressibility property is what separates a Tight Five from a useful summary.

Two Faces​

The same five-slot structure appears in two orientations depending on who is looking.

Engineer's Face — Inside-Out, Invariant​

Performance · Principles · Platform · Process · Players

Same five cells every cycle. Consistency of cognitive process is the point. The Engineer looks from inside the work outward — doing, building, attending. This face does not change with context.

Dreamer's Face — Outside-In, Context-Adaptive​

Purpose · Principles · Platform · Perspective · Performance

The five slots shift with whatever domain is in view. The Dreamer stands outside the work to see the big picture. Three cells bridge both faces (Principles, Platform, Performance). Two pivot: the Engineer's Process is what the Dreamer's Purpose matures into; the Engineer's Players is what the Dreamer's Perspective matures into.

When the Dreamer's five are explicit, the Engineer's foundation sharpens. Fix the dream first so the build has somewhere to land.

The Fractal​

The same binding appears across every domain on this platform. Different matter, same architecture. Remove one element in any row and the row collapses.

Questions​

Purpose — Principles — Platform — Perspective — Performance

Rhetoric​

Ethos — Logos — Pathos — Kairos — Topos

Persuasion​

Dreams — Failures — Fears — Suspicions — Enemy

The Loop​

Intention — Awareness — Impact — Measure — Reflect

Archetypes​

Dreamer — Realist — Engineer — Coach — Philosopher

VVFL​

Questions — Principles — Protocols — Standards — Platform

The same five slots compress every domain on this platform. What changes is the matter — the names of the elements. What stays constant is the binding: Bound, Polished, Incompressible.

Three Views​

Three existing pages each hold a different lens on the same pattern. None of them is complete alone.

Strategic view — Navigation System: the Tight Five applied to Value, Belief, and Control systems; rhetoric as navigation; the Dreamer's five priorities as a belief-building instrument.

Engineering view — The Tight Five (picture): the rugby scrum metaphor; the invariant Engineer's face; Te Whare Tapa Wha as a human instance; the ten-element loop.

Operational view — Tight Five Loops: fifteen-plus loop instances across Navigation, Engineering, Business, Agency, and Operations; the fractal at four scales (Agent, Individual, Team, Organization).

Context​

Questions​

Which of the three properties — Bound, Polished, or Incompressible — is hardest to achieve in the domain you work in most?

  • If the five-element structure is invariant, what changes when you apply it to a new domain — and what stays the same?
  • What is the difference between a five-item checklist and a Tight Five?