Coming back after time away
The short answer
Do not rebuild the old plan. Start today.
The instinct after time away — a week, a month, longer — is to reconstruct where you were and resume from there. It rarely works, because the plan was written against a world that has moved, and because reconstructing it is a large, vague, unrewarding task standing between you and any progress at all.
The thing that works is smaller and slightly uncomfortable: pick three things for today and do them. Not to catch up. Just today. Catching up is not a task and cannot be started.
Why the old plan is the wrong thing to restore
It is out of date in ways you cannot see. Some of it is done, some is irrelevant, some was overtaken. Sorting that out is itself hours of work, and it produces no output.
It is the wrong size. A plan built during a normal stretch assumes a normal amount of context loaded. On the first morning back you have none of that, and the honest capacity is lower than usual.
It puts a large reconstruction task first, on the day when starting anything is hardest. That is the opposite of what a first day back needs.
Keep the old list — it is a useful record of what once mattered. Just do not make reading it the first thing.
The first morning, concretely
- Write down what is in your head, for ten minutes, without sorting it. Everything you are half-remembering costs attention while it is unwritten and nothing once it is down.
- Find what is on fire, if anything. Usually less than feared, and usually two things rather than twenty.
- Send the unblocking messages. Anything waiting on you that someone else is stuck behind. Short, one ask each. This buys back more of the week than anything else you could do before lunch.
- Pick three things and give them times. Only today. Three is small enough to bind, which is the point.
- Leave the backlog alone until tomorrow. It will still be there and it will read better when you have one finished day behind you.
About the gap itself
Worth saying plainly, because most software gets this wrong and it matters.
A day you did not open is a day you did not open. It is not a failure, it is not a streak broken, and nothing about it needs to be made up. An unfinished task from three weeks ago is unfinished — a description, not a verdict, and the calendar moving on does not turn one into the other.
If a tool greets you after a month away with a wall of red, it has decided something on your behalf that it has no standing to decide. That is a design choice, and it is the wrong one. The test any returning screen should pass: could this make someone feel bad on a day they had a bad day?
The useful question on the way back is not what you missed. It is what matters now — and that is answerable this morning, in ten minutes, without reconstructing anything.
The second and third day
Day two, look at the old list properly. With one completed day behind you it reads differently: most items are obviously stale, a few are obviously live, and the sorting takes twenty minutes rather than feeling infinite.
Day three, go back to whatever your normal planning is. Not before — the first two days are for getting moving, and normal planning assumes a context you have not rebuilt yet.
Anything still on the list after a week away and a week back is worth a proper look. It is usually one of four specific things, and none of them is a discipline problem.
Where to go next
- The Top 3 method — three things for today, and no fourth
- What to do with a task you keep postponing — for what survives the return
- How to prioritise your tasks — once you are moving again
Using this in Decide One
Decide One is built for exactly this morning. A person returning after a month finds a clean day rather than an account of their absence — that is a deliberate decision, recorded in the product's own vision document, and it is the reason there are no streaks anywhere in it.
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.