You plan a tidy day, and by 10:45 a client problem has knocked over every block that follows. The plan wasn’t careless. It assumed nothing would happen, which on a reactive job is the one assumption guaranteed to be wrong.
Build an anti-schedule instead. Book only your fixed commitments and one or two protected focus blocks, then leave deliberate, unassigned buffer zones to absorb whatever lands. You plan less of the day in advance and finish more of what matters, because interruptions have somewhere to go.
Where the anti-schedule comes from, and why buffers work
The name nods to psychologist Neil Fiore’s Unschedule from The Now Habit. Fiore built it for procrastinators. You first block out committed time such as meetings, meals and commuting, plus guilt-free leisure, and record work only after you have done it. The anti-schedule keeps his central move, planning around what is genuinely fixed instead of pretending every hour is yours, and adds explicit space for interruptions.
That space matters because switching between tasks carries a measurable time cost, shown in experiments by Joshua Rubinstein, David Meyer and Jeffrey Evans. Meyer has estimated that these brief mental blocks can cost as much as 40 percent of someone’s productive time, a figure the American Psychological Association repeats in its summary of the research. It is a ceiling estimate, not a fixed rate.
Where an interruption lands changes its price. A crisis that hits the middle of a focus block costs more than its own minutes: you pay the switch twice, and the half-finished task keeps tugging at you while you handle the emergency. One that lands in a buffer, between tasks, costs far less.
Keep expectations calibrated. A 2021 meta-analysis of time management research by Brad Aeon, Aïda Faber and Alexandra Panaccio found its link to well-being was stronger than its link to job performance. An anti-schedule reliably makes chaotic days feel more controlled; it will not double your output.
The 10:45 test: one crisis, two calendars
Take a public-relations account director with a fixed 1:00 call with a media-monitoring vendor and two pieces of real work: a new-business campaign proposal and a quarterly coverage review for an existing client. At 10:45 a reporter calls about a client’s delayed product launch, and drafting a holding statement, getting the client’s sign-off and returning the call takes 75 minutes. Here is the same Tuesday planned two ways.
| Time | Traditional time-blocked day | Anti-schedule |
|---|---|---|
| 8:00–8:30 | Email and admin | Check-in: confirm the one task that must move, scan for fires |
| 8:30–10:30 | Campaign proposal draft | Protected focus: campaign proposal draft |
| 10:30–12:00 | Client status report edits; reporter calls at 10:45, report abandoned half done | Buffer zone; reporter calls at 10:45, holding statement approved and sent by noon |
| 12:00–12:30 | Lunch, eaten at the keyboard finishing the report | Lunch |
| 12:30–1:00 | Vendor call prep, skipped | Vendor call prep |
| 1:00–2:00 | Vendor call (fixed), underprepared | Vendor call (fixed) |
| 2:00–3:30 | Coverage review, starts late and overruns | Protected focus: coverage review |
| 3:30–4:30 | Expense reports, pushed to tomorrow | Buffer zone; nothing urgent, so status report pulled from the menu |
| 4:30–5:00 | Catch-up; leaves at 6:00 | Wrap-up: write tomorrow’s first step |
| Result | Three tasks slipped, lunch lost, an extra hour worked | Both focus blocks intact, press inquiry handled, one buffer turned into progress |
The rigid day did not fail at 10:45. It failed when it was planned, because there was no room for anything not already on it. The anti-schedule left two and a half hours unassigned and still delivered the proposal, the coverage review and the holding statement.
Build yours in five steps
- Mark fixed points only. Meetings, school runs, lab sessions and the travel time between them; a commute or a walk across campus is not free time. If you are unsure where your hours actually go, run a time audit for a few days first.
- Place one or two protected focus blocks. Make them 60 to 90 minutes, in the hours your interruption history says are quietest. Name each with the exact task (“Draft budget section of campaign proposal”, not “Proposal”) so starting needs no decision. Our guide to time blocking covers block design in depth.
- Add buffer zones and transitions. A reasonable starting point is one or two buffers of 60 to 90 minutes, usually late morning and mid-afternoon, plus 10 to 15 minutes between major blocks so a five-minute overrun does not push everything after it. Leave buffers empty on purpose.
- Keep a ranked menu, not a queue. Write a short priority list using the 1-3-5 rule: one big task, three medium, five small. When a buffer stays quiet or a meeting is cancelled, pull the next item instead of deciding from scratch.
- Check in daily, absorb weekly. Spend two minutes each morning on three questions: what moved yesterday, what one task must move today, and what is likely to blow up. Once a week, hold a half-day contingency block for anything the daily buffers could not absorb.
What to do when the crisis lands
When something urgent arrives, ask one question first: does this have to happen today? If not, capture it on your list and choose a slot at the next check-in. Only work that genuinely cannot wait gets the buffer.
If it cannot wait and you are mid-focus-block, take 60 seconds to write the next concrete step of the task you are leaving, such as “check figures in table 3, then write the summary paragraph”. That note lets you return later without reconstructing where you were, and makes it easier to stop thinking about the task while you deal with the crisis.
Anti-schedule, strict time blocking or Fiore’s Unschedule?
Choose by your main problem. Interruptions call for buffers; trouble starting calls for something gentler.
| Approach | Fits best when | Breaks down when |
|---|---|---|
| Strict time blocking | Most of the day is predictable, with one or two unplanned requests at most | Interruptions are frequent and each one forces a full reshuffle |
| Anti-schedule | You own real deliverables and face real interruptions: PR and agency leads, project managers, team leads, freelancers with live clients | Nearly all work is reactive, so focus blocks never survive |
| Fiore’s Unschedule | The problem is starting, not interruptions: procrastination, perfectionism, long solo projects | You must commit specific hours to other people in advance |
| Queue-based day | Support or on-call shifts where incoming tickets are the work | You also own projects that need protected time |
When buffers get eaten
- Buffers get booked in advance. This is the most common relapse. If you keep pre-filling them, you have more work than the structure can hold: cut or defer tasks with the Eisenhower Matrix, or ask which 20 percent of tasks drive most of your results.
- Everything becomes an emergency. If every request jumps straight into a buffer, the triage question is not being asked. Capture first, decide second.
- Focus blocks keep getting invaded. If interruptions hit the same block three days running, move it to a quieter slot rather than defending a time that does not work.
- Buffers overflow daily. Widen them by 30 minutes, or drop to one focus block for two weeks while you log what lands. The log shows whether you need to renegotiate workload or expectations.
- Buffers stay empty. Unused buffer time still did its job by protecting the day. Shrink them by 30 minutes or treat them as pull time from your menu.
Daily anti-schedule card
Once the five steps are routine, the whole plan fits on an index card or the top of a daily page. Fill in these lines each morning; it takes about five minutes.
- Fixed: start and end times of every meeting, pickup and travel slot.
- Focus: one or two named tasks, each with a start time.
- Buffers: start and end of each unassigned zone.
- Menu: one big, three medium and five small tasks, ranked.
- Rules: not today means capture; before leaving a task, write its next step.
- Log: at day’s end, what each buffer absorbed, plus tomorrow’s first step.
The log line is the one that pays off. After two weeks of entries, you will know your real interruption pattern and can size buffers from evidence instead of hope.
1 Comment