Decisional Delays
Decisional Delays
A decisional delay is the stretch of time between finishing one task and starting the next. That stretch is on no schedule. The next move usually gets decided inside it: which task comes next, what its first step is, and where the materials are. Deciding there is expensive for two reasons. The deciding uses the attention the next start needed. And while the choice is open, whatever is already open on the desk takes that attention first.
Closing the gap costs a few minutes the night before. Write the next task, its first action, its materials, and a fallback for when it is blocked. After that, finishing a task involves no decision. The next start was decided the night before.
Core takeaways
- A decisional delay is the unscheduled stretch between finishing one task and starting the next. The next move usually gets decided inside it.
- Deciding in the gap uses the attention the next start needed, and whatever is already open on the desk takes that attention. The larger cost is the break in absorption in the work.
- Closing the gap takes a few minutes the night before: write the next task, its first action, its materials, and a fallback for when it is blocked.
- A usable plan names six things: the next task, the start condition, the stopping condition, the materials, the fallback if blocked, and what not to do during the block.
- To measure the cost, log for about a week when each focused task ends and when the next one actually begins, and count the unplanned transition time.
- Planning and prioritisation are batched at the start or end of the day. During a block of focused work, inputs are blocked so no new options enter.
What the gap costs
The visible minutes between tasks are only part of the delay. The larger cost is the break in Flow State. Flow is absorption in the work. A timer does not define it. The gap breaks it.
When the next action is decided in the gap, four things happen together. Attention leaves the work that just ended. Planning uses the effort that should have gone into the next start. While the next action is undecided, whatever is already open on the desk draws attention. Re-entry into focused work takes time of its own.
Each decision feels small. Repeated across a day, the switching adds up to a large loss.
How to see the cost
The repair starts with measuring the loss. For about a week, mark when a focused task ends and when the next focused task actually begins. Compare the planned schedule to what actually happened. Count the unplanned transition time and the focus breaks that follow those gaps. In the first days of the log, the person usually notices no gaps. Over the week the gaps become visible. The point of the log is to find out whether decisions between tasks cost time the schedule does not show. A feeling of being more decisive is not the goal.
Two jobs go together: plan the decisions outside execution time, and measure how much time disappears between tasks. The log shows how much time goes to the gaps, and the plan made at the start or end of the day removes the decisions from them.
Plan before the block starts
The next action has to be specific before the work block starts, and the block has to be kept free of new choices. This replaces deciding as the work goes. Execution should not need constant re-planning.
Batch planning and prioritisation at the start or end of the day, so that no planning is needed in the middle of the day. While the work block is running, block inputs so that new options do not enter.
A usable plan names six things: the next task; the start condition; the stopping condition; the materials needed; the fallback if the task is blocked; and what not to do during the block. “Study biology” still contains decisions. “At 9:00, Aim the endocrine chapter for 25 minutes, and produce five why/how questions” removes more of the ambiguity. To Aim a chapter is to write what the material must answer before opening it.
When the plan fails
When the plan fails, the failure usually has one of five shapes.
| Failure | Repair |
|---|---|
| Vague plan | Write the next action |
| Mid-task planning | Batch at the day edges |
| Open distraction channels | Block inputs |
| Overplanned day | Fallbacks and buffers |
| Invisible transition loss | Track a week |
An overplanned day brings the decisions back as soon as anything slips. Fallbacks and buffers loosen a schedule that is too tight to hold once something slips.
The stretch between tasks does not go away. The six items written the night before already hold the decision, so no decision is left to make at the next start.
How to practice this
- For about a week, mark when a focused task ends and when the next focused task begins. Compare the planned schedule with what happened. Notice the unplanned transition time and the focus breaks that follow each gap.
- Expect the first days of the log to show no gaps. Notice whether gaps become visible later in the week.
- The night before, write the next task, its first action, its materials, and a fallback for when it is blocked. Notice whether the next morning’s first start needs any decision.
- Write the full plan with its six items: task, start condition, stopping condition, materials, fallback, and what not to do. Notice whether a line like “Study biology” still leaves choices open. Compare it with a line that names a time, a chapter, a duration, and an output.
- Batch planning and prioritisation at the start or end of the day. While a work block is running, block inputs. Notice whether new options stop entering the block.
- When a day slips, match the failure to one of the five shapes in the table. If the day was overplanned, add fallbacks and buffers. Notice whether the decisions stop coming back in the middle of the day.
Related pages
- Decision Making: hub for how much thinking a choice is worth.
- Choice Throttling: a different problem, a tangled choice rather than a between-task gap.
- Flow State: the state the gap breaks, absorption, not a timer.
- Procrastination: a System Problem: when the gap becomes avoidance.
- Self-Management: parent dimension.
Open questions
Which transitions create the most delay?
Does a written next-action queue, calendar blocks, or both close the gap better?
Sources
- Mark, Gudith & Klocke 2008, CHI: 23 min 15 sec to return to an interrupted task after intervening tasks. Used only as a bound: that study measures resuming after other tasks, not a self-posed “what next?” after a task ends.
- Gollwitzer & Sheeran 2006, implementation intentions: a specific next action reduces start friction. This supports writing the next action before the gap; it does not measure the gap itself.