How do you stop an urgent-feeling task from hijacking a plan to defer it to tomorrow?

What each one is actually for

Dialectical Behavior Therapy

DBT gives a person a short, repeatable move for the moment an urge outruns thinking — stop, step back, observe what's happening, then act only once the observing has happened. It's built for real crisis but works on any urge that arrives faster than a decision.

Do It Tomorrow

Do It Tomorrow protects a single rule: whatever arrives today, unless it's a genuine emergency, gets written on a fixed list for tomorrow instead of acted on now, so today's already-committed plan doesn't get rewritten by every new thing that shows up.

What you get out of pairing them

The rule is easy to state and hard to hold, because a new request rarely arrives as a neutral fact — it arrives with a spike of felt urgency attached, and the spike is what actually gets obeyed if there's nothing to catch it first. Having a specific move for that spike is what makes the rule something you can actually keep, not just something you know you should do. The fixed length of the list does something separate from that in-the-moment protection, too: an open list that anyone, including your own mind, can add to at any hour has no visible edge, so it can feel infinite no matter how much of it gets done in a day. A list that is only ever exactly tomorrow's tasks has a bottom you can see, which is a quieter relief than the moment-to-moment catch — less about surviving any one interruption, more about the list itself no longer feeling like something that grows faster than it shrinks.

What Dialectical Behavior Therapy rests on

• Acceptance reduces struggle randomised trials
  Allowing an internal experience to be present without resisting or acting on it reduces the psychological struggle that resistance would otherwise intensify.
• Affect labeling reduces arousal randomised trials
  Putting an emotion into words reduces the physiological and psychological intensity it would otherwise carry while unexamined.
• Cognitive reappraisal changes emotional response randomised trials
  Checking an emotional reaction against the actual facts of a situation can down-regulate a response calibrated to a threat that isn't really present.
• Pausing before reacting prevents escalation clinical practice
  Inserting a brief pause between an urge and an action prevents an impulsive reaction from escalating a crisis.

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.

Where they actually meet

Held side by side, the two rest on a related bet: that the thing pulling at you right now does not have to be obeyed right now. DBT's acceptance principle says an internal urge can be allowed to exist without being acted on, which is exactly what has to happen, felt in the body, before a person can write a demanding new task onto tomorrow's list instead of dropping everything for it.

The principle underneath both

A new demand and a rising emotion produce the same felt signal — do something, now — and neither the demand nor the emotion is actually asking to be obeyed on contact. Writing the demand down for later and letting the emotion be present without acting on it are the same move applied to two different kinds of pull.

What that makes the real goal

Protect a plan already committed to — today's task list, or a decision not to react — from being overridden by whatever shows up next simply because it showed up loudest. Put that way the goal belongs to neither method: a decision made in a calm moment needs protection against the version of you who meets the interruption, and anything that supplies it is doing the same work — a therapy skill, a task rule, or a sentence written on a card the night before.

Other practices that serve the same goal

A single daily 'capture window,' a fixed ten-minute slot for reviewing and re-sorting anything that came in during the day, carries anecdotal but widely reported support for the same target as Do It Tomorrow's deferred list — giving new demands a place to land other than immediate action. Cognitive defusion, a practice from acceptance-based therapies of noticing a thought as 'just a thought' rather than a command, carries mechanistic support for weakening the automatic link between an urgent-feeling thought and an immediate response. Once you can see that the pause and the list are doing one job at two different moments, a third move opens up, from the implementation-intention research this page already names: pre-commit to a specific cue paired with a specific response, so the behavior fires without a decision in the moment. Here that is one sentence, settled in advance — if a message lands while I am inside a work block, then I write one line on tomorrow's list and close the tab. It carries randomized-trial support for closing the gap between intending something and doing it, and it removes the step most likely to fail: deciding, mid-spike, whether this one counts.

A tradition that already does this

Do It Tomorrow's closed list has no named older tradition behind it the way some practices do — Mark Forster built the rule directly, as a working solution to his own overload, not as a modern translation of something centuries old. DBT's pause has the older lineage on this pairing: Marsha Linehan, who developed DBT, drew its pause-and-observe skills from her own Zen training, where noticing an urge before it becomes an action is a much older instruction than the clinical name STOP gives it.

Using DBT to steady Do It Tomorrow

