Deep Work in an Organisation That Is Not Built for It

Advice on concentrated work usually assumes an autonomous professional who controls their own calendar. Most people do not. They have a manager, a shared calendar anyone can book, a messaging channel with an implicit response expectation, and meetings scattered through the day by other people.

For further product context on the cost of task switching, consult further details.

Healthy-workplace research is available from the American Psychological Association healthy-workplace resources.

This page separates what is achievable on your own from what genuinely requires the organisation — because pretending the second category is a personal discipline problem is how people end up believing that fragmentation is their fault.

What you can do alone

Modest, and worth doing.

Book the block yourself. Put it in the calendar as an appointment with a subject line. An unlabelled hold gets overwritten; "Q3 analysis — drafting" usually does not.

Take the first hour. For most people the hour before the day's meetings begin is the only reliably uninterrupted one. Protecting it deliberately is more effective than trying to find time later.

Batch messages. Defined times rather than continuous attention. The cost is not the messages; it is the anticipation of them.

Reduce the number of places to check. Consolidating notification channels does more than any discipline technique.

Prepare the entry point. The re-entry cost is what makes interruption expensive. Leaving a note about exactly where you stopped and what comes next cuts it substantially.

Decline what you can. Where attendance is genuinely optional, decline. Where it is not, this advice does not apply and pretending otherwise is not useful.

What requires the organisation

Be clear that these are not within an individual's gift.

Consolidated meeting windows. No amount of personal planning recovers a day cut into eight pieces by other people. See calendar design for teams.

Response-time norms. If the culture expects a reply within minutes, no individual can opt out without cost. A stated norm — "chat is not urgent; call if it is" — removes the anticipation, and only a manager can set it.

Separating interrupt duty from project work. Some roles are reactive by design. Expecting the same person to also deliver concentrated work is a scheduling impossibility, not a motivation problem. Rotating the escalation duty usually recovers more capacity than everything else combined.

Reducing work in progress. Someone juggling six half-finished things cannot concentrate on any of them, and that is a commitment decision made above them.

Workload. If there is more work than time, concentrated work is the first casualty, and no technique restores it. See burnout as an operational problem.

How to ask for it

Asking for uninterrupted time reads as asking for a favour unless you frame it as an operational request.

Bring the number. How many uninterrupted blocks of two hours or more you had last month. It is usually low enough to make the argument by itself, and it is not contestable.

Attach it to output. "The analysis needs about six hours of uninterrupted work. Currently my longest block is forty minutes, which is why it keeps slipping." That is a delivery conversation, not a preference.

Propose something specific and small. Two mornings a week, or a protected block on Tuesdays. Easier to agree than a general principle.

Offer the trade. What you will be reachable for, and how someone reaches you if it is genuinely urgent.

Suggest it for the team, not just yourself. A protected block that applies to everyone is easier to agree and considerably more likely to hold.

For managers

Three things worth knowing.

You set it by example. If you book across people's blocks, they do not exist. If your own calendar is fragmented, everyone's will be.

Concentrated work looks like idleness. Someone thinking, reading, or working on paper produces no visible activity. If your organisation measures activity, it is measuring against the thing you say you want. See productivity surveillance.

The fix is structural and cheap. Consolidating meetings into windows costs nothing and does not require cancelling anything. It is the highest-return change available to most teams.

The honest limit

If you work in a role that is genuinely interrupt-driven — support, operations, clinical, front-of-house — concentrated work is not part of the job, and the advice does not apply.

The failure in those settings is not the absence of deep work. It is expecting the same person, in the same week, to also deliver project work that requires it. That is a staffing and scheduling decision, and the honest response is either to protect the time explicitly or to stop expecting the output.

Telling people to concentrate better in an environment that structurally prevents it is the same category error as offering resilience training to a team with too much work.