> ## Content Index > Fetch the complete content index at: https://www.leadingwithempathy.blog/llms.txt > Use this file to discover other available public pages before exploring further. # When Productivity Pressure Is Really a Capacity Problem - URL: https://www.leadingwithempathy.blog/when-productivity-pressure-is-really-a-capacity-problem/ - Published: 2026-10-06T06:30:52.000Z - Updated: 2026-10-06T06:30:51.000Z - Description: I could spend an entire day helping other people move forward and still finish feeling that I had accomplished nothing. The problem was not speed. It was a working day designed around unlimited access to my attention. - Author: Megan Tipps - Tags: Engineering Leadership, Sustainable Leadership, Workplace Productivity, Capacity Planning, Focus Time, Developer Culture, Management, Team Support, Context Switching, Workplace Wellbeing I have had working days so full that there was barely enough space between meetings to eat lunch, make coffee, or go to the bathroom. One meeting ended and another began. Somewhere between them came messages, questions, approvals, reviews, and problems that apparently could not wait. By the end of the day, I was exhausted. I had been busy almost continuously, but the meaningful work I had planned to do was still sitting exactly where I had left it that morning. It felt as though I had accomplished nothing. That was not completely true, of course. Other people had moved forward because I had answered their questions, reviewed their work, made decisions, joined their meetings, solved their problems, and kept the team functioning. The day had produced plenty of activity. It had simply produced very little of the work for which I was personally responsible. There is a particular kind of frustration in spending an entire day completing pieces of other people’s work while watching your own deadlines drift further away. It is difficult to explain because, from the outside, you may look helpful, involved, and essential. Inside, you feel as though you are failing at the work with your name on it. For a long time, I felt bad about that. I thought I should be better at fitting everything in. Perhaps I needed to plan more carefully, answer messages faster, or become more efficient between meetings. Maybe the problem was that I had not yet discovered the correct combination of calendar blocks, task lists, colour coding, and mild panic. But the problem was not that I needed to move faster. The problem was that the working day had been designed around unlimited access to my attention. ## When everything can interrupt, everything does The fragmentation did not come from one source. It was meetings, messages, urgent questions, reviews, approvals, production problems, and constant switching between different kinds of work. I was one person doing what often felt like ten separate jobs. Was it healthy? Hell no. Did I learn a great deal about what to do and what not to do? Hell yes. But learning from an unsustainable situation does not make the situation sustainable. The [Microsoft 2025 Work Trend Index](https://www.microsoft.com/en-us/worklab/work-trend-index/2025-the-year-the-frontier-firm-is-born?ref=leadingwithempathy.blog) describes a similar contradiction at a much larger scale. While 53% of leaders surveyed said productivity needed to increase, 80% of the global workforce said they lacked enough time or energy to do their work. Microsoft’s workplace telemetry also found that employees were interrupted by a meeting, email, or notification every two minutes during core working hours. [2025: The year the Frontier Firm is bornIntelligence on tap will rewire business. Every leader needs a new blueprint. The time to act is now. The question is: how will you adapt?![](https://storage.ghost.io/c/f2/0a/f20a4bc9-33b9-4e69-b1f0-50e39b5f094f/content/images/icon/favicon-32x32-d6648002-02a7-449a-8ba4-b47b1c90b6ce.png)![](https://storage.ghost.io/c/f2/0a/f20a4bc9-33b9-4e69-b1f0-50e39b5f094f/content/images/thumbnail/WTI_APR2025_OG_ShareAsset_68090367108c2-dfd2dac5-8d51-4b82-8215-98fa3e8e7245.png)](https://www.microsoft.com/en-us/worklab/work-trend-index/2025-the-year-the-frontier-firm-is-born?ref=leadingwithempathy.blog) Those numbers help explain why a full day can feel strangely empty. Attention does not only disappear during the interruption itself. Every switch requires you to remember where you were, rebuild the context, and find your way back into the work. Sometimes you return. Sometimes the next notification arrives first. A calendar can therefore be completely full while a person’s actual capacity for focused work is almost nonexistent. ## Some work becomes expendable when its value is less visible In that company, I often had the sense that people were comfortable with my lack of progress because I was helping other people make theirs. Their work generated revenue. Mine included keeping the team happy, answering questions, supporting the culture, and holding together the small pieces that allowed everyone else to continue. When there was a conflict, their immediate need usually won. Nobody necessarily said that my work did not matter. The prioritisation said it for them. Supporting a team is real work. Maintaining a healthy culture is real work. Reviewing, unblocking, explaining, and making decisions are real work. Yet these contributions are often treated as background conditions rather than things that consume time and attention. This is closely related to the [invisible workload I have written about before](https://www.leadingwithempathy.blog/what-we-ignore-today-becomes-tomorrows-burnout-a-leadership-perspective/), but fragmentation adds another layer. The work is not only difficult to see. It arrives in pieces, attached to other people’s priorities, until there is no uninterrupted part of the day left for your own. The emotional effect was not simply tiredness. I regularly ended the day feeling that I had not accomplished anything. Other people had received what they needed from me, but I had lost the small sense of completion that comes from moving something meaningful forward. That feeling accumulates. You begin each morning carrying yesterday’s unfinished work, then watch today’s work join it. ## The answer was not another productivity trick Eventually, I started asking a simple question before accepting meetings: am I genuinely needed here? Not whether I could contribute. I could usually contribute something. Not whether attending might be useful. Many meetings can be made vaguely useful if you try hard enough. The question was whether the meeting actually needed me in order to achieve its purpose. That distinction helped me decline or shorten meetings that had been consuming time without requiring my involvement. I also began protecting focus time more firmly. I booked it in the morning before the day started, but I left the previous day open for people to schedule legitimate meetings. If someone had known about a meeting the day before, there had been an opportunity to add it. A sudden meeting on the morning itself needed a stronger reason to displace work I had already committed to doing. It was not a perfect system. Production problems still happen. People sometimes need help urgently. Leadership and technical work will always contain interruptions because work involving humans refuses to arrange itself into neat calendar rectangles. The boundaries did, however, make the interruptions more deliberate. They created a moment in which I could decide whether something truly needed my attention instead of allowing every request to claim it automatically. More importantly, they helped me recognise that I had some say in the shape of my working day. ## Capacity is part of how work is designed It is easy to respond to slow progress by asking people to become more productive. It is harder to look honestly at the environment in which that productivity is expected to happen. How much of the day is already committed to meetings? Who has become the default answer to every uncertain question? Are people able to make decisions without waiting for one person? Is review work included when deadlines are set? Does the person supporting the team have protected time for the work only they can do? If one person must remain constantly available for everyone else to progress, the team does not have a personal productivity problem. It has a dependency problem. That does not mean individuals are powerless until an organisation redesigns everything around them. Self-reflection still matters. We can notice which meetings repeatedly add little, which questions should have clearer ownership, and which interruptions we accept from habit rather than necessity. We can ask whether our presence is genuinely required. We can protect a small amount of time and treat that commitment to ourselves as seriously as a commitment to someone else. Not everyone has the same authority to decline meetings or refuse sudden requests. That is part of why managers and organisations need to examine how work is arranged. Personal boundaries help, but they cannot compensate indefinitely for unclear ownership, understaffing, or a culture built around permanent availability. Still, the first change for me was recognising that a packed calendar was not something I simply had to endure. I could question it. I could make different choices about access to my attention. I could stop treating my own work as the first thing that should be sacrificed whenever someone else needed something. I still believe in being available to people. Supporting a team remains meaningful work. But availability without boundaries eventually makes that support fragile, because the person holding everything together is left with no room to do their own work or recover their attention. A working day will never be entirely free of noise. The more useful question is whether we have allowed the noise to become the design. Sometimes the work does not need us to become faster. It needs us to decide, more consciously, what gets to enter the day. ## Building great software starts with how we lead people. I write about engineering leadership, team culture, AI, psychological safety, and the lessons I've learned from nearly two decades of building software and leading teams. Join Email sent! Check your inbox to complete your signup. New essays in your inbox. No spam. Unsubscribe anytime.