Why the first session is so heavy
Three separate loads land on it at once. There's the work itself. There's the backlog, which is present as a vague, unquantified dread rather than as a number. And there's the self-assessment — sitting down means confronting how far behind you are, which is unpleasant enough that avoiding it is its own motivation.
Notice that only the first is actual studying. The other two are what makes the session feel impossible, and both can be handled separately. That's the whole strategy: unbundle the restart from the reckoning.
Day one: twenty minutes, no assessment
- 1
Pick the single easiest thing you own
Not the most important, not the most overdue. The easiest — a lecture you half-understand, a problem set you've mostly done, a chapter you find interesting. Importance is what you'll optimise on day five; on day one the only variable that matters is whether the session happens.
- 2
Set twenty minutes and stop when it rings
Stopping while it's still going well is deliberate. You want the memory of the first session to be "that was fine" rather than "that was exhausting", because that memory is what decides whether day two happens.
- 3
Do not look at the backlog
Not a glance at the missed lectures, not an audit of what's due. The reckoning is a separate task with its own slot, and doing it today converts a twenty-minute win into an evening of dread.
- 4
Write tomorrow's twenty-minute task on paper
One line. Specific enough that tomorrow-you doesn't have to decide anything, because deciding is the expensive part.
- 5
Stop. That's the whole day.
The temptation after a good twenty minutes is to do three hours and prove you're back. Resist it — the three-hour day is followed by nothing, reliably, and you're building a rate you can sustain rather than a gesture.
Days two to five: the same, slightly more
Twenty minutes becomes thirty, then forty-five. Add one session, not one hour. What you're rebuilding is the automaticity of sitting down at a particular time, and that's a function of consecutive days rather than of total hours — the finding underlying most of habit formation.
Keep the tasks easy for the full five days. It will feel like you're not addressing the real problem. You aren't, yet, and that's the plan.
Day six: the reckoning, done properly
Now quantify the backlog, in one sitting, with a pen. The dread is largely a function of it being unmeasured — an unknown quantity is infinite, and a list of nineteen items is finite and often smaller than the feeling suggested.
| Step | What you produce |
|---|---|
| List everything missed, one line each | A finite list. This alone reduces the dread substantially. |
| Mark each: examinable, assessed, or neither | Most items are neither. Those are already dealt with. |
| For examinable items, score exam weight 1–5 | A ranking. You now know what the top five are. |
| Draw a line under what fits in your available hours | An explicit abandonment list, in writing. |
| Schedule only the top three, one per week | A plan that is finishable, which is the only kind that gets followed. |
The abandonment step is not defeatism; it's the difference between a plan and a wish. How to catch up when behind goes deeper into the triage.
Don't rebuild the old system
Worth asking, before restoring everything exactly as it was: why did it stop? If the system required ninety minutes of processing every evening and you sustained it for four weeks, the honest conclusion is that it's too expensive, not that you're insufficiently disciplined.
- Cap the daily review queue so a week away produces a ten-minute return rather than a 400-card wall. Uncapped queues punish exactly the pattern you have.
- Cut the processing ritual in half. A forty-minute version that happens beats a ninety-minute version that doesn't.
- Delete rather than defer. The half-finished projects from before the break are mostly not coming back; formally killing them is a relief and frees the attention they were consuming.
- Add one weekly hour whose only job is repair — see the weekly review. Systems that assume failure survive it.
If the break was for a reason
Restarting after a holiday is a scheduling problem. Restarting after illness, bereavement, a mental health crisis or burnout is not, and applying scheduling advice to it produces guilt without producing sessions.
In those cases the twenty-minute rule still applies but the timeline doesn't — five days may be five weeks, and that's a normal recovery rather than a failure of the method. It's also the point to use the formal routes: extensions, mitigating circumstances, and the student support services that exist precisely for this and are consistently under-used. If the exhaustion predates the break and didn't lift during it, read student burnout before optimising anything.
The relapse
You will miss a day in the first fortnight. The thing that determines whether the restart survives is what you do on the day after, and the wrong response is doubling to compensate — that makes the next session heavier, which is precisely the mechanism that produced the original break.
Return to the plan at the normal size, and don't count the missed day as evidence about you. A restart that includes three missed days over a fortnight is a success; the alternative you're implicitly comparing it to isn't a perfect fortnight, it's another month of nothing.