The Stack Builder
Every habit tracker asks whether you did the thing. None of them ask how reliably the thing you attached it to actually happens — and that number sets a hard ceiling on the habit. This one does the arithmetic, which usually turns out to be the difference between a discipline problem and a scheduling fact.
Excel (.xlsx), seven sheets, and a 9-page PDF. No email, no signup, no drip sequence.
You probably do not have a discipline problem
That is not encouragement, it is arithmetic. Take a real example. You decide to spend twenty minutes on a side project when you get home from work. Sensible, specific, anchored. Over a fortnight you manage it four times, conclude you lack follow-through, and quietly drop it.
But “getting home from work” happened at a consistent, usable time on seven of those fourteen days. Your maximum was 50%. You hit 29% of a ceiling you never knew was there.
That is a design failure with a discipline failure’s reputation, and the two need opposite responses. More resolve does nothing about a 50% anchor. A different anchor fixes it in an afternoon. Most people have one genuine discipline gap and three design problems, and they spend all their effort on the wrong three.
What makes an anchor usable
An anchor is not just something you do. Three properties, and almost every failed stack is missing one of them.
It fires
Twelve days in fourteen, counted rather than remembered. Memory rounds up — everyone believes their morning routine is more consistent than the calendar says. Below about 85% you are attaching a habit to a coin flip.
It has a clear end
You attach to the end of an anchor, so it needs one. First coffee ends when the cup is empty. Getting home does not end — it tails off, and the attachment point drifts a little further each day until it is gone.
You are capable at that moment
An anchor can fire reliably, end cleanly, and still be useless because of what you are like when it happens. Attaching focused work to the end of the working day is a good design on paper and a bad one in a body.
One consequence worth acting on immediately: your most reliable moment of the day is probably carrying something trivial, out of habit. Moving the behaviour you actually care about onto your strongest anchor is the highest-return change available and it costs nothing.
Where stacks shed
Stacking works because the chain does the remembering. It stops working when the chain gets long enough that the chain itself becomes a thing you have to decide to do. The workbook reports adherence at position one against position three or deeper, and in most stacks the gap is enormous.
The useful part is what that tells you: the behaviours at positions three and four are not worse ideas than the one at position one. They are in a worse position. So the fix is not to try harder on position four — it is to move it onto a different anchor as a new position one, or to accept that this anchor carries two things and stop adding.
The other limit is time. A stack rides along on an existing routine; past about ten minutes it stops riding and becomes a separate activity you have to decide to start — which is the exact thing stacking was meant to remove. If it needs a decision, it is not stacked. It is a plan with a nicer name, and plans need calendars.
Four things people tell themselves
“I just need to be more disciplined.”
Usually means The anchor is weak and the arithmetic has never been done. The most common response to a design problem, and it produces months of effort against something effort cannot move.
Instead Fill in fourteen days of anchor ticks before deciding anything about yourself. If your ceiling is 64%, the 36% you have been calling a character flaw is a scheduling fact.
“I'll start again on Monday.”
Usually means The same stack, the same anchors, restarted with fresh enthusiasm. Enthusiasm is not a variable in the equation, so the second attempt produces the same number as the first.
Instead Change exactly one thing about the design first — the anchor, the position, or the length. Restarting an unchanged stack is how people learn that they cannot do this, which is not what they learned.
“It only takes fifteen minutes.”
Usually means Fifteen minutes is past the point where a behaviour rides along on an anchor. It now needs a decision, and it will lose to anything urgent, permanently.
Instead Shrink it until it does not need a decision, or move it out of the stack and into the calendar where it belongs. Both are honest. Leaving it stacked and failing teaches you nothing.
“My schedule is chaos, that's the problem.”
Usually means Correct, and also the point. A chaotic schedule means most anchors have low reliability — which is what the file measures, and why generic habit advice fails people whose weeks do not repeat.
Instead Find the one or two things that survive chaos. Almost everyone has at least one — waking, first coffee, the last thing before sleep. Those are your anchors. Everything else is scenery.
What is in the workbook
- Start Here
- The distinction the whole file exists to make, the colour convention, and one instruction about not looking at the numbers for a fortnight.
- Anchors
- The routines you already have. Tick the fourteen days each one actually happened. Computes reliability and grades whether it can carry anything.
- Stack
- One row per behaviour, attached to an anchor, with the same fourteen ticks. Computes adherence, your ceiling for that behaviour, the gap between them, and what is wrong with the row.
- Diagnosis
- Nine signals, including your ceiling and the split between design problems and discipline problems.
- Review Log
- Once a week, four lines. This is the Review step, and it is the one everybody skips.
- Thresholds
- What counts as reliable. Change them, but not on the back of one bad fortnight.
- Snapshot
- Seven numbers and three questions, if you want a second pair of eyes.
One instruction matters more than the rest: fill in the ticks daily and do not open the Diagnosis sheet for fourteen days. Checking the numbers every morning turns a measurement into a mood, and the mood is what makes people quit in week two. A stack cannot be judged on four days.
Why this is in a toolkit aimed at companies
Because the ceiling idea is fractal. A team’s operating cadence cannot beat the reliability of the person running it, for exactly the same reason a reading habit cannot beat the coffee it is attached to. In the Stack Assessment, personal discipline is layer one — underneath visible work, cadence, foresight and distributed ownership. Not because it matters most, but because it is underneath, and everything above it inherits its reliability.
This is the individual track of Habit Stacking. There is no commercial pitch attached to it — most people who use this will never speak to us, and the file works exactly the same either way.
The Stack Assessment
Which layer of your operating stack is actually holding, what you are maintaining on top of a gap, and which of the other files to open next.
Fifteen minutes →
The rest of the toolkit
Each one catches a failure the others cannot see. Run in the wrong order they still work individually and still under-deliver, which is exactly what the assessment exists to prevent.
The Operating Cadence
Whether the record keeps up with reality, or the board is a description of last Tuesday.
Workbook and field guide →
Measures ConcentrationThe Founder Dependency Audit
How much of the business runs through one person, and how long you could vanish before anybody outside noticed.
Workbook and field guide →
Measures ForesightThe RAID Log
Whether anything that goes wrong was ever anticipated, or every problem arrives as a surprise and gets handled well.
Workbook and field guide →
All of them are free and ungated, and listed at the toolkit index.
“Be consistent” cannot be checked, so when it fails there is only you to blame.
Most habit advice fails not because it is wrong but because it is unfalsifiable. Putting a number on the anchor makes the whole thing testable, and testable is what turns a personal failing back into a solvable problem.