Your infinite workday is a coordination problem, not a discipline problem

You sit down to finish one meaningful task. An email arrives. A Teams message pulls you into a thread. A meeting invite claims the hour when your brain is usually sharp. Someone asks for a “quick” call, which is rarely quick and almost never just one call.

By late afternoon, you have been active all day but cannot point to much that is finished.

That is not automatically a discipline problem. It may be a coordination system with no off switch.

The evidence points to fragmentation

Microsoft’s June 2025 Work Trend Index special report analysed globally aggregated, anonymised Microsoft 365 activity and surveyed knowledge workers. Its picture of the workday is not subtle:

• The average worker receives 117 emails per day.
• The average worker receives 153 Teams messages per weekday.
• During core work hours, employees are interrupted by a meeting, email, or notification roughly every two minutes.
• 48% of employees say their work feels chaotic and fragmented.

Those figures describe digital activity, not completed output. They are not proof that every message destroys 23 minutes of productivity, and Microsoft’s telemetry is not a controlled experiment. But the pattern is useful: a lot of modern work is structured around reacting to other people’s priorities.

An empty space on your calendar does not necessarily mean you have focus time. It may just mean that your interruptions are arriving through channels the calendar cannot see.

Why batching is worth testing

The obvious response is to become more vigilant. Watch the inbox. Keep Teams open. Reply quickly so nothing piles up.

That feels responsible. It is also a good way to turn your attention into a public utility.

A study published by the MIT Media Lab tracked 40 information workers in their normal workplaces for 12 workdays, combining computer logging, biosensors, and daily surveys. The researchers found that spending more time on email was associated with lower perceived productivity and higher measured stress. They also found that batching email was associated with higher rated productivity when email sessions became longer.

The useful caveat is that batching did not show evidence of reducing stress in that study. It is not a magic wellness ritual. It is a way to stop every incoming notification from becoming a decision about what to do next.

That distinction matters. The goal is not to check messages less because checking messages is morally suspect. The goal is to give coordination a container, so it stops leaking into every other type of work.

Build a coordination layer around your day

You do not need a heroic productivity system. You need a few rules that make the cost of interruption visible.

1. Separate production from coordination

Production creates something: a proposal, a product change, a sales call, a decision, a finished analysis.

Coordination moves information between people: reading messages, answering questions, scheduling, clarifying ownership, and checking status.

Both matter. They simply should not be mixed together by default.

Choose two or three coordination windows—for example, 10:30, 13:30, and 16:30. Review email and messages during those windows. Outside them, notifications stay off unless you are genuinely on call.

If your job requires a faster response, define the response time honestly. A 30-minute service expectation is different from pretending that everyone must be instantly available all day.

2. Protect a small number of real focus blocks

Start with two blocks of 45–90 minutes. Put them on the calendar as work, not as optimistic whitespace.

During each block:

• Close email and chat.
• Put the phone out of reach.
• Keep one clearly defined outcome in front of you.
• Write down new requests instead of switching to them.

Do not begin by demanding four hours of deep work from a fragmented day. That plan usually lasts until the first notification, then becomes another reason to feel behind. Two protected blocks are enough to test whether the system changes what gets finished.

3. Make meetings prove their case

A meeting should have a job. It should make a decision, resolve a real ambiguity, or produce an outcome that is difficult to create asynchronously.

Before accepting, ask:

1. What decision or deliverable is expected?
2. Why does this need a live conversation?
3. Who actually needs to be there?

If the answer is “we should discuss,” ask for a short written proposal first. The meeting may still be necessary. It will simply have something better to discuss than everyone’s live discovery of the problem.

End every meeting with an owner and a date. Otherwise the meeting has produced conversation, not progress.

4. Use an assistant as a buffer, not another loudspeaker

An assistant can help with the coordination layer by grouping related messages, preparing a daily digest, identifying unanswered requests, drafting low-risk replies, and surfacing tasks that are waiting on someone else.

The point is not to add AI to the noise. It is to turn many small decisions into one reviewable queue.

A useful rule is:

Let the assistant collect, classify, and prepare. Keep consequential commitments and ambiguous decisions in human review.

That gives you leverage without pretending that every message can be safely automated.

Run a five-day test

Do not redesign your entire working life based on one irritating Tuesday. Run a small experiment for five working days:

• Set two protected focus blocks each day.
• Check email and chat at fixed times.
• Convert at least one non-essential meeting into an async update or decline it.
• Keep a short list of interruptions that genuinely required an immediate response.
• Track four outcomes: meaningful tasks finished, focus blocks completed, after-hours checking, and end-of-day energy.

Do not measure success by how empty your inbox looks. An empty inbox can simply mean that you spent the day answering it.

At the end of the week, ask a better question: did the new rhythm produce more of the work that matters, with less spillover into the evening?

Coordination is work. It needs a budget.

Some roles need live response. Customer support, incident management, sales, and collaborative delivery cannot be run as silent monasteries. The answer is not to ban interruptions. It is to decide where they belong, who owns them, and what response time the work actually requires.

If every channel is urgent, nothing is prioritised. If everyone can interrupt everyone, the organisation has outsourced its planning to notification badges.

Start tomorrow with one 45-minute block, two message windows, and a list of what qualifies as urgent. That is enough to find out whether your problem is personal discipline—or a workday designed to keep you reacting.