Why the GROW Model Falls Apart Without a Batched Block

What each one is actually for

Task Batching

When the list will not get any shorter, its arrangement is still available to change. Task batching is a change to when work happens rather than to how much of it there is: you collect the jobs that call on the same kind of attention and do them in one continuous sitting, instead of one at a time as each occurs to you. Rather than answering a message the moment it lands, glancing at a report at ten, another message at eleven, and a document at two, you put forty-five minutes at four o'clock on the day and every short reply gets written there, in one go. The reason this returns more than it sounds like it should is that attention does not switch cleanly between unlike things. Some of it stays on the job you just left, still half-working it, which is why the next thing — even an easy next thing — takes longer and gets a thinner version of your focus than it would have got from someone arriving at it fresh. Nothing in this asks you to work longer or to want it more, which is what makes it available to somebody whose honest description of their situation is that there is no more time and no more willingness to be found. It is a single decision about the shape of a day, settled in advance, and its entire return is that the switching cost gets charged four times on a Tuesday instead of twenty.

GROW Model

The GROW model is a structure for a coaching or self-coaching conversation, developed in the UK in the 1980s by executive coaches including Graham Alexander and later popularized by John Whitmore. It walks through four steps in order. Goal: what do you actually want, specifically, not "be less stressed" but something you'd recognize if you got it. Reality: what is actually true right now, without the story you usually tell about it — where are you really starting from. Options: what could you actually do, listing more possibilities than feel comfortable before narrowing. Will, sometimes written as "Way Forward": which specific option are you actually going to do, and when. The model exists because most people, left alone with a problem, either stay stuck describing it or jump straight to a vague resolution — "I'll try to focus more" — that has no actual action attached to it. GROW forces the conversation all the way through to a named, committed next step.

What you get out of pairing them

A GROW conversation is only as good as what happens to the commitment the moment it leaves the room. The model is excellent at producing a specific "Will" — I will draft the proposal by Thursday — and almost silent on the much more common failure mode: Thursday arrives, and the proposal draft is the eleventh thing on a list, wedged between six unrelated small tasks that all showed up while you weren't looking, and it gets crowded out again. What batching buys a GROW commitment is an actual home on the calendar. Because batching already groups similar work into named blocks, a specific "Will" from a coaching conversation has somewhere real to go — not "sometime Thursday," but inside the existing deep-work block you already protect, or as the anchor task for a new one. The reverse also holds: batching without something like GROW tends to fill up with whatever is loudest that day, not with what actually matters, because batching organizes how you do tasks, not which ones deserve the protected time in the first place. GROW is what decides that; batching is where the decision survives contact with the rest of your day.

What Task Batching rests on

• Attention residue degrades subsequent performance observational studies
  Part of a person's attention stays on the task just left behind for a period after switching which impairs performance on the new task.
• Batched focus enables deeper engagement practitioner report
  Protecting an uninterrupted block of time for one kind of work allows a depth of engagement that fragmented attention across many task types does not allow.
• Task switching imposes cognitive cost randomised trials
  Moving attention between dissimilar tasks carries a measurable cognitive cost each time it happens even when each individual task is simple.

What GROW Model 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.
• Self generated options increase commitment observational studies
  Options a person generates themselves produce more ownership and commitment than options handed to them.
• Structured reflection clarifies goals observational studies
  Walking through Goal and Reality in a fixed sequence clarifies what a person actually wants and where they currently stand.

Where they actually meet

Both practices exist because a good intention, on its own, is not the same thing as a plan the day will actually let happen. GROW's "Will" step already gestures at this — a coach worth their fee pushes for "Thursday afternoon," not "soon" — but the model has no built-in mechanism for what the person's Thursday afternoon is actually made of. Batching is that mechanism. It takes the same insight GROW is reaching for when it insists on specificity, that a vague commitment quietly dies, and applies it at the level of the whole day instead of one conversation: group like tasks, protect the block, and now a specific commitment has an actual slot instead of a hopeful mention.

The principle underneath both

A decision made in a calm, reflective moment, whether that is a coaching conversation's Will step or a Sunday-evening plan for how the week's blocks will run, only survives if it is attached to a specific time and place before the busy version of you shows up. Left as a general intention, it competes on equal footing with every other thing clamoring for attention that day and loses more often than it wins. Attached to a named block or a named moment, decided in advance, it has a fighting chance, because the choice of when to act was already made back when you were thinking clearly, not later, when you are not.

What that makes the real goal

Both practices are aiming at the same target from different sides: getting a good decision made in a clear-headed moment to actually survive contact with a normal, distraction-filled day. GROW makes sure the decision itself is real and specific rather than vague. Batching makes sure the day has a structure that can actually hold it. Neither one alone solves the whole problem — a specific decision with nowhere to live, or a well-organized day with nothing important scheduled into it, both fail the same way, just from opposite ends.

