Using Collaborative Problem Solving to enhance Time Blocking

And how Time Blocking sharpens Collaborative Problem Solving in return.

Collaborative Problem Solving, often shortened to CPS and developed largely by psychologist Ross Greene, starts from the idea that a child's difficult behavior is usually a mistaken strategy for solving a real problem the child doesn't yet have the skill to solve any other way — so instead of punishing the outburst, an adult and the child sit down together, name the actual unsolved problem behind it, and build a plan neither could have written alone. Time blocking means assigning every task an actual slot on your calendar in advance, so an open-ended to-do list — which leaves the moment of deciding what to do next exposed to whatever feels easiest or loudest — becomes a series of fixed, already-decided commitments. On this reading, both replace a vague, global judgment about a person — a difficult kid, a lazy adult — with a specific, nameable problem and a concrete plan built around what's actually going on, rather than a character verdict. The link between an unmet need and a workaround behavior is well established in clinical and applied-behavior-analysis settings; time blocking's own trial base rests mostly on the pre-commitment research behind it rather than the named practice itself, and nobody has tested turning a diagnostic conversation on your own missed calendar block.

What each one is actually for

Collaborative Problem Solving

Collaborative Problem Solving treats a child's recurring difficult behavior — meltdowns, refusal, aggression — as evidence of an unsolved problem the child lacks a skill to handle any other way, rather than evidence of bad character or simple defiance. In practice, an adult picks a moment when things are calm, not mid-outburst, and runs a structured three-step conversation: first, genuinely curious inquiry into what's actually hard about the specific situation for the child, in their own words, without arguing or correcting; second, the adult states their own concern about the same situation plainly; third, the two of them generate a solution together that actually addresses both concerns, rather than the adult simply imposing a consequence. The method's own name for this structured conversation is Plan B, and the point of doing it together rather than deciding for the child is that a solution the child helped build tends to survive contact with the next hard moment in a way an imposed rule usually doesn't.

Time Blocking

Time blocking takes your list of tasks and gives each one an actual slot on the calendar — not "work on the report sometime today" but "report, 9 to 10:30" — so that the moment you'd otherwise spend deciding what to do next, a moment that reactive demands like email and interruptions are very good at hijacking, has already been decided in advance. The practice usually includes blocking time for things that aren't obviously tasks too — a block for email, a block for nothing scheduled at all, buffer time between meetings — because an unblocked gap in the calendar tends to get filled by whatever is most urgent-feeling in the moment rather than whatever actually matters most. Done consistently, the calendar itself becomes the record of what you intended to prioritize, which is checkable in a way a mental sense of your own priorities never quite is.

What you get out of pairing them

Collaborative Problem Solving gets an adult and a child something punishment rarely delivers: a solution that actually holds, because it addresses the real obstacle the child kept hitting rather than adding a consequence on top of a problem still sitting there tomorrow. Time blocking gets you something a to-do list never quite manages: protection for what you actually meant to prioritize from the pull of whatever feels most urgent in the moment, because the decision about what to do next got made earlier, while you were calmer and thinking more clearly than you will be mid-afternoon. Each one, in its own domain, trades a plan made in the heat of the moment for one made earlier, with room to see what the real problem actually is.

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 Time Blocking 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.
  • 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.
  • Pre commitment reduces decision fatigue plausible mechanism
    Deciding in advance how time will be spent removes many in-the-moment choices that would otherwise be hijacked by reactive demands.

Where they actually meet

CPS refuses to treat a difficult behavior as simply bad, insisting instead that it's a mistaken strategy for meeting a real, specific, nameable need the child hasn't yet found a better way to meet. Time blocking refuses to treat a missed task the same crude way — as simply laziness — and instead treats a pattern of avoidance as evidence that something specific about the task or the moment it was scheduled isn't actually working, which is a diagnosable problem rather than a character flaw. Both replace a vague verdict about a person with a specific, examinable problem about a situation, which is the only kind of problem you can actually build a working solution to.

The principle underneath both

A recurring 'failure' that looks like a character flaw from outside is nearly always a workaround for a real, specific need — and a workaround only stops once that need is named and addressed, not once it gets punished or rescheduled with more resolve attached to it. Treated as a verdict, a behavior earns a consequence; treated as a signal, it gets investigated, and only the second approach produces a plan that touches what's actually causing the pattern.

What that makes the real goal

In practice, both end up doing the same thing: identifying the specific unmet need or obstacle and building the plan around that directly, instead of building it around the visible behavior — the meltdown, the missed block — which is only ever the symptom. Parenting and scheduling aren't really the subject here; the subject is any recurring problem that keeps recurring because nobody has yet named what it's actually a workaround for.

Other practices that serve the same goal

Functional behavior assessment, used widely in special education, formalizes the same diagnostic move CPS uses — systematically identifying what a behavior is actually accomplishing for a student before designing an intervention — with its own research base in applied behavior analysis settings. The five whys technique, borrowed from manufacturing quality control, pursues the same root-cause logic on any recurring operational problem by repeatedly asking why the surface problem happens until an actual underlying cause, not a symptom, is reached. Motivational interviewing, used in health and addiction counseling, shares CPS's collaborative structure directly, working from the premise that a person is more likely to follow through on a plan they helped build than one handed to them, with a solid trial base of its own in behavior-change settings.

