How Organizations Create Overwhelm By Design

There's a meeting on your calendar that didn't need to exist.

You know the one. Sixty minutes of eleven people watching two people talk, while the other nine compile their own to-do lists in the notes app and pretend to look engaged.

Nothing gets decided. A follow-up meeting gets scheduled to discuss what should have been decided. You leave forty-five minutes behind on work that actually needs doing, and somehow this is just Tuesday.

And somewhere in the middle of all of this, you started wondering what was wrong with you.

Nothing is wrong with you.

The system was designed this way. Not maliciously, in most cases. But by accident, by habit, by decades of organizational choices that optimized for the appearance of productivity rather than actual output.

And you've been absorbing the consequences of those choices while being told it's a capacity problem you need to solve with better habits.

This week, we're naming the design.

When I say organizations create overwhelm by design, I don't mean someone in a boardroom decided to make your life hard.

I mean something more insidious:

the structures and systems that govern how work happens were built with a set of assumptions that no longer reflect reality, and in many cases were never built to reflect the reality of the people doing the actual work.

Design is what happens when someone makes a choice about how things will work.

The always-on expectation solidified before smartphones made it technically possible to be always on, which means there was never an intentional decision to make that the norm. It just became one.

The result is a workplace infrastructure built for a workforce and a context that no longer exists, being operated by real people in real constraint, and generating chronic overwhelm as a predictable, structural output.

Not as a side effect. As an output.

When you put certain inputs through certain systems, you get certain results. Organizations have built systems that reliably produce overwhelm. The people moving through those systems experience it as personal.

They weren't meant to.

These aren't the only ones. But these are the ones your nervous system knows intimately.

Meetings are the most expensive communication tool an organization has. They require the simultaneous attention of multiple people, interrupt individual flow, and generate a disproportionate time cost relative to what gets decided or communicated.

And yet meetings are the default. Not email, not documentation, not asynchronous tools. Meetings. Because they feel collaborative. Because they're schedulable. Because they create the visible appearance of work happening.

The design failure: organizations default to meetings for everything that doesn't require meetings, and then treat the resulting calendar saturation as an individual time management problem.

If your calendar is full and your actual work is happening in the margins at 6am and 9pm, that is not a personal scheduling failure. That is a meeting culture that has consumed the space in which work was supposed to happen.

Urgency is addictive. It focuses attention, bypasses deliberation, and creates the feeling that something important is happening. Organizations that have normalized chronic urgency often don't know how to function without it. The urgency has become the signal that work matters.

The design failure: when everything is urgent, nothing is. But more practically, sustained urgency creates a cortisol environment that degrades the cognitive capacity required for complex work. The same organizations that generate constant urgency then wonder why their teams struggle with innovation, strategic thinking, and quality output.

You cannot sprint indefinitely. Physiologically, you cannot. When you feel like you're falling behind despite working at maximum output, check the urgency design before you check your productivity system.

The reply-all email. The fifteen-person meeting. The Slack channel with forty members where updates relevant to four people are broadcast to everyone because "visibility is important." These are all versions of the same design failure: treating information volume as a proxy for inclusion and transparency.

Real inclusion is people having the information they need to do their jobs and make good decisions. Information overload is the opposite of that. When everyone gets everything, the cognitive cost of filtering relevant from irrelevant becomes an unpaid, unacknowledged part of everyone's job.

You spend genuine working hours reading things that don't require your attention, attending meetings that don't need your presence, and managing a flood of inputs that were sent your way because excluding you felt exclusionary. This is a design problem. It has a design solution. It has not been solved because it requires someone to make careful decisions about who actually needs to know what, and that's harder than copying everyone.

Organizations reorganize when things feel unclear, when leadership changes, when strategy shifts, when results disappoint. Restructuring signals action. It's visible. It demonstrates that something is being done.

The design failure: reorganization is expensive and disorienting, and it's frequently used when the actual problem is process, culture, or resourcing, not structure. People who've been through multiple restructures in a short period (and midlife professionals often have) carry an accumulated cognitive and emotional load that doesn't get acknowledged in the next restructure.

Each reorganization means relearning relationships, re-establishing credibility, re-navigating informal power structures, and often re-doing work that was in progress. The cost is borne by individuals. The decision was organizational.

Being seen working is not the same as working. But many organizations have built systems, cultures, and performance expectations that reward visibility over output. Being first in. Staying late. Responding to the 8pm email. Having a full calendar. Being available.

These are visibility signals. They're not necessarily output signals. But in the absence of clear output metrics, visibility becomes the measure, and organizations optimize for what they measure.

If you feel compelled to perform busyness, to signal effort through hours rather than outcomes, to respond to messages at all hours because absence of response reads as absence of commitment, you are living inside a visibility culture. It is exhausting by design, because it requires continuous presence rather than sustainable contribution.

This one might be the most damaging. When overwhelm becomes visible, the organizational response is frequently some version of resilience: workshops on stress management, wellbeing benefits, mindfulness apps, EAP programs. These are not without value. But they are offered as the solution to a structural problem.

