The Tight Five
How many things can you hold in your mind and still act?
Not think about. Not write down. Not save to a spreadsheet you'll never open again. Hold in working memory while making a decision under pressure.
The answer, for nearly everyone, is five.
The Problem
You've been in the meeting. Twelve strategic priorities on the whiteboard. Everyone nods. Nothing changes. You've written the plan. Forty-seven action items, colour-coded, time-boxed. By Thursday it's dead. You've had the insight at 2am that connects everything, and by morning it's fog.
This isn't a discipline problem. It's an architecture problem.
Your mind has a loading dock and it fits five crates. Load six, one falls off. Load twelve, you're standing in a car park full of scattered cargo wondering where to start.
Miller's Number says seven, plus or minus two. But Miller was measuring recall, not agency. Recall is passive. You can hold seven digits long enough to dial a phone. Agency is active. You hold the elements, see their relationships, and decide what to do next. That costs more. Five is the budget.
The question isn't whether five is enough. It's which five.
Why Tight
The word carries three loads.
Bound. In rugby, the tight five are two props, the hooker, and two locks. They bind together in the scrum. Arms interlocked. Eight bodies pushing against eight bodies. Remove one prop and the scrum collapses. Not weakens. Collapses. The tight five don't score tries. They create the platform that makes tries possible. Every flashy backline move in the history of the game started with five people doing unglamorous work nobody films.
Polished. In stand-up comedy, a tight five is a comedian's best five minutes. Not their shortest. Their most refined. Comedians perform hundreds of times, in rooms that don't laugh, cutting every word that doesn't land, adjusting every pause, until what remains is pure signal. A tight five sounds effortless because everything that required effort has been removed. That's why the best pitches feel like conversations. They've been compressed until nothing remains that doesn't serve the person listening.
Incompressible. Both meanings converge here. You cannot remove a prop from the scrum. You cannot cut a joke from the set. What remains is what must remain. The test isn't "is this good?" The test is "does the system collapse without it?"
The count isn't the point. The binding is.
The Swap
Here's the move most people miss.
The Tight Five isn't a fixed list. It's a slot structure. The five changes depending on what mode you're in, what domain you're operating in, what question you're trying to answer. The architecture is constant. The contents are contextual.
A Dreamer loads one five. An Engineer loads another. A Coach loads a third. Same mind, different schema, different world visible.
Building a business? Principles, Performance, Platform, Process, Players. You see the value creation system. Checking your health? Wairua, Hinengaro, Tinana, Whanau, Whenua. You see which wall is cracking. Preparing a pitch? Ethos, Logos, Pathos, Kairos, Topos. You see where persuasion leaks. Examining your life? Five questions that won't let you hide. You see where you're lying to yourself.
Scott Adams wrote that the ability to change your mind is one of the best life skills you can develop. He's right, but incomplete. The skill isn't changing your mind. It's changing your schema. Loading the right five for the context you're in, then acting from that frame instead of whatever frame you happened to wake up with.
The meta defines the matter. Whoever loads the schema controls what becomes visible.
The Sequence
Order matters.
In process engineering, commissioning means verifying that a built system actually works. You don't test the control loop before the pipe is installed. You don't calibrate instruments before the wiring is proven. Each component progresses through states: idea, spec, drawing, procurement, installed, wired, controls proven, operating. Readiness is the weighted blend of all components at their different stages.
The Business Five works the same way.
Principles first. What's true? Without this, every downstream decision is a guess dressed as strategy. Performance second. What does good look like? What does bad look like? Without this, you're building blind. Define good cheese before designing the pipework. Platform third. What creates leverage? Only meaningful once you know what you're measuring and why. Process fourth. How do things get done? Only valuable when built around performance targets, not vibes. Players fifth. Who does what? Only assessable against the system they operate in.
Most people start at Platform. They buy the tools before naming the problem. Or they start at Players. They hire before knowing what the job actually requires. Commissioning teaches you to resist that impulse. Wire the principles first. Prove the measurement second. Build the platform third. Document the process fourth. Then, and only then, assess who plays what role.
It's unglamorous. It's the tight five. It's what makes the flashy stuff possible.
When Mantras Graduate
Here's a connection that took me too long to see.
A mantra is a trigger phrase. The human equivalent of a hook. "Act on principles, not emotion." "Ship, then iterate." "One task, full attention." Good mantras. Useful under normal conditions.
But mantras fail under load. When the pressure hits, the phrase evaporates. You don't forget the mantra. You forget to use it. That's the gap between knowing and doing, and willpower alone can't bridge it.
The upgrade path runs through four levels. A mantra is a phrase you remember. A rule is context you load and apply. A hook fires automatically on an event. A system prevents the error entirely. Each level fails at a higher threshold. Mantras fail under cognitive load. Rules fail under pressure. Hooks fail when misconfigured. Systems, if designed right, don't fail at all.
The Tight Five is what mantras become when they graduate to systems.
Instead of remembering a phrase, you load a schema. Instead of relying on willpower, you have architecture. Instead of "I should remember to check all five dimensions," you have a frame that makes forgetting impossible. If any element is missing, you feel the gap the way you'd feel a missing prop in a scrum. The thing falls over.
This is why thinking deeply before the moment arrives matters more than willpower during it. A surgeon doesn't deliberate mid-incision. The deliberation happened in the years of anatomy, the thousands of practice cuts, the schemas loaded so deep they became instinct. The Tight Five is the same mechanism applied to decisions. You don't think through five elements under pressure. You loaded them before the pressure arrived. Now you act.
Standards compound. But only through this graduation. A phrase on the wall is decoration. A schema in working memory is architecture.
The Instrument
This isn't just philosophy. It's a product.
The Prompt Deck is a 5x5 alignment instrument. It helps people find their own five. Not by telling them what matters, but by running them through the structure until their five emerges. Three levels: Discovery pulls ideas. Strategic gives clarity on what and why. Tactical converts to action: five facts, five questions, five answers, five ideas, one decision.
Two modes. Pep Talk — the inner loop, selling yourself first. Pitch — the outer loop, aligning others to your vision.
The first and most important sale is always to yourself. If your own five doesn't hold, no pitch will save you. The inner loop maps directly to the outer: clarity produces consensus. Trust produces conviction. Leverage produces commitment. Conviction produces credibility. Agency produces capital. Capital is the last column because it's earned, not asked for. A system that demonstrates the preceding four can predict its own performance. Prediction is what capital buys.
The Time + Mind instrument is the complement. Prompt Deck answers what matters. Time + Mind measures whether you actually spent your attention on what matters. Together they close the gap between intention and reality.
The Fractal
The same five runs at four scales simultaneously. An agent processing a task. A person planning a week. A team shipping a feature. An organisation setting quarterly priorities. Same architecture. Different contents. Same binding. Different matter.
Misalignment at any scale produces dis-ease. Harmony produces flow. The navigation system diagnoses which scale is misaligned: Value tells you whether the work matters, Belief tells you whether the direction is grounded, Control tells you whether the levers work.
What works at one scale works at all. This is the fractal nature of schemas. A schema that organises your morning also organises your industry. The matrix that reveals gaps in a market also reveals gaps in a life. Each dimension you add to the grid is a new axis of void. More meta, more space to explore, more potential to discover.
The Loop
Static fives decay. That's the failure mode of every strategic framework ever built. Step 5 never happens. You create the artifact. It captures a moment of clarity. Then it freezes. The world moves. The artifact doesn't.
The VVFL is the antidote. Validated. Virtuous. Feedback. Loop.
Every Tight Five instance must revolve and evolve. The questions sharpen. The principles get tested against reality. The process gets stress-tested by friction. The platform absorbs what worked. The players grow. Each cycle compounds. Not just maintaining the five, but upgrading it.
The master loop: start with the question — what's the gap between intention and reality? Apply the principle — what truths filter noise from signal? Follow the protocol — what method closes the gap? Set the standard — what threshold defines success? Build the platform — what infrastructure makes the next cycle faster? Each pass produces a better question. The loop compounds.
Quality is prevention, not inspection. The loop that turns is the loop that learns. The loop that learns produces the predictions that earn trust. The tight five isn't a list you check. It's a loop you run. Each revolution either tightens the binding or reveals where the binding is weak.
The Choice
What five would you load right now?
Not abstractly. Not as a thought experiment. For the thing you're actually working on. The decision you're circling. The problem that's stalled. The conversation you're avoiding.
Which five elements, if you held them in mind simultaneously, would give you the clarity to act?
And which one are you leaving out — the one that would change everything, the prop that would stop the scrum from collapsing — because it's uncomfortable to include?
Load it. Bind it. Act.
That's the tight five.
Context
- Tight Five Prompts — The reference: all instances, the sequence, the binding
- Think Deep Act Quick — The triangle that feeds the five: questions, problem solving, decisions
- Matrix Thinking — The deep work tool: make the invisible visible
- First Principles — Nomenclature is the first principle of first principles
- Navigation System — Value, Belief, Control: the three systems deep thought calibrates
- Knowledge Schema — Schemas influence attention; the five you choose is the world you see
- Archetypes — The five processing modes: Dreamer, Engineer, Realist, Coach, Philosopher
- Mantras — What the Tight Five upgrades from
- Standards — Where protocols compound into predictability
- Quality Assurance — Deming: prevention over inspection
- VVFL Loop — Why the loop must be validated AND virtuous
- Close the Gap — Picture the dream, map reality, close the gap
- Routes — Schema selection is route choice: which five to carry?
- Flow — The Tight Five under pressure produces flow: compressed depth, not empty slogans
Questions
What makes five the right number — cognitive science, or the binding that prevents removal?
- If the architecture is constant but the contents are contextual, how do you know when you've loaded the wrong five?
- Where does the commissioning sequence break — is there a domain where Performance before Platform is wrong?
- The mantra-to-system graduation path assumes systems can be designed right — what happens when the system itself needs to evolve?
- Which prop are you leaving out of your scrum right now — and is it the one that would change everything?
The Tight Five is the schema. Dream Engineering is how ideas arrive to fill it.