How to plan a week, not just a day
The short answer
The two levels do different jobs and confusing them is why weekly plans fall apart by Tuesday.
A week is where capacity becomes visible. It is long enough to see that eleven things do not fit in twenty-two available hours, and short enough that the estimate still means something.
A day is where the decision happens. It is the only level at which you know what is actually in front of you.
So a weekly plan that assigns specific tasks to specific days is doing the day's job a week early, with worse information. That is the mistake. By Wednesday reality has diverged, the plan is visibly wrong, and the natural response is to abandon it — when what was wrong was the resolution, not the planning.
What belongs at the week level
The three to five things that must be true by Friday. Not tasks — outcomes. The migration is live. The board pack is sent. This is the list you would name if someone asked what the week was for.
The total hours those need, added up. This is the entire value of weekly planning and it is the step people skip. Five outcomes at six hours each is thirty hours, and almost nobody has thirty hours of focused time in a week once meetings, messages and the unforeseen are taken out. Finding that out on Monday is worth more than any arrangement of tasks.
The fixed points. Meetings, deadlines, the day you are travelling. These are the walls the rest has to fit between, and they are known in advance.
What is waiting on someone else. Anything blocked should have its unblocking message sent on Monday morning, not discovered on Thursday. This single habit recovers more of a week than any scheduling technique.
What belongs at the day level
Everything else, decided that morning or the evening before.
Each day you take a small number from the week's outcomes and commit to them — three is a practical figure, because the constraint is what makes it a decision. What you take depends on what the day actually holds, which you could not have known on Monday.
That is the correct division: the week bounds, the day chooses.
The capacity arithmetic, done properly
Be honest about the denominator, because this is where weekly plans quietly lie.
A forty-hour week does not contain forty hours of focused work. Take out meetings, then take out the time around meetings that is too fragmented to use, then take out messages, then take out the thing that always arrives. What remains — for most people, most weeks — is somewhere between fifteen and twenty-five hours.
Plan against that number, not against forty. A week planned against forty hours fails in a way that looks like a personal failing and is actually an arithmetic error made on Monday.
If the outcomes need more than the honest number, the week is over capacity before it starts. That is information you can act on — cut scope, move something, tell someone — and it is only actionable while it is still Monday.
The review is the half that gets dropped
Fifteen minutes at the end of the week, and it is the part that makes the next one better.
- What did you plan, and what actually happened? Not to grade it. To find where your estimates are systematically wrong, which is usually a small and specific set of categories rather than everything.
- What did not get done, and why? Blocked, displaced, or never started — three different causes with three different fixes.
- What carried over, again? Anything on its third week is telling you something. It is usually one of four things.
Planning without reviewing is guessing repeatedly. The review is where the guess becomes an estimate.
Where to go next
- How to prioritise your tasks — the three conditions and which method each needs
- The Top 3 method — what the day level looks like
- How long should a task take? — the estimates the week arithmetic depends on
Using this in Decide One
Decide One works at the day, which is where the decision is. The weekly and monthly views show what actually happened rather than what was intended — planned against actual, which is the only honest input to next week's arithmetic.
A line you did not finish is unfinished. It is not marked against you, and a day you did not open is not counted.
Open Decide One — free to use, with no account. Nothing you write leaves your device.
Decide One is a priority instrument. Bring the day into view, choose a method, give the first thing real time.