Teaching individuals to be more resilient within a system that generates chronic overwhelm is like giving people better shoes to run on a treadmill that keeps accelerating. The shoes don't address the treadmill.

The design failure is treating the human as the variable to be adjusted rather than the system. And the insidious part is that resilience framing puts the burden of an organizational failure back onto the individual. You're overwhelmed because you haven't developed enough resilience. Not because the system is generating more than any human can sustainably absorb.

You didn't start your career in the organizations that exist today. The accumulation of design failures, the layering of communication tools, the normalization of always-on, the volume of restructures, these have built up over time, and you've absorbed each layer.

You also carry more context. Early career, you were in fewer meetings because your presence wasn't required. Now it is. You have more relationships to maintain, more stakeholders to navigate, more institutional memory to hold. Your cognitive load is higher because your role is more complex, not because your capacity has declined.

And you're doing this while managing life at full volume. Children who may be teenagers or young adults with their own complex needs. Ageing parents who need increasing support. Your own body requiring more maintenance than it did at 28. Relationships that need tending. A sense of your own identity and purpose that midlife has a habit of questioning.

The organization doesn't see most of this. It sees a professional with experience and capability, and it loads accordingly. The design failure is that the loading assumes a single-focus, fully available, domestically-supported professional. It always did. It just didn't apply to you back then.

You might be wondering what practical difference it makes to understand that overwhelm is structural rather than personal. You still have the same calendar. The same volume of email. The same urgency culture bearing down on you.

It stops the self-diagnosis spiral. When you believe overwhelm is a personal failing, you spend cognitive energy on self-criticism, self-improvement schemes, and the exhausting work of trying to be more.

Naming it as structural frees that energy.

It changes where you look for solutions. Individual overwhelm calls for personal coping strategies. Structural overwhelm calls for structural responses. Once you know you're dealing with the second, you can stop trying to solve it with the first.

The solutions look different. They involve renegotiating scope, changing communication norms within your sphere of influence, setting structural constraints rather than trying to manage inputs individually.

It gives you language. For the people you manage. For the conversations with leadership. For yourself when you're explaining to your partner why you came home depleted again.

"I'm overwhelmed" sounds like a personal state. "The system is generating more inputs than any human can process sustainably" is a systems analysis. One invites sympathy. The other invites action.

It separates what you can change from what you can't. Some structural failures are outside your control to fix. You cannot single-handedly reform meeting culture across an organization.

But you can change what happens within your own sphere. Your team's meetings. Your communication norms. Your response time expectations for the people you work with. Naming the design helps you see the difference.

This is not a list of productivity hacks. Those belong to a different conversation. This is about the smallest structural moves available to you, within the system as it exists.

Before you can change anything, you need to see it clearly. The Organizational Overwhelm Audit at the end of this issue will help you map where the design is broken in your specific context. Not to fix everything at once. To see what you're actually working with.

When you're overwhelmed by a specific thing, pause before you find a personal coping solution. Is this an information overload problem? A meeting culture problem? An urgency problem? The category matters because it points toward where the solution lives.

You probably can't eliminate the all-hands meeting. You might be able to stop scheduling thirty-minute check-ins that could be a Slack message. Small changes in your own practice compound, and they model different norms for the people around you.

This one costs something socially, and I won't pretend otherwise. But every time you respond to the 9pm email immediately, you signal that this is acceptable and reciprocal. Where you have any margin to set different norms, setting them changes the system, incrementally, imperfectly, but really.

In the room where decisions get made, or in the conversation with your manager, naming the structural cause rather than the personal effect changes the conversation.

"I'm struggling to manage my workload" sounds like a me-problem. "Our team is absorbing four restructures' worth of transition work with no capacity adjustment" is a them-problem that needs a them-response.

The audit below is not a wellness exercise. It's a systems diagnostic.

The goal is to map where overwhelm is being generated in your organizational context, so you can see the design failures clearly rather than experiencing them as undifferentiated exhaustion.

Work through each section honestly. You don't need to share this with anyone. It's information for you.

Don't try to fix everything. Look at your audit and identify the single area generating the most overwhelm. Just one. Then identify the smallest structural change within your control that would reduce the load in that area.

That's your Week 7 action. One area. One smallest viable move.

The organizations most people work in were not designed for the humans inside them. They were designed for efficiency metrics, quarterly results, legacy processes, and a workforce that looked very different from the workforce that actually exists.

You are not failing to adapt to a well-designed system. You are a human being absorbing the consequences of a system that was never designed with you in mind.

Naming that is not defeatism. It's accuracy. And accuracy is where sustainable change begins.

The design can be worked with, worked around, and in some cases, changed. But not while you're blaming yourself for being affected by it.

Next week, we go deeper into the personal cost: what happens to your sense of identity and self when overwhelm stops being temporary and becomes your permanent operating mode.

See you then.

Mia x

Flow & Thrive Journal | empoweredmidlife.co.uk The Midlife Reality Files runs weekly. If someone forwarded this to you and you'd like to subscribe, you can do that here.

Here’s to finding your flow,