How to Structure a Workday Around Focus

Interruptions are switches you did not choose. A study by Gloria Mark and colleagues at the University of California, Irvine produced a counterintuitive result: people completed interrupted tasks in less time with no difference in quality. The explanation is that people compensate by working faster, and the authors found that this "comes at a price: experiencing more stress, higher frustration, time pressure and effort."

That finding changes how to think about interruptions. The visible output can look fine on any single day. The cost shows up as strain, which accumulates across weeks and is harder to see on a task list.

The same study found that individual differences exist in how people handle interruptions. Personality measures such as openness to experience and need for structure predicted how disruptive interruptions were. In practice, some people on a team will be hurt much more by an always-on chat culture than others, and they may not say so.

The evidence above supports one structural rule: group similar work together and protect the complex work from switching. A practical version uses three kinds of blocks.

A few guidelines make the blocks work.

1. Put the hardest work where your energy is highest. Many people find that is the morning, but the right answer is personal. Track it for a week and decide from the record, not from habit.
2. Make focus blocks long enough to absorb residue. If the first minutes of any task are foggy, a 25-minute block loses a larger share to warm-up than a 90-minute block does. Aim for at least one long block each day.
3. Limit focus blocks to one project. Switching between two complex projects inside a block brings back the switching cost the block was meant to remove.
4. Batch shallow work. Checking email after every paragraph is task switching. Two or three scheduled sweeps a day usually cover response-time expectations.
5. Cluster meetings. A day with meetings at 10:00, 13:00 and 15:30 has no long block left. Moving them into one afternoon frees the morning.

Leroy's experiments also show that finishing is not enough by itself. Her abstract reports that being able to finish one task before switching to another is not enough to enable effective task transitions, and that time pressure while finishing the prior task helped people disengage and move on.

Most real tasks do not finish neatly at the end of a block. You can still make the stop cleaner.

• Stop at a defined point. End a block after completing a section, a function or a decision, not in the middle of one.
• Write the next step down. Before switching, write one or two lines: where you are, what you were about to do, and any open question. The goal is to move the open loop from your head to a page.
• Use a short time box for the last stretch. Leroy's finding about time pressure suggests that a clear deadline at the end of a block helps you wrap up and let go.
• Close the tools. Close the documents and tabs from the finished block so they do not pull attention back.

The same habit applies to the end of the day. A written list of open items and tomorrow's first task gives the work somewhere to wait.

Breaks are part of the structure, not a reward for finishing it. A systematic review and meta-analysis published in PLOS ONE pooled 22 study samples on micro-breaks, defined as breaks of 10 minutes or less. It found statistically significant but small effects of micro-breaks in boosting vigor and reducing fatigue.

The performance results were more mixed. A summary of the study on ScienceDaily notes that no overall association was found between micro-breaks and better task performance. Longer breaks tended to be linked to better performance, especially for creative or clerical tasks, and less so for cognitively demanding tasks. The authors suggest that recovery from demanding cognitive work may need longer breaks.

The review also describes what kind of break helps. Work-related activities during breaks were associated with decreased well-being, decreased sleep quality and increased negative mood in the literature it summarizes, while physical activities such as stretching and exercise were associated with more positive emotions and less fatigue.

Practical rules that follow:

• Take short breaks between blocks to manage fatigue. A few minutes away from the screen counts.
• After a long, demanding block, take a longer break before the next hard task.
• Make the break different from the work. Reading work email in the kitchen is not a break.
• Move during breaks when you can. Standing, stretching and walking fit the evidence on physical break activities.

Individual planning only goes so far if the team expects instant replies. Since interrupted people speed up and absorb the cost as stress, a manager will often not see the damage in output. Team norms do more than personal willpower.

• Agree on response times by channel. For example, chat within a few hours, email within a day, and a phone call for anything urgent. When people know what urgent looks like, they stop treating every message as urgent.
• Create shared focus time. A few hours on set days with no internal meetings gives everyone a protected block at once.
• Use office hours. A manager or senior engineer who holds open hours twice a day replaces dozens of interruptions with two predictable windows.
• Write requests so they can wait. A message with full context and a clear deadline can be handled during a shallow block. A message that says "got a sec?" forces an immediate switch.
• Respect individual differences. Mark's study found that people differ in how much interruptions disrupt them. Let people set their own notification and status rules within the team norms.

The same principles apply when part of the work is done by AI agents. Delegating a well-specified task to an agent and reviewing the result in a shallow block is cheaper than supervising it step by step during a focus block.

This template assumes a morning peak and a mostly meeting-free morning. Adjust the times to your own energy pattern and obligations.

Two long focus blocks a day is a realistic target for most roles. On heavy meeting days, protect one.