Do It Tomorrow's rule is simple to state and hard to hold to, because a new request rarely arrives as a neutral fact, it arrives with a spike of urgency attached, and the spike is what actually gets obeyed. Before writing the incoming task on tomorrow's list, run DBT's STOP skill: stop what you are doing, physically pull back from the keyboard or phone, notice what the urgency in your chest is actually saying, and only then write the task down. Naming the feeling out loud, even one word, 'anxious,' 'a spike of I-have-to-answer-this-now,' uses affect labeling, DBT's finding that putting a feeling into words lowers its intensity, so the deferral is not just a paper move while the body stays braced to react.

Using Do It Tomorrow to steady DBT

DBT's distress tolerance skills tell a person what to do with an urge in the moment, pause, check the facts, ride it out, but they say nothing about what happens to the thing the urge was about once the moment passes, and an unresolved task left floating in memory can itself become a source of the next spike. Borrow Do It Tomorrow's closed list as the concrete landing spot: once a STOP pause has settled the urge to react immediately, the specific next move is writing the task, in one line, onto a fixed list for tomorrow, which turns 'later' from an open-ended promise into a bounded set the person already trusts will get looked at. Two details decide whether that landing spot actually holds. The line has to be specific enough that tomorrow-morning you knows what it means without reconstructing the situation, "reply to Dana re: budget numbers" rather than "Dana," which is a reminder that something is owed rather than a task. And the list has to be genuinely closed at the end of the day: if you can keep adding to tomorrow's page at eleven at night, then tomorrow is just another open inbox, and an urge does not settle when what you wrote it into has no edge.

9:40am, deep in a report, a Slack message lands marked urgent

You are forty minutes into a report due at noon when a coworker's message lands, all caps in your head even though the text itself is polite, and your hand is already moving toward the reply box. You stop, physically push back from the desk an inch, and notice the feeling is not really about the message, it is the familiar spike of 'if I don't answer instantly something bad happens.' You name it, quietly, 'urgency spike, not an actual emergency,' and the intensity drops enough that you can look at the message as a request rather than a fire. You write one line on tomorrow's list, 'reply to Dana re: budget numbers,' close the tab, and go back to the report. Whether any of it holds is decided the next morning. At nine you open tomorrow's list, which is now today's, and the Dana line is sitting third from the top. You reply. It takes four minutes. Nothing bad happened in the nineteen hours it sat there, and that is the piece worth registering on purpose, because an urgency spike does not learn from being overruled once — it learns from a run of instances where the feared thing did not arrive. Put a tick beside the line and two words, "no fallout."

When this is worth reaching for

A message lands mid-task carrying an urgency in its tone that the actual content doesn't support, and your hand is already moving to answer before you've checked which one is real. That gap between the felt spike and the actual stakes is the exact place a pause followed by a one-line deferral does more than either the pause or the list alone.

Where this does not apply

The pairing assumes the incoming pull is an urge worth pausing on, a task that only feels like an emergency. When the interruption is a genuine, externally time-sensitive event, a server actually down, a person actually in danger, DBT's pause skills are not built to slow down a response that legitimately cannot wait, and Do It Tomorrow's list is not the right container for it either. The two also have different native targets: DBT's skills were built for emotional crisis, not ordinary task overload, so a person whose problem is purely a messy calendar with no real emotional spike attached may get more scaffolding here than the moment needs. There's also a specific way the list itself fails that neither skill fixes. If the same one-line task shows up on tomorrow's list three or four mornings running, that's a different problem than the urgency spike this pairing catches — it's a sign the task is stuck: too large for one line, blocked on someone else's response, or something being avoided rather than deferred. Running the STOP skill and writing it down again for a fifth day does not fix a task that keeps correctly getting deferred and never actually getting done; a list entry that survives a week needs to be broken into a real next step or looked at directly, not pushed forward again.

What the evidence does and does not support

DBT's distress tolerance skills, including STOP and check-the-facts, carry trial support for their own targets, reducing crisis behavior and emotional escalation. Do It Tomorrow's deferred-list system as a whole is a widely used productivity practice with anecdotal support rather than controlled trials, but the specific relief a closed list produces has a real experimental result behind it, not just user testimony: a 2011 study by Masicampo and Baumeister found that simply writing a concrete plan for an unfinished task removed that task's intrusive pull on attention almost as effectively as finishing it, which is close to exactly what happens when a demand gets written down for tomorrow instead of left open in memory. Nobody has tested using DBT's pause skills specifically to support task deferral; this page describes a plausible mechanism, drawn from what each practice is built to do, not a tested combination. A trial of the pairing would have to measure something narrower than how people felt: whether the deferred task stayed deferred. Count how many one-line entries written under a spike were still on tomorrow's list at day's end rather than acted on within the hour, with one group taught the pause and one given only the deferral rule.