How to protect focus time without disappearing on your team

Choose an output, not an impressive length of time

“I need more focus time” describes a frustration. “I need to check the assumptions in Thursday's proposal before we send it” describes work your team can recognise. Begin with something specific enough to finish or move to a clear stopping point.

For example: draft the recommendation and list three unresolved questions; review one section of a contract with the right specialist; reconcile the exceptions in a report. Avoid a vague label such as “strategy” if you cannot explain what will be different afterwards.

Pick a realistic opening in the existing work pattern. Forty-five minutes may be more workable than two hours. That is an example, not an evidence-based optimum. The right duration depends on the task, your role and the cover available.

A small six-week study by researchers Koustuv Saha and Shamsi Iqbal compared 15 people using automatically scheduled focus time with 10 controls and reported wellbeing benefits. Its scale and setting do not establish a universal productivity gain or ideal session length. It supports trying a considered arrangement, not promising that a calendar tool will fix work. See the 2023 focus-time study^[1].

Check who would be waiting for you

Before adding the block, ask what depends on your availability. Are you the only person who can approve a payment, answer a customer escalation or unblock a colleague? Is a deadline likely to land during that period?

Move routine dependencies first where possible. Send the file someone needs, answer the decision already waiting, or agree a later response time. Do not create a quiet hour for yourself by silently transferring the disruption to somebody else.

If your role requires continuous cover, discuss a rota or a brief hand-off with your manager. Another person's availability is not yours to promise. Without agreed cover, keep the normal service arrangement and raise the need for a different work pattern.

Sometimes the issue is not interruption at all. If more work is being allocated than can fit into the week, use our guide to agreeing what should move when work is added. A protected slot cannot make an impossible workload possible.

Make the urgent route specific enough to use

“Contact me if it is urgent” leaves every person to make the same judgement differently. Agree one channel and a few examples of what should interrupt the block. Follow your organisation's incident and escalation rules rather than inventing a competing system.

For an office team, the agreement might be that a live service incident or a decision blocking today's customer deadline warrants a call. A request for next week's slides can wait until the stated check-in. Those are illustrative distinctions, not rules suitable for every workplace.

Do not turn off every notification without checking whether approved emergency or accessibility arrangements rely on them. Use your existing authorised settings, and make sure the urgent route actually reaches you. You do not need a new app, monitoring tool or paid subscription to have this conversation.

Keep the response promise honest. “I will check messages at 11:00” is useful only if you can do it. “I will see everything eventually” is not a workable cover plan.

Ask for an experiment your manager can judge

Try this wording: “The proposal needs an uninterrupted assumptions check before Thursday. Could I protect 10:00 to 10:45 on Tuesday and Wednesday this week? I will check routine messages afterwards. For the existing incident route, I will remain reachable. I will share the checked section and flag what still needs a decision.”

Adapt the time and channel to the actual team. Then ask: “Would that leave anyone without cover, or conflict with a deadline I have missed?” This invites a useful constraint instead of forcing your manager to accept or reject the whole idea.

Agree when you will review it. After two sessions, you can discuss whether the output improved, whether anyone was left waiting and whether the timing was sensible. You are proposing a way to deliver work, not requesting immunity from collaboration.

If the blocked time collides with a recurring meeting, inspect the meeting before declining it. Our meeting audit helps separate a decision you need to attend from an update that might be handled differently.

A worked example: the proposal that never gets checked

Consider a fictional project coordinator, Maya. She needs to review a proposal, but colleagues keep asking for small clarifications. She initially books two hours every morning and mutes chat. A teammate misses an approval, and the team loses trust in the arrangement.

The repair is not to abandon concentration. Maya asks when colleagues most often need her. The team agrees two 45-minute sessions after the morning hand-off, with another colleague covering only the questions they have actually agreed to cover. The existing incident channel remains available.

Before each session Maya names one output: on Tuesday, identify unsupported assumptions; on Wednesday, revise the recommendation using the answers received. Afterwards, she posts a short update in the team's existing place, not a new reporting system.

The first session is interrupted by a genuine deadline problem. Maya records that fact and reschedules the remaining review time with her manager. The second session works. They now have something specific to improve: the timing of approvals, rather than a debate about whether Maya is sufficiently responsive.

This is an illustration of coordination, not a claim that one script guarantees agreement. In another role, shorter slots, shared cover or a different day might be the only realistic options.

Review the arrangement without tracking every minute

After the experiment, ask three questions. Did the named output move forward? Did anyone lose necessary access to you? What would make the next attempt easier? A few notes are enough; you do not need to measure colleagues or build a productivity score.

If the slot repeatedly disappears, look for the cause. An unclear priority, missing cover, too many approvals or a genuinely overloaded team needs a different response from a habit of checking messages. Bring concrete examples to the person who can change that arrangement.

The UK's HSE Demands standard^[2] emphasises achievable work within agreed hours. Its Control standard^[3] includes a say in work patterns and, where possible, pace. These are UK workplace-management standards, not a universal legal entitlement to a quiet hour. They underline why work design cannot be reduced to individual willpower.

Keep breaks and the end of your working day intact. Do not compensate for a protected morning by silently moving all messages into the evening. If there is no workable space for essential tasks, the problem needs a capacity or priority decision, not a more determined employee.

Your ten-minute next step

Write five short lines: the output you need to move; a realistic slot; who might depend on you; the agreed urgent route; and when you will review the attempt. Leave unknowns marked as questions rather than pretending the arrangement exists.

Send a focused request to the person who can agree it. If you first need to understand what success looks like, our first-month expectations guide offers questions that also work beyond a new role.

The aim is a working agreement: enough space to think, without leaving the people who rely on you guessing. One small, visible experiment is a better start than a perfect calendar nobody else understands.