Sequence creative tasks before reactive tasks each day
Do generative (creating) work before reactive (responding) work — never the other way around.
Why it works
Reactive tasks (email, chat, requests) are open-ended: they surface new problems, create commitments, and load working memory with other people’s priorities. Once the reactive mode activates, attention residue from those interactions stays active and interferes with the blank-page state that generative work requires. Sequencing creative work first ensures the generative phase begins in a clean cognitive state.
How to do it
- Identify your primary creative or analytical deliverable for the day before opening any communication tools.
- Work on that deliverable for at least one uninterrupted session before opening email, Slack, or your task manager.
- Move all "responding to others" tasks — replies, reviews, approvals — to the second half of your workday by default.
- Treat exceptions (genuine emergencies) as exceptions, not as reason to abandon the sequence.
Evidence
Attention residue (Leroy, 2009) demonstrates that incomplete tasks from prior interactions reduce performance on subsequent tasks. Sequencing creative work before reactive work prevents the accumulation of residue from reactive interactions during the generative phase. (mechanistic)
The optimal sequence is mechanistically supported; individual variation in chronotype may shift which morning hours are best for creative work.
Sources
- Leroy (2009), attention residue and performance, Organizational Behavior and Human Decision Processes
Common mistake
Starting the day with a "quick" inbox check to feel organized, which typically takes 20–30 minutes and loads reactive priorities into working memory before creative work begins.
Practice this with IX Coach
7 days free, then $40/month (~$1.30/day).
More practices for Task Batching: Grouping Similar Work to Cut Switching Costs
- Categorize tasks by cognitive mode, not by topic
Group tasks by the type of thinking they require — not just by project — to minimize the mental gear-changing between batches.
- Batch email into 2–3 fixed windows per day
Process email in dedicated 20–30 minute windows rather than responding whenever a notification arrives.
- Batch low-stakes decisions to reduce decision fatigue
Group routine decisions into a single weekly slot rather than making each one as it appears.
- Save admin tasks for your cognitive trough
Assign low-cognition administrative tasks to the time of day when your focus is naturally lowest.
- Create a communication batch protocol for your team
Agree with collaborators on expected response windows so batching doesn’t create perceived unavailability.
- Batch weekly planning into a single review session
Consolidate all task review, prioritization, and scheduling into one weekly session rather than planning continuously throughout the week.
Related concepts
- Deep Work, Made Practical
Focus blocks, attention residue, and the shutdown ritual — with the evidence
- Getting Things Done (GTD), Made Practical
The five steps, the next-action habit, and the science of offloading your mind
- Monotasking, Made Practical
The real cost of task-switching, and how to work one thing at a time