0/5
← The Operator’s Reset
── LAYER 04 · RADICAL TIME TRACKING ──
Measure Reality
“I do not know where my time goes.”
52 MIN FULL TRAININGREQUIRES CLAUDE CODE
── MEASURE REALITY WALKTHROUGH ──
Recording pending
The written layer is complete and stands on its own.
If you need persuading on why any of this is worth doing, go back to The Operator's Reset.
This document assumes you are already convinced and want to install it.
── WHAT THIS PRODUCES ──
A tracked window of real behavior, sorted into six decisions, with the ones that create work turned into tasks that have owners.
- Time
- 15 to 30 minutes to configure. After that, tracking happens inside your working day rather than alongside it.It is not a separate project. You are not carving out hours to run a time study. You are pressing start and stop while doing the work you were already going to do, and the review at the end is 30 to 90 minutes once.
- Diagnostic window
- 3 to 7 consecutive days.
── DEFINITION OF DONE ──
- Facts
- Every meaningful block carries a clean label under a scoring method you chose deliberately, with notes wherever the work got confusing or repeated or delayed.
- Feelings
- Clearer and less foggy rather than judged.
- Functionality
- Every meaningful activity sorted into one of the six decisions, with the ones that create work existing as real tasks and the ones that do not existing as written decisions. If the study does not change what happens next, it did not finish.
WHAT THIS COVERS · 31 CHAPTERS
- 01What actually breaks
- 02Two ways this runs
- 03Step 1: Pick your mode
- 04Step 2: Pick your tool
- 05Step 3: Learn the labels
- 06Step 4: Decide how you score a broken block
- 07Step 5: Run the study
- 08Step 6: Read the data
- 09Maker work and manager work
- 10The cost of a meeting is not its duration
- 11Three stages of calendar design
- 12Schedule manager work back to front
- 13When a maker block breaks, consider flipping modes
- 14Give meetings a standard territory
- 15The maker's no
- 16What managers owe makers
- 17Organisational quiet time
- 18Remote work needs output-based trust
- 19Count human hours, not meeting hours
- 20Your calendar is organisational evidence
- 21What to look for in the data
- 22Proactive before reactive
- 23The 168-hour principle
- 24Step 7: Decide what happens to each activity
- 25Step 8: Hand off what should not be yours
- 26A worked example, from the twelve days I actually tracked
- 27Allocation, and when to add it
- 28Reading your own data
- 29The API layer, optional
- 30By role
- 31Completion check
── THE TRAINING · ONE DOOR ──
Read the full training
The complete written layer, unabridged, in a focused reading view with its own outline. About 52 minutes.