Welcome — your access is confirmed. This is the full course. Bookmark this page; you can return to it any time.
The premise
Productivity advice usually optimises the wrong variable. It assumes the problem is speed — that you need to do more things per hour. For most people the actual problem is selection and protection: too much of the day is spent on work that would not have mattered even if it had been done perfectly, and the work that does matter gets the fragments.
This course works on four levers, in order of leverage: Selection (what earns time), Protection (how it gets defended), Execution (how the block is used), and Maintenance (how the system survives contact with a bad week).
Module 1 — Selection: deciding what earns time
Every hour is spent on something. The question is never whether you were busy; it is whether the busy was aimed. The sorting test below is deliberately blunt, because subtle prioritisation systems collapse under pressure.
The three-question sort
- Does this move a named outcome? If it does not connect to something you decided mattered, it is optional by definition — regardless of who asked.
- Would the cost of not doing it be real? Much routine work has an imagined consequence. Test it once by not doing it and observing what actually happens.
- Am I the only one who can do it? If not, it is a delegation or deletion candidate, not a scheduling problem.
The two-list exercise. List everything you did last week. Mark each item M (moved a named outcome) or N (did not). Total the hours in each column. The N total is your recoverable capacity — and it is almost always larger than people expect before they count.
Module 2 — Protection: defending the block
Selected work still has to survive the week. Protection is structural, not a matter of discipline.
- Schedule the important work first. Calendars fill from the outside in. Whatever is not blocked becomes available, and whatever is available gets taken.
- Give the block a real name. Vague labels get overwritten by other people and by yourself.
- Match hard work to your good hours. Most people have two to four genuinely sharp hours. Spending them on email is the single most common productivity error, and it is invisible because email feels like work.
- Batch the interruptible work. Messages, admin and small requests go into defined windows rather than being sprinkled across the day, where each one costs a re-entry.
Module 3 — Execution: using the block well
The entry ritual
Deep work has a start-up cost of roughly ten to twenty minutes. A fixed entry sequence — same place, same first action, notifications off, one written sentence stating what "done" looks like for this block — shortens it considerably, because the routine itself becomes the cue.
Defining done before starting
Open-ended blocks drift. Before beginning, write the completion condition: "a working draft of section two," not "work on the report." This gives the block an end and gives you a way to tell whether it succeeded.
Handling the interruption you generate yourself
Most interruptions during focused work are self-generated: a thought about something else. Keep a capture sheet next to you, write the thought down in five seconds, return. The point is not organisation — it is that written thoughts stop cycling, so you are not spending attention holding them.
| Block length | Best used for | Watch out for |
|---|---|---|
| 25–45 min | Defined tasks with a clear finish | Too short for work needing deep context |
| 60–90 min | Real cognitive work; the default for most people | Needs a genuine break after, not another block |
| 2–3 hrs | Complex synthesis, writing, building | Rare and expensive; protect ruthlessly, no more than one a day |
Module 4 — Maintenance: surviving a bad week
Every system meets a week that breaks it: illness, a crisis, travel. The systems that last have a documented reduced mode rather than an implicit collapse into nothing.
- Define minimum mode in advance. One protected block a day and the weekly review. Nothing else is required for the system to still count as running.
- Re-entry is a scheduled event. Book thirty minutes at the end of the bad week to reset the coming one. Without it, the recovery week is spent reacting.
- Do not compensate. Attempting to make up lost blocks by overloading the next week is how one bad week becomes three.
The weekly operating rhythm
| When | Duration | What happens |
|---|---|---|
| Friday or Sunday | 20 min | Review last week's M/N split; select next week's three outcomes; block them into good hours |
| Each morning | 3 min | Confirm the day's one non-negotiable block and its completion condition |
| Each evening | 3 min | Close the loop: capture open items, set tomorrow's first action |
The 30-day build
| Week | Install |
|---|---|
| 1 | Two-list exercise. Count your M and N hours. Change nothing else yet. |
| 2 | One protected block per day, in your best hours, named on the calendar. |
| 3 | Entry ritual and completion conditions. Batch messages into two windows. |
| 4 | Weekly review installed; minimum mode written down before you need it. |
Where this usually goes wrong
Optimising the tool instead of the selection
Reorganising the task manager feels productive and changes nothing. If the N column is large, no tool will help.
Blocking time you do not actually have
A calendar at 100% capacity produces guilt, not output. Block less than you think, and let the first month prove the number.
Treating the review as optional
The review is the only part that adapts the system. Without it, you are running a fixed plan against a changing week, which works for about a fortnight.
Do the two-list exercise before anything else. Almost everyone discovers that the constraint is selection rather than speed, which changes what the rest of the course is for.
Keys Personal Development School. Questions about your access: reply to your purchase receipt.