A tradition that already does this

Agile software teams already run a version of this pairing at an organizational scale: the retrospective, a recurring meeting where a team diagnoses what actually went wrong in the last work cycle — not who's to blame, but what specific obstacle produced the recurring problem — followed immediately by sprint planning, which commits the resulting fix to an actual dated slot in the next cycle rather than leaving it as a vague intention. It's the identical two-step arriving from a completely different field: diagnose the real, specific problem first, then commit the fix to a concrete time, because a diagnosis without a scheduled commitment tends to evaporate by the next cycle.

Using Collaborative Problem Solving to Enhance Time Blocking

When a time-blocked task keeps getting skipped — the same block, moved or ignored for the third week running — the usual response is to reschedule it again, or add willpower, both of which leave the actual obstacle untouched and guarantee a fourth skipped week. Borrow CPS's diagnostic move on yourself instead: before rebuilding the block, run a short, honest version of the same curious inquiry the method uses with a child, aimed at your own resistance rather than a kid's — not "why am I so undisciplined" but specifically what's actually hard about starting this particular task at this particular time. Often the real answer isn't laziness at all: the first concrete step isn't clear, the block is scheduled right after a draining meeting with nothing to recover from, or the task quietly depends on someone else's input that hasn't arrived. Build the new block around whatever that specific answer turns out to be — a different first step, a different time of day, a dependency resolved first — rather than simply re-scheduling the same failed block with more determination attached.

Using Time Blocking to Enhance Collaborative Problem Solving

A CPS conversation regularly produces a genuinely good plan that still falls apart within a week, and the most common reason isn't that the plan was wrong — it's that the plan never got attached to an actual time and place, so it stayed a good intention exactly the way "I'll be better about deadlines" stays a good intention on a to-do list. Bring time blocking's specific discipline into the last step of the conversation: instead of ending on "we'll try checking in about homework after school," end on "four-fifteen, at the kitchen table, for ten minutes, starting tomorrow" — an actual slot, named out loud by both of you before the conversation ends. The diagnostic work CPS does is real and necessary, but a correctly diagnosed problem with no scheduled moment to practice the fix tends to quietly revert to the old pattern within days, for exactly the same reason an untimed personal task quietly reverts to being skipped.

The Third Tuesday of Missed Blocks

You've moved the same calendar block — "write the proposal section," 2 to 3:30 — three Tuesdays running, each time telling yourself you'll definitely do it next week with more discipline. This time, instead of moving it a fourth time, you sit with the actual question: what specifically happens at two o'clock that makes this block fail every single week. It turns out the block sits right after your team's Tuesday status meeting, which reliably leaves you mentally fried and needing fifteen minutes you never scheduled, so the proposal block starts already depleted and gets abandoned by ten past two. You don't reschedule the same block with more resolve; you move it to Wednesday morning, before anything else has drained you, and you name the actual first step inside the block itself — not "write the proposal section" but "draft the three bullet points for section two" — small enough that starting it doesn't require the discipline the old version quietly demanded. It holds the following week, not because you tried harder, but because the block was finally built around what was actually happening at two o'clock on a Tuesday.

When this is worth reaching for

Behavior that looks willful or defiant from the outside but persists despite consequences that would normally work is the signal — that persistence itself means something real is being missed, and it is what collaborative problem solving is built to find. A specific, recurring task that keeps failing in the same way despite genuine intention to complete it calls for the same diagnostic borrowed into time blocking; an occasional missed block that doesn't reflect any real pattern does not.

Where this does not apply

CPS assumes a relationship where an adult holds real responsibility for supporting another person's behavior and development, and turning its diagnostic conversation inward on your own procrastination isn't a precise fit — you can't hold yourself accountable the way an adult holds a child accountable, and treating your own resistance as a child's unsolved problem can slide into excessive self-analysis when the honest answer is simply that a task is unpleasant and still has to happen. And where a child's difficult behavior includes real risk of harm to themselves or others, CPS's calm, collaborative structure needs professional guidance to implement safely — it is not a substitute for a clinician's assessment of what's driving that level of escalation.

What the evidence does and does not support

Collaborative Problem Solving has real clinical and observational support, including reduced behavioral incidents in some school and inpatient settings where it's been formally implemented and studied, though its evidence base is smaller and less uniformly controlled than more established behavioral interventions. Time blocking's core mechanism — pre-committing a specific action to a specific cue, in this case a calendar slot — draws on the strong implementation-intention research base, though time blocking as a complete named practice has less direct trial testing than that underlying mechanism does. Nobody has studied using CPS-style diagnostic questioning on one's own procrastination, or ending a CPS conversation with a literal calendar block instead of a general plan; both are reasonable extensions of well-evidenced pieces, not a tested combination in either direction.

Practice this with IX Coach

Try this practice

The two practices on their own

Other pairings with these practices

The principles underneath both