Why Does the Same Task Keep Getting Pushed to Tomorrow's List?

What each one is actually for

Collaborative Problem Solving

Collaborative Problem Solving starts from a specific claim: a person who keeps not doing something is not, on this account, simply being lazy or defiant. There is usually a specific, nameable obstacle in the way, and the method's job is to find it out loud rather than guess at it or punish around it. In practice it means sitting down away from the moment of friction and walking through three steps in order: state what has been noticed, plainly and without blame ('this has been on the list four nights running now'), ask what is actually making it hard, and then build a fix together that the person with the problem had a real hand in shaping, rather than one handed down to them.

Do It Tomorrow

Do It Tomorrow, a method from productivity writer Mark Forster, has one deliberately narrow rule: when a new task arrives, whatever it is, an email, a request, an idea, it does not go on today's list. It goes on tomorrow's. Today's list was closed and committed to yesterday, and nothing gets added to it partway through the day no matter how urgent it feels in the moment. The list itself is also a closed set rather than an ever-growing pile — once tomorrow's list is written, new arrivals during tomorrow go onto the day after that, so no single day's list can balloon past what a person can actually do. You can picture the mechanics directly: a page for today, a page for tomorrow, and a firm rule about which page a new thing is allowed to land on.

What you get out of pairing them

If you have ever watched the exact same line item survive four, five, six nights of rewriting itself onto tomorrow's list, the honest question worth asking is not 'why am I so bad at this' but 'what is actually stopping this.' Do It Tomorrow's list, on its own, has no way to ask that question — its whole design is to defer cleanly, not to diagnose, so a genuinely stuck task and an ordinary one that simply has not come up yet look identical on the page. What CPS's method hands you is a way to tell them apart and do something about the one that is actually stuck: a short, specific conversation, with yourself or with someone else, that turns four nights of silent rewriting into one afternoon of naming the real obstacle and building an actual way past it.

What Collaborative Problem Solving rests on

• Externalizing makes pattern visible randomised trials
  Putting an internal pattern into an external, structured form makes it visible and available for examination instead of remaining implicit and merely enacted.
• Parts have positive intent clinical practice
  A behavior that looks like misbehavior is usually a mistaken strategy aimed at meeting a legitimate underlying need rather than an expression of badness itself.
• Collaborative solution generation increases buy in observational studies
  Jointly generating a solution with the person who has the problem produces more durable follow-through than an imposed solution.

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

Both practices treat a recurring behavior as a signal worth reading rather than a fault to correct on the spot. Collaborative Problem Solving starts from the idea that a behavior read as defiance or misbehavior is usually a mistaken strategy for meeting a real need the person cannot yet name, so the response is to jointly diagnose the actual unsolved problem instead of punishing the surface behavior. Do It Tomorrow starts somewhere far more mundane, a task list, but the same move is available inside it: when one task gets written onto tomorrow's list, then tomorrow's, then the next day's, that pattern of repeated deferral is itself an external, visible signal, in the same way CPS treats an outburst as a signal, that something about the task is genuinely unsolved rather than merely unscheduled. What was, on either account, read as a discipline problem, a defiant kid, a procrastinating adult, becomes instead a diagnostic clue pointing at a specific obstacle a plain schedule or a plain consequence cannot reach.

The principle underneath both

A task or a behavior that keeps not happening is not, by default, evidence of unwillingness. It is a repeated data point, and repetition is what turns an ordinary delay into a signal worth stopping to read. CPS reads that signal in a raised voice; Do It Tomorrow's list reads it in a line of text that will not stay crossed off. Neither practice asks you to trust your general impression of the pattern — both make you count it, on paper, before deciding what it means.

What that makes the real goal

Underneath either method the actual target is the same: tell apart a thing that has a real, specific obstacle in front of it from a thing that simply has not been gotten to yet, and stop treating both as the identical failure of discipline. Once that distinction exists, the stuck ones get a different kind of attention, a conversation about the obstacle, rather than another round of the same ineffective push. That target holds regardless of which method surfaced the stuck item first.

Other practices that serve the same goal

The Eisenhower Matrix, which sorts tasks by urgency and importance into four quadrants, gets at a related distinction, what actually matters versus what only feels pressing, but has no mechanism at all for noticing repeated deferral specifically; a genuinely important task can sit in the 'important, not urgent' quadrant indefinitely without the matrix ever flagging why. David Allen's Getting Things Done asks for a weekly review where every open item gets looked at again, which will eventually surface a stuck task through sheer repeated exposure, though it relies on the review actually happening rather than building the flag into the daily list itself. A simple visible tally mark, one small mark next to a task each time it gets rewritten onto a new day, borrows nothing from either practice by name and does the counting job on its own, which is most of what actually matters here.

