Pro free for 30 days.No card.Start free →

Deep work and interruptions in a small team: how to protect focus time

What research says about interruptions and attention residue, and six practical team agreements, from shared focus blocks to channel response times, that protect deep work in a small business.

By WorkBOS Content Desk7 min read
Headphones resting on a laptop keyboard (Photo by TheAngryTeddy on Pixabay)
Photo: TheAngryTeddy / Pixabay

In a small team, everyone is reachable all the time. A customer calls, a colleague pings you in chat, the owner walks over with a quick question. Each one is reasonable. Added together, they leave people with a day full of activity and very little finished thinking work.

This guide explains what research says about interruptions and switching tasks, then gives a practical set of team agreements for protecting focus time. The goal is not silence. It is to make sure that the work that needs concentration, such as proposals, analysis, writing, design and planning, gets uninterrupted time, while urgent matters can still reach people.

What the research says about interruptions

Switching tasks leaves a residue

Psychologist Sophie Leroy studied what happens when people move from one task to another before the first is finished. In two experiments, described in the journal abstract, people who could not fully disengage from an unfinished task performed worse on the next one. She called the effect attention residue. The same abstract notes that simply finishing the earlier task was not enough for a clean transition, though time pressure while finishing it helped people let go.

For a business owner, the practical reading is simple: jumping between five half-finished jobs costs more than the clock suggests, because part of your attention stays behind.

Interrupted people work faster, and feel worse

A study by Gloria Mark and colleagues at the University of California, Irvine, available as a conference paper, put 48 people through a simulated email task with and without interruptions. People who were interrupted finished faster, in about 20 minutes against nearly 23, and their work was no worse on the measures the researchers used. But they wrote shorter emails and reported significantly more stress, effort, time pressure and frustration. The authors suggest people compensate by working faster, and they note that the study did not measure the time spent getting back into the task, so the real cost may be larger.

Two things stand out. First, interruptions do not always show up as slower work, so a team can feel fine on output while quietly becoming more stressed. Second, the authors found that interruptions about unrelated topics cost no less than related ones, in their words any interruption changes the work pattern. Do not assume a quick, harmless question is free.

You will sometimes see a precise recovery time, such as "23 minutes", quoted online. The study above did not measure recovery time directly, so this guide does not rely on any specific figure. The safer takeaway is that interruptions have costs beyond the seconds they take.

Decide what counts as deep work in your business

Deep work, as the term is commonly used, means focused effort on demanding tasks without distraction. In a small business that might be:

  • Writing a proposal or a tender response
  • Reviewing financial figures or building a budget
  • Designing a process or a product
  • Preparing a performance review
  • Writing documentation or training material

Not everyone needs the same amount. A bookkeeper or developer may need several long blocks a week. A receptionist's job is availability, and that is fine. Decide role by role.

Team agreements that protect focus

1. Create shared focus blocks

Pick one or two windows a day when the whole team treats interruptions as a last resort, for example 9:00 to 11:00. Shared windows work better than individual ones, because nobody feels rude for being quiet, and nobody gets pinged by someone who is not on the same schedule.

2. Agree what is truly urgent

Write a short list of what justifies breaking into focus time, such as a customer-facing outage, a safety issue or a payment failure. Everything else waits until the next check time. If nothing is written down, everything is urgent.

3. Give every channel a response time

People interrupt because they do not know how fast an answer is expected. A simple scheme:

| Channel | Expected response | Use it for | |---|---|---| | Phone call or direct message marked urgent | Within 15 minutes | Real emergencies | | Team chat | Within a few hours | Quick questions, coordination | | Email | Within a working day | Details, external messages | | Task comment | Within a working day | Questions about a specific piece of work |

Write the table down and share it. Our guide on asynchronous communication for small teams goes deeper on setting these norms.

4. Batch the small stuff

Check email and chat at set times, for example three or four times a day, rather than keeping them open. Batching lets people deal with many messages in one go instead of switching constantly.

5. Plan the return path

Before you stop a task, write one line about where you were and the next step. When you come back, you do not have to rebuild the picture from memory. This also reduces the pull of the unfinished job, which fits the attention residue findings above.

6. Cut meetings that could be messages

Meetings are the most expensive interruption because they take several people at once. Keep a regular meeting only if it makes decisions or solves problems. See running meetings people don't dread for a simple structure, and move updates into writing.

A one-week trial

Do not roll this out as a new policy. Try it for a week and look at what happened.

  1. Monday: Explain the idea, and agree the focus window and the urgent list.
  2. Tuesday to Thursday: Run the focus window. Everyone notes when they were interrupted and by what.
  3. Friday: Meet for 15 minutes. What worked? What leaked? Which interruptions were really needed?
  4. Adjust. Change the window, the response times or the urgent list, and run another week.

If you are the owner, go first. A team will not protect focus time if the person at the top breaks it routinely.

Common mistakes

  • Declaring a quiet policy without an urgent route. If people cannot reach each other in a real emergency, they will ignore the policy.
  • Applying it to everyone equally. Customer-facing roles need to be reachable. Give them a different pattern, such as a coverage rota.
  • Measuring only output. As the interruption study shows, speed can hide stress. Ask people how the day feels as well.
  • Forgetting the owner. Owners are often the biggest source of interruptions, with "quick questions" at all hours.
  • Treating the tools as the fix. Turning off notifications helps, but the real change is agreeing who can expect what from whom.
  • Planning no time at all for focus. A weekly plan with no protected block is a plan for fragments. The weekly planning routine shows where to put it.

How WorkBOS can help

The agreements above matter more than any tool. If it is useful, WorkBOS keeps team chat, tasks and the shared calendar in one place, so questions can be attached to the task they are about and people can see what a colleague is working on without asking. Automations can handle routine notifications. See pricing for plans and the docs for how chat, calendar and tasks fit together.

Frequently asked questions

Q: How long should a focus block be? A: Long enough to make real progress on one thing. Many people find 90 minutes to two hours useful. There is no research-based magic number, so start with what fits your day and adjust.

Q: Will customers suffer if staff are less reachable? A: Not if you plan for it. Keep one person or a rota on coverage, set expectations in your customer communication, and keep a clear route for emergencies. Most customer questions can wait an hour.

Q: Is multitasking ever fine? A: For simple, routine tasks it is less costly. The evidence on attention residue is about demanding work where you need to think. If a task needs concentration, give it one slot.

Q: How do I handle the boss who interrupts constantly? A: If that is you, collect your questions into a daily list and send them at set times. If it is someone else, ask for the same thing and propose agreed check-in times.

Q: Do I need special software to do this? A: No. A shared calendar, a short written agreement and some self-discipline are enough. Software only helps if it makes the agreement easier to keep.

Sources are linked in the text above: Organizational Behavior and Human Decision Processes (attention residue, via RePEc), University of California Irvine, Gloria Mark (interrupted work study).

Run it all from one place

Projects, clients, finance, people and AI employees in one system. Start free, no card needed.

Start free →