Quote
Busy is not productive. Productive is when today’s move still changes Friday’s scoreboard.
Here is the trap almost everyone walks into: a full week of real work that leaves the lag measure exactly where it was — because energy went to urgency, vanity metrics, and ten warm tasks instead of one lever. Productivity on the Codex is not more hours. It is one Battle, a lead measure you can still move today, quadrant-two time on the calendar, and five-minute daily rails that beat a heroic Monday that evaporates by Wednesday.
This map is priority, containers, and execution systems only. If the block is I sat down but scattered in minute three, open Focus (MoC); if the block is I never start the rep, open Habit (MoC); if it is hours logged but no correction, open Deliberate Practice (MoC); if the wrong self showed up, open Identity (MoC); if you cannot name the problem, step up one level at the foot.
What people get wrong
- More tasks equals more progress. A full week of quadrant-one firefighting can leave the lag measure unchanged.
- Measuring the scoreboard daily. The lag is yesterday’s news — calibrate the lead while there is still time to act.
- Diffuse sun. Many priorities at low heat warm nothing; one lens concentrates the week.
- Heroic Monday, empty Wednesday. A one-off decision without daily rails drifts by mid-week — see Diffuse-sun fight below.
- Efficiency without effectivity. Hitting the result while burning the system is still a loss over fifty-two weeks.
Read in this order
Short on time? Open 1 · Fast entry only.
1 · Fast entry
Open: Lag vs Lead Measure — write lag and lead on one line before you open the inbox. Start here when time is short.
2 · Weekly focus
Open: Battle Of the Week — one opponent this week, not ten warm tasks.
3 · Reset rhythm
Open: Weekly Review — convert last week’s noise into next week’s single signal.
4 · Triage science
Open: Eisenhower Matrix — important versus urgent before you schedule.
5 · Daily rails
Open: Personal Alignment System (SAP) — five minutes on the true domino beats a fog label and a heroic plan.
Go deeper
Optional depth — eight blocks below. Inbox owns the calendar? Quadrant-two fight first. Many projects at low heat? Diffuse-sun fight. Goals stay vague? Evidence papers row. Short on time? Put it to work or skip to Your move.
Shelf anchors
Kind Note Why open it Core volume First Things First Roles and mission before task volume Core volume Eat That Frog Highest-resistance task while attention is fresh Core volume Atomic Habits Systems, cues, and review when busy looks like motion Canon spine Behavioral change canon Five pillars — read in place, do not copy
Lineage threads
Fight shape Open Shortcut feels like truth under uncertainty Heuristics and biases lineage Prosperity lore needs historical placement New Thought lineage
Evidence papers
Steps 2–4 above — weekly containers and triage. Add paper depth when goals stay vague or willpower feels depleted:
Paper Open when Locke 2002 Goal setting task motivation Goals stay vague — specific + feedback beats intention Baumeister 1996 Self-regulation failure overview Competing goals drain standards and monitoring
Quadrant-two fight — shelf to move
When urgency drowns importance (triage science above):
Step Layer Note Move 1 Book Shelf anchor · First Things First Name roles before tasks 2 Atlas 4 · Triage science above Label quadrant before schedule 3 Doctrine 1 · Fast entry above Lag and lead on one line 4 Doctrine 3 · Reset rhythm above Block one quadrant-two slice this week
Diffuse-sun fight — shelf to move
When many projects at low heat (nothing compounds):
Step Layer Note Move 1 Doctrine 90-90-1 One priority · ninety minutes · ninety days 2 Atlas Cumulative effect Compound needs a protected slice 3 Doctrine 5 · Daily rails above Five minutes beats hero Monday 4 Doctrine 2 · Weekly focus above One Battle — not ten opponents
Put it to work
Lever: Tipping point — one muscle the week must train.
Filter: Signal vs Noise — one signal in, one explicit no.
Cost: Efficiency vs Effectivity — score the result and the drag.
Score: productivity score — 1–10 after the block + two honesty questions.
Dictionary: Social performance vs self-authored score — write your Life Performance before borrowing hours-as-virtue.
Recovery: recovery system — protect the reset stack so the container survives the season.
Evening: OTT — plan tomorrow before sleep closes the day.
Trigger: Proaction vs Reaction — install the move before Monday owns you.
Rails: Personal Standards — non-negotiables that make the container reachable.
Mechanism — measure, drift, and zones
Note Open when Lead Measure Agency lives in today’s move Lag Measure Read the scoreboard after the week Vanity Metric The number feels good but cannot be steered Drift and Sedimentation Busy forward motion while rituals erode Context design Shape cues so the lead rep is the easy path Decision hygiene Separate analysis from who signs Zone of Genius Protect hours that compound Zone of Incompetence Remove work from your direct execution layer
Evening stack
Run OTT three nights: Battle line · two deliverables · one boundary — notice how the morning lands.
Your move
Write your Battle’s lag and lead on one line. Block one lead rep in the next twenty-four hours before you re-check email — the rep, not the mood. Log whether you moved the lead or only read the lag.
Need the wider picture? Step up to Self-Architecture (MoC).