The Ideal Week
What does your ideal week look like? How can you close the gap with reality?
The weekly review is the one cadence that makes everything else work. It shapes priorities and checks how closely your actions align with your stated intentions.
Ideal Week Template
An ideal week template is a standard protocol — a reusable pattern for time allocation that can be shared, measured against, and improved.
| Day | Theme | Archetype | Focus |
|---|---|---|---|
| Monday | Strategy & Operations | Philosopher | Direction setting, weekly plan, biggest problem first |
| Tuesday | Quality & Building | Engineer | Deep work, shipping, technical execution |
| Wednesday | Connection | Coach | Meetings, outreach, relationship building |
| Thursday | Sales & Product | Dreamer | Customer-facing work, pitching, product decisions |
| Friday | Financial & Review | Realist | Numbers, metrics, weekly mirror, admin close-out |
| Saturday | Question | All | Learning, exploration, reading, skill building |
| Sunday | Reflect | Narrator | Rest, weekly reflection, intention setting for Monday |
The template is a starting position, not a cage. Six hats, seven days — and a day of rest.
Tradable Templates
The 20-year idea: what if ideal week templates were open standards anyone could adopt?
| Property | What It Means |
|---|---|
| Specific | Named time blocks, not vague categories — "90 min deep work 6-7:30am" not "some morning focus" |
| Measurable | Plan vs actual tracked per block — the Weekly Mirror shows the gap |
| Shareable | Exportable format others can import and adapt |
| Evolvable | Version history — templates improve with data |
When someone shares a template that works, others gain a protocol they didn't have to discover from scratch. When many people use the same template and share results, the template evolves through collective feedback. Standards create abundance.
Calendar Is List
Sam Corcos: the problem with digital to-do lists is they create a false sense of infinite capacity. Your time is finite. Your list is not. The result is anxiety and drift.
The fix is structural: move every task directly onto the calendar with an assigned time block. Not "get to this eventually" — a specific block with a specific slot. When the calendar is full, the week is full. The constraint is honest.
| System | Capacity signal | Failure mode |
|---|---|---|
| To-do list | Infinite (false) | Things fall through the cracks unnoticed |
| Calendar | Finite (true) | You have to negotiate what actually fits |
Slack is not waste. Aim for 50% of your day open — not to leave work undone, but to absorb reality without cascading failure. Every unexpected task eats into unblocked time. Without that buffer, one disruption blows the whole week. As your estimation accuracy improves, you can reduce this to 25%.
Email is a to-do list in disguise. Treat each message as a task: assess the effort required, mark it as read, then schedule a specific block to address it. An unscheduled email is an unscheduled task.
Weekly Plan Protocol
Monday morning (or Sunday evening), 15-30 minutes:
| Step | Action | Artifact |
|---|---|---|
| 1 | Review last week's mirror (plan vs actual) | Patterns to carry forward or break |
| 2 | Check calendar for commitments | Fixed blocks go in first |
| 3 | Identify the week's 3 outcomes | Not tasks — outcomes. "Shipped X" not "worked on X" |
| 4 | Block deep work first | Peak energy hours protected before anything else fills them |
| 5 | Theme remaining days | Which archetype leads which day? |
| 6 | Set slack space | At least 50% unblocked — not waste, capacity |
Engineering Cadence
The driver's week carries a loop the engineering team feels every day. If the week has no rhythm, engineering drifts between idle and panic. A named touchpoint per day removes guesswork and keeps the pump loaded.
| Day | Engineering Touchpoint | Station |
|---|---|---|
| Monday | Scan the priority stack. Queue work two levels deep. | Hopper → Filter |
| Tuesday | Deep build. PR reviews. No new directives. | Pump |
| Wednesday | Open Debate on any pending plan. Run Accountability on last sprint. | Filter + Gauge |
| Thursday | Dogfood production against the stories. Post pass/fail with evidence. | Gauge |
| Friday | Weekly mirror. Extract one lesson. Update the loop itself. | Evolve |
Engineering never waits on the driver. Every Friday, one lesson must leave the week — logged, named, and folded into the next Monday's intake. A week without an Evolve step is a corrective loop at best; it never compounds.
Weekly Mirror
Friday afternoon or Sunday evening, 15 minutes. The Weekly Mirror answers: who were you trying to be, and who did you show up as?
| Dimension | Ideal Hours | Actual Hours | Gap |
|---|---|---|---|
| Deep work | ? | ? | ? |
| Connection | ? | ? | ? |
| Admin | ? | ? | ? |
| Learning | ? | ? | ? |
| Rest | ? | ? | ? |
The mirror is for pattern recognition, not judgment. Sunday Narrator writes in expressive form (Pennebaker): 15 minutes of continuous prose, no editing, answering:
- Where's the biggest gap? — That's where the system is weakest
- What stole time from deep work? — That's the enemy to defend against next week
- What pattern has repeated 3+ weeks? — That's structural, not accidental
- What did I not see coming? — That's the reception gap (feeds next week's overnight-question type ratio)
Continuous prose beats bullet-list reflection — narrative synthesis activates when the hand does not lift. Pennebaker's expressive writing research shows sustained 15-20 minute weekly practice produces measurable health and performance gains. Bullets filter; prose connects.
GTD Weekly Review checklist (David Allen): Get Clear (process inboxes), Get Current (review projects and actions), Get Creative (what new ideas deserve space?).
The Yield Metric
Dreamineering Yield = Artifacts Shipped ÷ Hours Invested
Not all hours are equal. The yield metric tracks whether your time allocation produces outcomes — not just activity. A week of 60 hours with zero shipped artifacts has a yield of 0. A week of 30 hours with 3 shipped artifacts yields 0.1 art/hr.
The ideal week template optimises for yield, not hours.
The Shadow
The perfect week that never happens. A template so beautiful it creates guilt instead of flow. The point is the gap between ideal and reality — that gap is information, not failure. Adjust the template to match what's actually possible, not what looks good on paper.
Plans are worthless, but planning is everything.
Context
- Perfect Day — The building block of the week
- Monthly Cycles — Patterns across weeks
- Standards — Why tradable templates matter
- Archetypes — The alter egos that lead each day
- Flow State — What the template is optimising for
Links
- The calendar is the to-do list — Sam Corcos on why to-do lists fail and how calendar blocking solves it
Questions
If your calendar is full but your outcomes aren't, what does that say about how you're converting time into results?
- What is the difference between a blocked week and a productive one — and how do you know in advance which you're building?
- If you kept 50% slack and still shipped the same outcomes, what does that tell you about the work you were doing with the other 50%?
- When a task slips off the calendar, do you reschedule it or let it disappear — and what does that pattern reveal?