Using Collaborative Problem Solving to enhance Do It Tomorrow

Do It Tomorrow protects today's plan by pushing every new task onto tomorrow's list, but it has no built-in way to notice when the same task has now moved five nights running without ever getting done, since the method's whole design is to defer, not to diagnose. Borrow CPS's core move directly: when a task reappears on the list for the third or fourth day in a row, stop treating it as an ordinary carryover and sit with it the way CPS asks an adult to sit with a child, and ask, out loud if it helps, what specifically is making this hard to start, not 'why haven't you done this' but 'what's the actual obstacle,' then write down a concrete next step that addresses that obstacle rather than just rewriting the same task onto tomorrow's list again. The concrete move is using the list itself as the trigger, a task's third appearance is the cue that converts an ordinary deferral into a CPS-style diagnostic conversation, whether that conversation is with someone else or with yourself.

Using Do It Tomorrow to enhance Collaborative Problem Solving

CPS conversations work best held deliberately, not squeezed into the exact moment the behavior is happening, when both people are already flooded and reactive, but without a structure for when to have that conversation, it often ends up happening reactively anyway, right in the heat of a meltdown, or not at all because the moment passes and it goes unaddressed. Borrow Do It Tomorrow's deferred-capture principle, writing a newly arriving demand onto a fixed list rather than reacting to it immediately, and apply it to the unsolved problem itself: when a behavioral pattern shows up today, write down 'talk about homework refusal' on tomorrow's list instead of trying to have the full collaborative conversation in the middle of tonight's outburst, then hold the conversation at that scheduled time, calmer, with both people more available for genuine joint problem-solving. The concrete move is treating the CPS conversation as a task that deserves its own protected slot on tomorrow's list rather than an improvised response demanded by the moment it arises in.

7:40pm, homework still not open, same as last night

You're standing in the kitchen and the homework folder is exactly where it was at 7:40 yesterday, unopened, and the argument about to start is the same argument you had last night and the night before. Instead of repeating the same warning that hasn't worked three nights running, you write 'homework refusal, what's actually going on' onto tomorrow's list, the same way Do It Tomorrow asks you to defer any newly arriving demand rather than react to it on the spot, and you tell your kid you'll figure it out together tomorrow after school, not tonight. Tomorrow, at a set time when neither of you is mid-conflict, you sit down and ask what specifically makes starting the homework hard, not as a lecture but as a real question, and what comes back, that the assignment feels impossible to even begin, not laziness, is the unsolved problem the last three nights of consequences never got near.

When this is worth reaching for

A task has now moved onto its third or fourth day's list in a row, and nothing about tomorrow makes that any more likely to change than today did. That repetition is the actual signal worth acting on, not the first appearance of a task and not a single ordinary carryover, which happens to everyone and means nothing on its own. It also matters when the item is a recurring behavior rather than a chore, the same conflict at the same time of day, since a list that keeps rewriting one line is the same pattern as an outburst that keeps recurring, just in a quieter register. If a task is simply new, it landed today and has not yet had a fair chance to get done tomorrow, there is nothing to diagnose yet; let the ordinary deferral run its course before reaching for a conversation the situation has not earned.

Where this does not apply

Collaborative Problem Solving is built for a specific, recurring, relational pattern between two people where something underneath the surface behavior is genuinely unsolved, and a plain logistical task with no resistance behind it, buying milk, renewing a parking permit, doesn't have an unsolved problem for a joint conversation to surface. For a task that simply hasn't come up yet rather than one that keeps getting avoided, Do It Tomorrow's ordinary deferral does the whole job on its own, and running a CPS-style diagnostic conversation on a task nobody is actually resisting adds a layer of process the situation doesn't call for.

What the evidence does and does not support

Externalizing an internal pattern into visible, structured form has RCT support in the wider literature CPS draws on, and jointly generated solutions producing more durable follow-through than imposed ones has observational support; the idea that misbehavior reflects a mistaken strategy for a legitimate need is a clinical account, not a measured finding. Implementation intentions closing the gap between intending and acting has strong RCT support; Do It Tomorrow's specific claims about closed lists and deferred capture rest on practitioner reports rather than controlled trials. No study has tested using a task's repeated reappearance on a Do It Tomorrow list as a trigger for a CPS-style conversation; this page describes a plausible reading of two separately evidenced practices, not a tested combination.