How do people get demanding work done during the day?
Protecting Uninterrupted Time
Concentration requires blocks, and most workplaces are designed to prevent them. What actually protects time, and what only appears to.
Procedure
Demanding work requires sustained attention. Most work environments supply attention in fragments and then wonder why the demanding work happens in the evening.
The evening problem
A specific and common pattern worth naming.
The working day is consumed by meetings, messages and interruptions.
The actual work — thinking, writing, building, analysing — happens after hours, when nobody is asking anything.
This looks like commitment and is a design failure. It means the organisation has structured the day so that its core work cannot be done in it.
It is also the most reliable route to exhaustion, because it removes the recovery period entirely.
A useful diagnostic: ask when people do their most demanding work. If the answer is early morning or after everyone logs off, the day is not working.
What protects time
Organisation-level blocks. A shared period where meetings are not scheduled. Individual blocked time fails because it is overwritten by anyone more senior.
Clear response expectations. People fragment their own attention when they believe an immediate reply is required. Stating an actual expectation — hours, not minutes — returns the block.
Fewer channels. Each additional message system multiplies interruption surface.
Asynchronous defaults. Written updates, recorded briefings, decisions documented rather than convened.
Manager cover. Someone absorbing interruptions on behalf of the team, which is real work and should be recognised as such.
What does not
Advising individuals to block their calendars, which works until someone senior needs the slot.
Focus apps and browser blockers, which address self-interruption when most interruption is external.
Do-not-disturb status, which people ignore or feel guilty using.
Encouraging people to be more disciplined, which locates a structural problem in the individual.
Designing for different roles
Focus needs vary and should not be flattened.
Roles that are mostly reactive — support, operations, service — need predictable off-rotation periods rather than daily blocks.
Roles that are mostly generative need long blocks and few of them, rather than short blocks and many.
Managers need both and usually get neither. Their focus time has to be protected by someone else.
Ask each team what shape they need, rather than applying one policy.
The interruption audit
A useful exercise, run for a week.
Log interruptions: who, what, whether it could have waited, whether it could have been written.
Aggregate by source. The findings are usually concentrated — a handful of recurring interruptions account for most of the volume.
Fix the top three. Frequently the answer is documentation, a clearer route, or a decision that keeps being reopened.
This produces more usable time than any individual technique, because it removes the interruptions rather than teaching people to endure them.
The measurement worth keeping
Largest uninterrupted block in a typical day, self-reported, per team, tracked over time.
Simple, comparable, and it moves when you change something. It is also immediately understood by people who would ignore a composite wellbeing score.
When the most demanding work happens
A single diagnostic question that reveals whether the working day functions.
Ask people when they do their hardest thinking.
Early morning, late evening, or weekends means the day has been structured so that the core work cannot happen in it.
During the working day means the design is working.
Ask the follow-up: what would have to change for that work to move into normal hours.
The answers are usually specific and fixable — a recurring meeting, a response expectation, an interruption source.
Track the answer over time as one of the simplest available measures of whether meeting and interruption reduction is working.
Protecting time at organisational level
Individual blocked time fails, and the reason is structural.
Anyone more senior can overwrite it, and frequently does.
Declining on the basis of blocked time requires standing that junior people do not have.
So the protection has to be organisational: a period where meetings are not scheduled, held by the organisation rather than defended by individuals.
Half a day, twice a week, is a common shape.
It only works if senior people observe it, which is the same condition as everything else in this section.
Also in this section
- How do I know if my team is genuinely over capacity?
- People say they have no time to do their actual work.
- Why does the team collapse whenever one person is off?
- People are working hard but the wrong things keep happening.
- Why is every project a crunch at the end?
- Can people change their roles without a reorganisation?