Other practices that serve the same goal

Implementation intentions, the if-then planning technique researched extensively by psychologist Peter Gollwitzer, chase the exact same objective in the most minimal possible form: instead of a full coaching conversation or a batched calendar, you just decide "if it's 4pm on Thursday, I will open the proposal document," and this single-sentence version has strong randomized trial support for closing the gap between intending to act and actually acting. Time-blocking more broadly, scheduling specific hours for specific work rather than working from an unordered list, pursues the same goal at the level of an entire calendar and has decent observational support among people who track their own output before and after adopting it. Weekly reviews, a habit popularized inside Getting Things Done and adopted well beyond it, serve the same objective by giving commitments a recurring checkpoint to be re-attached to a real time slot before they quietly drift off the list entirely.

Giving the GROW model's 'Will' step an actual address on the calendar

Most GROW conversations get the Will step half right: the person names something real, "I will send the pitch deck to my manager for feedback," and even names a day, but stops short of naming when in that day, which leaves the commitment to compete with whatever emails or requests show up first. Close a GROW conversation by asking one more question the model doesn't force but easily accepts: which existing batch does this belong in, or does it need a new one? If you already batch your writing work into a 9am block three mornings a week, the pitch deck goes there, named specifically, not just added to a list that also has fourteen other things on it. If no batch exists yet for this kind of task, the Will step is the moment to create one, because you already have the motivation and the specificity right in front of you, and both tend to fade by the next morning.

Using GROW to decide what actually deserves the batch you've protected

The most common way batching quietly fails is that the protected block fills up with whatever tasks happen to be sitting there when the block starts, rather than the tasks that would have mattered most to put in it. Before you build or refill a batch, run a short version of GROW on it: what do you actually want this block of time to produce this week, not generally but specifically (Goal); what usually happens to this block in practice, does it get taken over by small requests instead of the real work (Reality); what could you actually do differently, a stricter definition of what belongs in it, a different time of day, a shorter list (Options); and which one will you actually try this week (Will). A batch built this way is a decision, not just a grouping — and a batch that was decided on, rather than defaulted into, is much harder for the loudest task of the day to quietly take over.

It's Tuesday, 4pm, your batch block just started, and you almost skip it for a Slack message

Last Thursday, in a short self-coaching session using GROW, you decided the goal was finally starting the vendor comparison your manager asked for two weeks ago, the reality was that you kept telling yourself you'd "find time" for it and never did, the options included doing it first thing, doing it last thing, or blocking a specific slot, and the Will was: Tuesday at 4pm, in the writing batch you already protect three days a week. It's now Tuesday, 4:02pm, and a Slack message just came in asking about something unrelated and mildly urgent-sounding. A week ago you would have answered it immediately, and the vendor comparison would have slid to "tomorrow" again. Instead, because the block has a name and a reason you decided on it four days ago in a clearer-headed moment, you know the Slack message belongs in tomorrow's messaging batch, not in this one, and you actually open the vendor comparison document instead. The decision about what to do right now was made on Thursday, not right now, which is exactly why it survives.

When this is worth reaching for

You run coaching-style conversations, with yourself or with someone else, and they reliably produce specific, well-formed commitments that then quietly don't happen — the gap isn't clarity, it's follow-through. It also fits blocks that already exist on the calendar but keep getting filled with whatever's loudest in the moment instead of whatever was actually decided in advance.

Where this does not apply

If your actual problem is that you don't know what you want in the first place, batching adds nothing; you need the Goal and Reality steps of GROW, or something like them, before scheduling helps at all — a well-protected block of time spent on the wrong thing is still wasted. And if your work is genuinely unpredictable minute to minute, an on-call role, a job made of interruptions by design, forcing batched blocks onto it fights the actual shape of the job rather than fitting it, and the more useful move is closer to triage than to scheduling.

What the evidence does and does not support

The cost of switching between different kinds of tasks is well documented in controlled lab studies, and the broader claim that protected, uninterrupted blocks support deeper engagement has consistent observational and practitioner support, though the specific batching framework as commonly taught has not itself been tested as a packaged intervention. The GROW model's structure, walking Goal, Reality, Options, and Will in that order, has decades of coaching practice behind it and reasonable observational support for producing clearer, more specific commitments, but like most coaching frameworks it has not been isolated and tested against alternatives in a large trial. Nobody has directly studied whether commitments made through a GROW conversation are more likely to be completed when the person also uses task batching; the connection here rests on the well-supported general finding that specific plans attached to specific times and places are far more likely to be carried out than vague ones, applied to this particular pair.