Stop Letting Today's List Eat Tomorrow's Rest
And how Deliberate Rest sharpens Do It Tomorrow in return.
Do It Tomorrow, the system Mark Forster built around a single rule, works by closing today's task list the moment you start working it: whatever new thing shows up during the day, an email, a request, an idea, gets written onto tomorrow's list instead of today's, so the list you're actually executing stays exactly what you committed to that morning rather than growing every time something new lands in front of you. Deliberate Rest, drawn from Alex Soojung-Kim Pang's research into how highly productive people across history actually structured their days, treats real recovery, a short workday, a nap, a walk, a substantial hobby unrelated to work, as a scheduled, protected part of demanding work rather than whatever time happens to be left over once work is done. Put side by side, both practices are defending the same kind of boundary from opposite ends of a day: Do It Tomorrow keeps the day's work from silently expanding past what you agreed to that morning, and Deliberate Rest keeps the recovery afterward from being the first thing sacrificed when the day runs long anyway. Neither boundary holds without the other; a closed list that just frees up time for more unscheduled work protects nothing.
What each one is actually for
Do It Tomorrow
Do It Tomorrow is built around one specific mechanical rule that's easy to state and surprisingly hard to actually follow: once you begin working through today's list, the list is closed, nothing gets added to it for the rest of the day, no matter how urgent it feels when it lands. A new task, request, or idea that shows up at 11 a.m. doesn't get squeezed into today, it gets written down on tomorrow's list, which you haven't started yet and which is still open to receive it. This sounds like it would just delay everything by a day, and in a narrow sense it does, but the actual effect is different: because today's list can never be silently expanded by whatever interrupts it, the amount of work you're actually accountable for finishing today is fixed and knowable from the moment you start, rather than an open-ended target that keeps moving as the day goes on.
Deliberate Rest
Deliberate Rest starts from a specific historical observation Pang documents at length: a striking number of people who produced enormous amounts of high-quality creative and scientific work, Charles Darwin among them, actually worked far fewer hours in a literal sense than modern expectations assume, often four or five focused hours a day, protected by firm stopping points, long walks, regular naps, and substantial time given to activities entirely unrelated to their main work. The practice, distilled from that pattern, is to treat recovery activities as deliberately scheduled and defended, not as whatever's left after work finishes, on the argument that the recovery isn't separate from the productive output, it's a structural part of what makes the next stretch of focused work possible at anywhere near full capacity. A short workday with a genuine hard stop and a protected walk afterward isn't slacking on this account; it's closer to how the output actually got produced in the first place.
What you get out of pairing them
What Do It Tomorrow buys you is a work day with an actual edge, one that can't quietly balloon into an unbounded, ever-growing list one interruption at a time, which removes a specific, exhausting kind of overwhelm, the feeling that the list is never really done because it keeps changing shape underneath you as you work it. What Deliberate Rest buys you is sustained output across months and years rather than a short intense burst followed by a crash, and, less obviously, actual problem-solving you cannot force by sitting at the desk longer, since stepping fully away from a hard problem lets background mental processing continue on it in a way that continued, effortful focus on the same problem tends to block. Put together, the thing each buys you turns out to protect the other: a closed list is what makes it possible to actually stop at a defined point rather than working until exhaustion decides for you, and real rest afterward is what keeps tomorrow's closed list something you can actually execute at full capacity rather than a fixed amount of work attempted on a depleted brain.
What Do It Tomorrow rests on
-
Implementation intention closes intention action gap
randomised trials
Pre-committing to a specific situational cue paired with a specific response lets the behavior fire automatically when the cue occurs, without depending on in-the-moment willpower.
-
Closed lists reduce overwhelm
practitioner report
A fixed bounded list of tasks rather than an ever-growing open list reduces the felt overwhelm of an infinite to-do list.
-
Deferred capture protects commitment
practitioner report
Writing newly arriving tasks onto tomorrow's list rather than acting on them immediately protects today's already-committed plan from being derailed by reactivity.
What Deliberate Rest rests on
-
Incubation aids problem solving
observational studies
Stepping away from focused, effortful work into unrelated activity lets unconscious incubation continue, aiding problem solving and creativity.
-
Recovery enables sustained performance
observational studies
Protecting structured recovery time between periods of effortful engagement sustains high performance over time rather than merely pausing it.
Where they actually meet
Both practices are defending against the same belief, from opposite ends of a day: that more automatically produces more, more tasks squeezed onto today's list, more hours logged at the desk. Do It Tomorrow answers that belief by refusing new tasks entry into today no matter how urgent they seem in the moment they arrive. Deliberate Rest answers it by refusing to let a long day quietly cannibalize the walk, the nap, or the hard stop that was supposed to happen regardless of how much got finished. Each practice puts something deliberately outside a boundary, new tasks go to tomorrow, real rest goes on the calendar, on the shared premise that protecting the boundary is precisely what makes the work inside it trustworthy day after day, rather than a one-time act of discipline that erodes the moment things get busy.
The principle underneath both
Real output over a stretch of time, a day, a week, a working life, comes from two components acting together, a period of genuinely committed focused effort and a firm boundary that keeps that effort from being stretched past what an actual person can sustain without their capacity quietly degrading. Protecting the boundary, closing a list, ending a workday, holding a scheduled rest, is not time taken away from the effort; it's what keeps the effort itself reliable enough to still be there tomorrow, instead of being spent all at once today and unavailable when it's needed again.
What that makes the real goal
If a protected boundary on both ends is what makes effort sustainable, then what both practices are actually building toward is a system you can trust to produce again tomorrow, not just a plan that gets you through today. That's a different target than simply finishing everything currently in front of you, which a completely open list and an unprotected evening both allow you to attempt, right up until the day it doesn't work anymore. The objective is closer to reliability across many days than maximum output on any single one, on the reasoning that a plan which quietly costs tomorrow's capacity to satisfy today's list isn't actually more productive, just differently distributed.
Other practices that serve the same goal
The Pomodoro Technique pursues the same objective at a much smaller scale, building short mandatory breaks directly into a single work session rather than only at the level of a full day, with its own body of practitioner and some experimental support for sustaining attention across a longer stretch of work. Cal Newport's shutdown ritual, a fixed short routine that formally closes out a workday, functions like Do It Tomorrow's closed list applied to the end of the entire day rather than to new incoming tasks specifically, defending the same boundary from a slightly different angle. Periodization in athletic training, where planned recovery weeks are built directly into a training program rather than added only once fatigue forces the issue, rests on well-established sports science showing that measurable strength and endurance gains occur during the recovery period, not during the exertion itself, a close athletic parallel to Deliberate Rest's core claim.
A tradition that already does this
Pang's own research for Deliberate Rest turns up historical figures who were already, in effect, running something close to a closed list alongside their protected rest, a firm, early stopping point for the day's actual work, after which the rest of the day was genuinely off-limits to new work demands rather than available to whatever came up. The two named systems here weren't built together, Forster's list-closing rule and Pang's historical argument for scheduled recovery come from entirely separate projects decades apart, but the pattern this page describes, a bounded work period defended on both sides, is one that shows up on its own in the working lives Pang actually studied.
Using Do It Tomorrow to protect Deliberate Rest from the day's own momentum
The most common way scheduled rest actually gets skipped isn't a conscious decision to skip it, it's the day running long because something new landed at 4 p.m. that felt urgent enough to handle before the walk or the stopping point that was supposed to happen at five. Do It Tomorrow's closed-list rule is a direct defense against exactly that failure: once today's list is closed, that 4 p.m. arrival doesn't get to compete for a slot in today's remaining time at all, it goes straight onto tomorrow's list, which means it structurally cannot be the reason today's protected rest gets cut short. Applying the rule with the day's stopping point specifically in mind, treating the walk, the nap, or the hard stop as part of what today's closed list is protecting, not just the visible tasks on it, turns Do It Tomorrow from a productivity rule into something that also directly defends the recovery half of the day.
Using Deliberate Rest to make Do It Tomorrow's closed list something you can actually keep closing
Do It Tomorrow's rule is simple to state and genuinely hard to follow under fatigue, because a tired, depleted state makes almost everything feel urgent enough to justify breaking the rule just this once, and one broken closure tends to make the next one easier to break too. Deliberate Rest addresses the actual cause rather than the symptom: a person who has protected real recovery, a walk that actually happened, a stopping point that actually stopped, has more of the specific capacity that resisting an urgent-feeling interruption requires than a person running on an unprotected, ever-extending day. Treat the rest not as a reward for having kept the list closed, but as the thing that makes keeping it closed possible again tomorrow, which reframes a missed walk or a skipped stopping point as a direct threat to tomorrow's discipline, not a harmless one-off.
The email that arrives at 4:40, ten minutes before the walk
You're closing out the last item on today's list when a message lands that reads as genuinely time-sensitive, a client asking for something by end of day, worded in a way engineered to make anything except immediate action feel irresponsible. Today's list closed at 9 this morning, and the scheduled walk at five, sitting right there on the calendar since Sunday, is the one thing standing between you and just answering it now and seeing where the next hour goes. You write the request onto tomorrow's list instead, at the top, where it will be the very first thing you see, and you say so in a two-line reply, that you'll have this to them by tomorrow morning. It does not feel urgent to write those two lines; it feels like it might disappoint someone. You go on the walk anyway, mostly on the strength of the rule rather than any calm you're currently feeling, and somewhere around the second block the version of you that was about to answer that email at 4:41 has quieted down enough to notice tomorrow morning was always going to be soon enough.
When this is worth reaching for
Days are genuinely interrupt-driven — new requests or ideas arrive constantly enough that an open list would grow all day regardless of how much gets finished — and there is at least some control over when the workday actually ends. That combination of conditions is where this pairing is most useful. It matters least for work with a small, stable, well-defined set of daily tasks that rarely gets interrupted, where neither a closed-list rule nor a hard-won recovery boundary is defending against much of anything in the first place.
Where this does not apply
A genuine emergency, one with real consequences for delaying a day, is not a candidate for either rule; Do It Tomorrow's own rule assumes ordinary work interruptions, not situations where waiting actually causes harm, and no scheduled walk should take priority over handling something that can't wait. This pairing also doesn't fit someone in a role with hard external deadlines set by other people on a short cycle, court filings, live event production, where the list genuinely cannot be closed on your own schedule regardless of what either practice recommends. And a single unusually demanding day or week, a product launch, a family emergency, is not the moment to introduce either rule for the first time; both work best as an ongoing habit, not a first-time experiment during the exact week least suited to experimenting.
What the evidence does and does not support
Deliberate Rest's core claims rest mainly on Pang's own historical case studies and a smaller body of observational research on recovery, incubation, and creative problem-solving, evidence that is suggestive and consistent rather than the product of controlled trials measuring the practice as a defined intervention. Do It Tomorrow's closed-list mechanism has essentially no formal research behind it at all, its support is almost entirely anecdotal, from Forster's own writing and from practitioners who've adopted it, though the general principle that pre-deciding a response reduces reliance on in-the-moment willpower does have separate experimental backing under other names. No study has tested running these two specific named systems together, or measured whether a closed list actually makes scheduled rest more likely to survive a demanding day; the connection drawn here is a reasoned one between two practices that are each, on their own evidentiary terms, more lightly tested than their popularity might suggest.
Practice this with IX Coach
The two practices on their own
Other pairings with these practices
- 168 Hours Time Audit and Deliberate Rest
A time audit can misread protected recovery as wasted hours — deliberate rest gives that time a category so it survives the cut, on this reading.
- 168 Hours Time Audit and Do It Tomorrow
The audit shows how much of a week gets eaten by requests you answered the moment they landed. Do It Tomorrow is the rule that stops the eating.
- 90-Second Rule and Deliberate Rest
The body clears a strong emotion in about 90 seconds if left alone. Structured rest between work blocks may run on a similar logic.
- Action Planning (Implementation Intentions) and Deliberate Rest
Rest fails for the same reason follow-through fails: nothing decides it in advance. An if-then plan aimed at recovery, on this reading, fixes that.
- Action Planning (Implementation Intentions) and Do It Tomorrow
Mostly yes, and that is worth knowing plainly. One honest reading of what naming the mechanism does and doesn't add to the method.
- Attention Management and Deliberate Rest
A break spent half-watching your phone recovers almost nothing. Attention management can turn scheduled rest into rest that actually restores focus.
- Attention Management and Do It Tomorrow
A closed list stops new demands from landing on today. It does nothing about the pull that starts inside your own head twenty minutes later.
- Behavior Design (Environment Design) and Deliberate Rest
The same default that decides whether you start working also decides whether you actually stop. On this reading, one lever explains both failures.
- Behavior Design (Environment Design) and Do It Tomorrow
The rule is simple to state and easy to break the second a task lands. On this reading, capture friction, not willpower, is where it actually fails.
- Calm Company Design and Deliberate Rest
A calmer team culture only helps if the hours it frees up actually become rest instead of more work packed into the same day.
- Collaborative Problem Solving and Deliberate Rest
Resistance to a break and resistance to a rule can be the same signal in different clothes. A way to read one using the other, honestly limited.
- Collaborative Problem Solving and Do It Tomorrow
A task that keeps moving to tomorrow's list night after night isn't a scheduling failure. Here's what Collaborative Problem Solving says it usually is.
The principles underneath both
- implementation intention closes intention action gap
Pre-committing to a specific situational cue paired with a specific response lets the behavior fire automatically when the cue occurs, without depending on in-the-moment willpower. Shared by 28 practices in the corpus — here in 50/30/20 Budget Rule.
- incubation aids problem solving
Stepping away from focused, effortful work into unrelated activity lets unconscious incubation continue, aiding problem solving and creativity. Shared by 2 practices in the corpus — here in Focused vs. Diffuse Thinking.
- recovery enables sustained performance
Protecting structured recovery time between periods of effortful engagement sustains high performance over time rather than merely pausing it. Shared by 2 practices in the corpus — here in Digital Sabbath.