Tool 29 of 32 · about an hour
Leading-Indicator Shield
Pairs every stream of invisible deep work with a visible number that buys it patience.
In Plan, from the Value-Source Audit's numbers, then reviewed weekly, indicator first, for as long as the deep work stays invisible.
What it is for
To pair every stream of invisible deep work with a visible number on the value engine, so the deep work is not killed at week six for having no pulse.
The failure it catches
Deep fixes are invisible while they are happening, and invisible work loses support, reliably, at around week six. The deep work does not get killed because it is failing. It gets killed because nothing visible has a pulse.
Why it works
The cheapest action that moves a real value number now, often almost trivial because it was the first thing dropped, puts a pulse on the wall. Reviewing that pulse before any progress narrative buys a stated number of weeks of patience. Honesty about how many weeks it buys is the decision that week six would otherwise force in a panic.
How to run it
- From the Value-Source Audit, take the one to three numbers that genuinely show the value engine breathing.
- Find the cheapest action that moves one of them now. It is often almost trivial, because it is usually the first thing that got dropped when times got hard.
- Pair every stream of deep work with the visible number that shields it.
- Review weekly, the number first, then patience for the deep work.
- Scope honestly: the pulse buys N weeks. If the fix needs more, that is a decision for the contract now, not at week six.
How to read the result
The indicator is on the wall and reviewed before any progress narrative, or the shield is not installed. The pulse is not the fix and must never be reported as the fix. The pulse buys time for the fix.
How to run it well
- Be honest about how many weeks the pulse buys. If the fix needs longer, decide that now.
- Pick numbers that actually show the value engine, not numbers that look busy.
Where it breaks
- A vanity number shields nothing, and a leadership watching the wrong pulse still panics on schedule.
- The pulse is not the fix. Reporting the pulse as if it were the fix is how companies lie to themselves with dashboards.
What would prove it wrong
Deep work killed at week six despite a live, business-nuanced pulse would mean the shield mechanism is weaker than claimed.
What we watch
Whether a live, business-nuanced pulse actually buys the stated weeks of patience, or whether week six still kills the deep work anyway.
Ask yourself
- Which visible number would show the value engine is still breathing while deep work is invisible?
- What is the cheapest action that would move that number now?
- How many weeks of patience does that pulse honestly buy, and is the deep work longer than that?
- Are you reviewing the pulse first each week, before the progress story?
Fed by: Baseline Vitals, Value-Source Audit, Definiteness Scoring
Feeds: Checkpoint Review