Planning
When did you last step outside the loop to check if it's the right loop?
Planning is a feedback loop, not a to-do list. Review at the wrong cadence and you're either micromanaging yourself or discovering in December that January's plan was dead by March.
Review Cadences
Different time horizons demand different questions. The system that maps to each horizon determines what you review.
| Cadence | System | Question | What You Review | Tool |
|---|---|---|---|---|
| Within blocks | Control | Am I present? | Current mode vs chosen mode | State Switcher |
| Daily | Control | Did I protect deep work? | Intention vs attention, one thing | Time Oracle |
| Weekly | Belief | Am I on track? | Plan vs actual, pattern gaps | Week Calendar |
| Monthly | Belief | Am I building or drifting? | Weekly patterns over 4 weeks | Monthly Cycles |
| Quarterly | Value | Is this the right game? | Priorities, trajectory, identity | Quarter-Year |
The cadences nest. Daily reviews feed weekly mirrors. Weekly patterns reveal monthly trends. Monthly trends inform quarterly strategy. Miss a level and the ones below it lose meaning.
Ideal Week Templates
The 20-year idea: tradable best practices for time allocation. An ideal week template is a standard protocol — a proven pattern someone else can adopt, measure against, and adapt.
| Without Templates | With Templates |
|---|---|
| Reinvent the week every Monday | Start from a proven pattern |
| Drift into reactive mode | Default to intentional mode |
| "Where did the week go?" | "Here's what I chose and what happened" |
| Personal productivity stays personal | Best practices compound across people |
Templates become tradable when they're specific enough to follow, measured against reality, and shared as open standards rather than locked advice.
| Template Element | What It Defines |
|---|---|
| Day themes | Which archetype leads each day (Strategy, Building, Connection, Reflection) |
| Energy mapping | Peak hours protected for deep work, valleys for admin |
| Review slots | When daily close, weekly mirror, and monthly cycles happen |
| Flex space | Buffer for reality — no template survives contact with Monday |
The VVFL at Every Level
Each cadence runs the same loop at different speeds:
| VVFL Step | Daily | Weekly | Quarterly |
|---|---|---|---|
| Capture | Morning intention | Week plan | Quarter goals |
| Build | Deep work blocks | Execute against plan | Ship against strategy |
| Measure | Evening close | Weekly mirror (plan vs actual) | KPI review |
| Iterate | Adjust tomorrow | Adjust next week | Adjust priorities |
| Reflect | Think box | Pattern recognition | Is this the right game? |
Sustainability
Most review systems get abandoned. Research on why:
| Failure Mode | What Happens | Fix |
|---|---|---|
| Too heavy | 90-minute weekly review becomes a chore | Start with 15 minutes. Expand only when it earns its time. |
| No visible value | Review feels administrative, not generative | If the review doesn't change next week's plan, it's not working. |
| Skipped once, gone | Miss one week, guilt prevents restart | The cadence is a rhythm, not a streak. Resume without judgment. |
| Wrong cadence | Daily review for strategic questions, annual for tactical | Match the question to the time horizon. |
David Allen (GTD): the weekly review is the "critical success factor" — the one cadence that makes everything else work.
Why Plans Fail and Planning Works
"Plans are worthless, but planning is everything." Eisenhower said it. Burns said it earlier — the best laid plans of mice and men gang aft agley. Everyone quotes these. Nobody explains why both halves are true simultaneously.
Plans fail because they are predictions about a future that does not exist yet. Every plan assumes conditions that will change, dependencies that will shift, and information you do not have. The longer the plan, the more assumptions. The more assumptions, the more fragile. A 12-month plan is not a roadmap. It is a stack of guesses that compound in error.
Planning works because the act of planning forces discovery before creation. That is the mechanism. Not the document. The thinking.
| What Planning Forces | Why It Matters |
|---|---|
| Check what exists | Before building, you discover what's already there — duplicates, overlaps, prior work |
| Name your unknowns | The plan demands you list what you don't know BEFORE you hit it mid-execution |
| Sequence dependencies | You find that B depends on A, and C depends on B — before wasting time on C |
| Surface conditions | Prerequisites that seemed obvious turn out to be missing or assumed |
The plan is a forcing function. It makes you think about the work before doing it. The thinking changes what you do — even when the plan itself gets thrown out on first contact with reality.
Broken Plans Are Data
When reality contradicts your plan, you have learned something about your prediction model. The plan predicted X. Reality delivered Y. The gap is information.
| Response to Broken Plans | What It Produces |
|---|---|
| Abandon the plan, wing it | No model improvement. Same mistakes next time. |
| Force reality to match the plan | Rigidity. You build the wrong thing on schedule. |
| Update the model, replan | Better predictions next round. Calibration improves. |
The productive response to a broken plan is not abandoning planning. It is replanning — faster, with better information, informed by what just happened. Each replan is a tighter prediction. The cadence pages (day, week, month, quarter) exist because replanning at the right frequency is how plans survive contact with reality.
The Forcing Function
The most valuable thing a plan can do is prevent you from skipping a step that would have changed everything downstream.
A dependency graph does not just schedule tasks. It forces earlier phases to reshape later ones. Discovery before creation changes what gets created, not just how efficiently it gets created. A plan that forces you to check what already exists before building something new will catch redundancy before you waste weeks on it. A plan that forces you to define success before executing will catch misalignment before you ship the wrong thing.
The plan is not the sequence of steps. The plan is the structure that makes you think about the right things in the right order. That structure survives even when every step inside it changes.
The Shadow
Planning as procrastination. Perfecting the system instead of doing the work. Reviewing without changing anything. The most dangerous trap: an ideal week template so detailed it has no room for life.
Plans are worthless, but planning is everything.
Context
- Perfect Day — Daily intention and presence
- Perfect Week — The tradable template
- Monthly Cycles — Trend recognition
- Quarter-Year — Strategic recalibration
- Working Memory — The cognitive workspace planning protects
- Focus — What deep work blocks defend