Deep work under siege

We have more tools for concentration than any generation of knowledge workers before us. Noise-cancelling headphones. Focus-mode toggles on every device. Apps that block other apps. Pomodoro timers shaped like tomatoes, because apparently the fruit was the missing variable. And yet the average knowledge worker in 2024 is interrupted roughly thirty-one times per day and spends seventy per cent more time in meetings than they did in 2020. We built an arsenal of focus tools and then used them to decorate the margins of a calendar that belongs to everyone else.

The paradox is worth sitting with. The era that gave us the most sophisticated attention-protection technology also produced the most fractured attention in the history of office work.

Something went structurally wrong, and it was not a failure of willpower.

The meeting creep nobody voted for

Remote work was supposed to liberate us from conference-room culture. And for about six months in 2020, it did. Calendars opened up. People reported thinking more clearly, working in longer unbroken stretches, rediscovering what it felt like to hold a problem in their head for ninety continuous minutes. But then something predictable happened. Organisations, nervous about losing visibility into what people were doing, replaced physical presence with digital presence. The stand-up became a video call. The hallway check-in became a scheduled slot. The informal whiteboard session became a recurring ceremony with a calendar invite, a Zoom link, and an implied obligation to keep your camera on.

But the real damage was not any single meeting. It was the cumulative architecture. When your calendar has six meetings scattered across the day, you do not have six meetings and several hours of free time. You have six meetings and several fragments of time too short to hold a real thought.

Deep work does not happen in the gaps between meetings. The gaps are where it goes to die.

I watched this unfold at Grab in real time. We were building products for markets across Southeast Asia, and the coordination overhead was genuine. Different time zones, different regulatory environments, different user behaviours by country. But the response to that complexity was more synchronous meetings, not fewer. By the time I mapped a typical product manager's week, the picture was grim: twenty-three hours of scheduled meetings. That left seventeen hours in a standard forty-hour week. But those seventeen hours were not contiguous blocks. They were confetti. Fifteen minutes here, twenty-two minutes there, a luxurious forty-five-minute stretch on Thursday afternoon that inevitably got claimed by a "quick sync."

The most important product thinking of the quarter was supposed to happen inside that confetti.

Why willpower fails and architecture works

The common advice is to "protect your focus time." It sounds reasonable. But it frames the problem as an individual discipline challenge, which is a bit like telling someone to protect their lungs while the building fills with smoke.

I learned this the hard way at Freshworks. I had adopted the habit of blocking two-hour focus windows on my calendar every morning. Colour-coded them red. Labelled them "Deep Work, Do Not Book." For the first two weeks, it worked beautifully. But by week three, the blocks started getting overridden. A stakeholder would message: "I see you have something from 9 to 11, but this is urgent." And because it was on a screen, not behind a closed door with a physical lock, the social cost of declining felt higher than the cost of surrendering the block.

This is the pattern I call The Focus Fortress problem. You can build the walls. But if the culture treats every wall as negotiable, you have built a suggestion, not a structure. The fortress has to be embedded in something the organisation recognises as legitimate, or it will be breached every time someone has a "quick question."

What finally worked was not individual calendar blocking. It was team-level agreements. When a product trio agrees that mornings before 11 a.m. are synchronous-meeting-free, and when engineering leadership reinforces that norm, the fortress becomes structural. One person's red block is a request. A team's shared norm is architecture.

Nobody argues with architecture.

Calendar Negative Space

The concept I keep returning to is what I think of as Calendar Negative Space. In photography and design, negative space is not emptiness. It is the deliberate absence that gives the positive elements room to breathe, room to mean something. A calendar works the same way. The unscheduled time is not leftover time. It is the most valuable time on the calendar, the time where the actual product thinking happens.

But most organisations treat calendar negative space as inventory to be consumed. If a slot is open, it is available. If it is available, someone will claim it. The calendar operates like a gas, expanding to fill every container.

I once asked a product director at a large petroleum company how many hours per week she spent in genuinely generative thinking. The kind where she was holding a user problem in her mind, turning it over, connecting it to business constraints, sketching possible solutions. She paused for a long time. "Maybe two," she said. "On a good week." But she was working fifty-hour weeks. Ninety-six per cent of her time was the mechanics of product work. Four per cent was the thinking that product work actually is.

That ratio is not unusual. It is the norm.

The calendar had become the product, and the product had become an afterthought.

So what does an architectural defence look like in practice? Three things I have seen work consistently. First, time-box the shallow work instead of the deep work. Schedule your meetings into a defined afternoon window and let the morning be unstructured by default. Now the burden of proof shifts: someone who wants your morning has to justify pulling you out of deep work, rather than you having to justify staying in it.

Second, make the cost of interruptions visible. At Grab, I started logging every interruption for two weeks. Not to shame anyone, but to create data. My most productive ninety-minute stretch had produced more measurable output than three full days of fragmented work combined. Data does not fix culture by itself. But it gives reformers something concrete to point at.

Third, negotiate at the team level. A single person blocking focus time is making a personal lifestyle choice, easy to override. But a team agreeing that certain hours are sacred is establishing a working norm. Norms are much harder to breach than preferences.

The maths over time is stark. A product manager who gets three hours of uninterrupted thinking per day will, over a quarter, accumulate roughly sixty hours of deep work. A product manager whose focus is sliced into fifteen-minute fragments will accumulate close to zero usable hours, because cognitive switching cost eats most of each fragment before real thinking begins. But both will appear equally "busy" in any utilisation report.

You cannot think your way to a better product in eleven-minute increments between stand-ups.

If you are recognising this pattern in your own calendar, the intervention is not another productivity hack. It is a conversation with your team about what you are collectively willing to protect. The tools already exist. The headphones are on your desk. But the architecture of your day has to make room for the thinking your role actually requires, or no tool will save you. That is not a discipline problem. It is a design problem. And product people, of all people, should know the difference.