Tukuk-OSWhy plans die on Wednesday
A study plan usually fails for one of three boring reasons. It front-loads: Monday gets five heroic hours because Monday-you believes in Monday. It ignores collisions: the plan has no gap for the assembly, the match, the bad night. And it has no rule for failure — when a day collapses, the session is deleted instead of moved, the backlog silently grows, and the plan is abandoned by the evening it first needed to bend.
The fix is not more discipline. It is a smaller plan with a load-bearing structure: rank what is due, spread what remains, cap each day, and count what actually happened on Sunday.
Step one: decide what tonight is for
Deadline order is a trap — the essay due Friday quietly eats the week while the problem set due tomorrow waits behind it. The honest ranking divides each job's effort by the days left around it: pressure per day. A task that feels like a 4 with three days left is a 1.3-per-day; a 2 due tomorrow morning is a 2-per-day, and tomorrow morning wins. List every assignment as name | days left | effort 1-5 and let an assignment prioritiser do the division and hand back the work order — with a concrete first move for each line, because knowing the order is only half of starting.
Effort is a ten-second guess and it is usually within one sitting of the truth; the guess itself is the point, because it names the thing you are avoiding.
Step two: spread the subjects instead of stacking them
Now the recurring load: subjects and the hours each honestly needs per week. The default instinct is blocked practice — all of one subject until it is done — which feels efficient and fades fastest. Interleaving spreads the same hours so every subject is re-met just as it starts to slip; the spacing research says the mixed schedule wins, and the companion article on spaced repetition explains why.
Type Maths | 4 style lines into a weekly study grid and it round-robins the subjects across the days with a deliberate cap: three one-hour sessions a day, no more. The cap is doing two jobs — it keeps quality above the point where focused recall collapses in a school day, and it guarantees the grid always leaves room for the unexpected, which is the difference between a plan that survives February and a poster on the wall. When a day collapses, the rule is printed under the table: move the session, never delete it.
Step three: run the session, then count the truth
Inside the session, one timer does the arguing: 25 focused minutes, five off — a pomodoro timer keeps the count so you can stop negotiating with yourself every ten minutes.
And on Sunday, one honest number ends the debate about how much you "basically" studied. Keep a line per session as you go — 2026-11-05 | Maths | 45 — and paste the week into a study log: totals per subject, average per study day, and the quiet discovery that History got nine minutes again. Everyone's felt sense of a study week is wrong in the same direction — the comfortable subject swells, the dreaded one shrinks — and the log is the cure, because it counts what happened instead of what it felt like.
The week that bends
The structure is four tools and ten minutes: the prioritiser says what tonight is for, the grid says what the week looks like, the timer says when to stop, the log says what actually happened on Sunday. Nothing in it requires a perfect week — it requires a plan whose failure mode is move, not abandon. Plans that survive are not the ambitious ones; they are the ones with a rule for the bad night.