A Pace You Can Sustain: Beating the Infinite Workday

The quiet substitution

The promise of "Do more with less" was meant to be about efficiency: better tools, smarter processes, less waste. For many teams though, it became something else: do more with fewer people and less time in the day. The workday didn't get more productive for some; it got bigger, spilling past the natural edges of the work day until it had no edges left. Microsoft's researchers gave the result a name that lands because it's true: the infinite workday. Their data describes it precisely. The average employee is interrupted every two minutes. Meetings after eight in the evening are up sixteen per cent year on year. The day has fractured into a "triple peak": morning, afternoon, and a third shift late at night to catch up on the work the meetings displaced. And the human verdict is clear: around half of employees, and more than half of leaders, say their work already feels chaotic and fragmented.

Into that, we're now adding AI, and here's the fork in the road. Microsoft's own researchers warn that AI can either rescue people from the infinite workday or pour fuel on it, depending entirely on the choices leaders make. Used to clear away low-value work, it creates space. Used to cram more in, it simply raises the metabolic rate of an already-overheating system. Which it becomes is a leadership decision, not a technological inevitability.

Recovery is part of performance, not its opposite

The instinct under pressure is to treat rest as the thing you do once the work is finished, and since the work is now infinite, rest never comes. The science says this is exactly backwards. Research on recovery, notably Sabine Sonnentag's work on psychological detachment, shows that people who genuinely switch off from work return sharper, more resilient and more productive; the detachment isn't time stolen from performance but an input to it. Microsoft's own Human Factors Lab found the point at the neurological level: back-to-back meetings measurably raise stress, while short breaks between them let the brain reset. Recovery isn't the reward for performance. It's one of its raw materials. An absolute must.

For a leader, that reframes a whole category of decisions. Protected focus time, genuine breaks, a real boundary at the end of the day: these aren't perks you grant a tired team. They're the conditions under which good work gets done at all. A team that never recovers isn't a high-performing team running hot; it's a high-performing team you're quietly spending down.

Protect the deep work

Sustainable pace and the closure discipline of post 3 are the same fight from two sides. The infinite workday is, at root, an attention problem: a day so fragmented the deep, valuable work has nowhere to happen except the late-night third peak. If you're constantly dealing with "fire drills" (urgent, important, unplanned tasks), that's a symptom of your system, not a cause: poor communication, poor cadence, poor planning. The remedy is a ruthless application of the eighty-twenty rule: protect the twenty per cent of work that drives most of the value, and use everything at your disposal, AI included, to strip away the rest. Fewer, better meetings. Defended blocks of focus. Permission to be unavailable. None of this is soft; it's the only way the work that matters gets the attention it needs.

Model it, or it isn't real

Of everything in this chapter, this is the part a leader cannot delegate. A manager's own behaviour is the loudest signal in the system. If you send messages at eleven at night, your policy on protected time is noise; your team reads the behaviour, not the memo, and quietly concludes the late-night third peak is what success looks like here. Sustainable pace is set by what leaders visibly do: when they log off, whether they respect a colleague's focus block, whether they take the recovery they tell others to take. Your team is as chaotic as you are, as always-online as you are, as stressed as you are. You are, whether you intend to be or not, the pacesetter. But such as easy fix to make, role-modelling the approach you want others to take means more than a statement of intent.

Stretch assignments, or stretching hours

A quick word on the classic productivity hack: the stretch assignment. In a world rewarded for impact, a stretch assignment easily becomes a way to create more impact. But a stretch that simply becomes a stretch in working hours, rather than a stretch in the person's skills and development, is the wrong stretch to reward. If your team's stretch assignments only consume longer hours and don't support their growth, that's a signal to help them make a change.

The shift

Doing more with less isn't achieved by doing more for longer; that road ends in a fragmented, exhausted team and an AI strategy that merely accelerates the exhaustion. It's achieved by protecting attention, designing for recovery, and using the capacity AI frees to create space rather than fill it. Pace isn't the enemy of performance. An unsustainable pace is.

We've now walked the whole argument. Which leaves the most practical question of all: where does your team actually stand today, and how do you move it forward? That's Part IV, and posts 10 and 11.