Low Clarity + High Demand = Overwhelm

The conversation goes the same way every time. A deadline that was comfortable three weeks ago isn't anymore, or a piece of work that looked self-contained turned out to be tangled up with six other systems. Within twenty minutes we're debating capacity plans: hire, reshuffle, tighten priorities. Within the hour, the argument is back: adding people to a messy situation doesn't help unless their explicit job is to un-mess the thing.

After years of having that conversation, including more than once when I was the person stuck in the mess myself, I've come to believe overwhelm almost never runs on volume alone. It runs on the collision of two forces: high demand and low clarity. Either one alone, people cope with. Put them together and you get paralysis, burnout, and a cycle that feeds itself.

Volume alone rarely breaks people

Think for a moment about the last time you felt genuinely overwhelmed. Was the pile of tasks actually too tall? Or did you find yourself not knowing which piece mattered, who owned the next step, or what finished looked like?

We can pull some useful vocabulary from John Sweller's cognitive load theory.

• Intrinsic load is the inherent complexity of the task.
• Germane load is the effort that builds lasting understanding.
• Extraneous load is everything unnecessary the environment dumps on top.

A well-run organization concentrates effort on the first two. In a poorly-run one, extraneous load eats everything else.

Fuzzy strategy forces people to guess at priorities. Fuzzy ownership drops critical work between the seams. Fuzzy success criteria keep the finish line invisible. Fuzzy communication routes the same message through five channels and still misses the person who needed it.

All of this is extraneous load, and it does not stack politely. It compounds.

The danger zone

In Wiring the Winning Organization, Gene Kim and Steven Spear describe two very different environments for problem-solving. The "winning zone" has well-bounded problems, cheap failures, enough time to think, and clear signals when something goes wrong. The "danger zone" has tangled problems, costly failures, compressed time, and broken feedback loops that let things fester unnoticed.

One of their findings that has stayed with me: the same people who flail in the danger zone produce exceptional work in the winning zone. What changes is the system around them.

Low clarity is how a team ends up in the danger zone. Priorities blur and every task starts to feel urgent. Ownership gets foggy and problems either get solved twice or not at all. Feedback loops break, and minor issues become crises that nobody saw coming.

Layer high demand on top of that and people lock into permanent reactive mode. There's no space to plan because there's always a fire, no time to learn because the next deliverable is already late, and no energy for improvement because the firefighting required to keep the system running consumes whatever energy remains.

Every fire costs twice

When clarity is low and demand is high, delivery chaos becomes the default state. It demands heroic effort to keep things moving. That's the first cost, and it's the visible one: attention, focus, and delivery time spent holding the current crisis together. On its own, that cost is survivable.

The second cost is where the real damage lives. Heroics burn people out. Burned-out people leave and take their hard-won operational knowledge with them. That loss makes the next delivery worse. For a while, continued heroics can still keep things moving, but each round takes more effort to produce the same result. Eventually, compressed margins choke off the investment that would have built the system to stop the fires in the first place.

A team pushes a quick fix at midnight to keep production running. It works. Three months later that fix interacts with a different change someone made independently, and a new failure shows up that nobody can trace back to the original night. The fix was right for the fire. It was wrong for everything that came after.

From there, the cycle accelerates, and it rarely slows on its own.

High performers amplify the signal they're given

The instinct in a crunch is to lean harder on your best people. They'll figure it out. They always do.

I've been that person. For a stretch of several years, I was the central knowledge-holder for a payment-processing and financial-reconciliation setup, covering both the data side and the systems side. Deadlines stayed tight, ownership stayed fuzzy, and acceptance criteria never got concrete enough for anyone else to step in. Every time anyone asked how we could move faster, I had to defend why we couldn't, and every time I did, the answer embedded me deeper into the work. Knowing the theory didn't help. The system was running on the basis of my ability to hold it together while working to stabilize it. Stopping long enough to build the clarity that would have freed me meant missing the next deadline.

High performers are force multipliers, and a multiplier amplifies whatever signal the system is emitting. A high performer in a clear system compounds the work. The same person in a murky one just amplifies the ambiguity. Your best people work longer, decide faster, take on more ownership, and in the process build a shadow structure that quietly covers for the dysfunction. That arrangement holds until they burn out and leave, at which point everything they were privately holding together unravels at once.

Adding people to an unclear system makes it less clear.

"Hire better people" delays the reckoning by substituting system design with hope. Every talented person absorbing chaos on behalf of the organization is one resignation away from the structure collapsing in plain view.

Brooks's Law says adding people to a late project makes it later. The same logic, extended: adding people to an unclear system makes it less clear.

Clarity as infrastructure

Clarity doesn't mean process or bureaucracy. It means knowing who decides, agreeing what "done" looks like before work begins, and a new hire becoming productive in weeks rather than months because the organization can describe how it operates instead of asking every newcomer to reverse-engineer it.

Three levels hold up clarity under pressure.

What game are we playing? A firm that can't decide whether it sells premium expertise or commodity delivery ships inconsistent quality, confused pricing, and frustrated teams. Strategic ambiguity cascades into every engagement.

Who owns what, by when, to what standard? Without operational clarity, handoffs turn into negotiations, dependencies arrive as surprises, and deadlines become soft guesses nobody actually trusts.

How do we share knowledge, raise problems, and respond when something goes wrong? Without cultural clarity, people default to self-protection. Information gets hoarded because sharing feels risky. Bad news gets buried because surfacing it has no obvious upside. Mistakes repeat because the last time they happened, nobody wrote down the lesson.

When all three are present, organizations absorb high demand without breaking. People move fast because the rails are there. When any one is missing, demand is eventually what exposes the gap.

The kindness trap

One of the most damaging patterns I see is when organizations substitute pleasantness for clarity. It's common, maybe especially in Nordic workplaces where conflict avoidance gets dressed up as culture. Hard conversations about performance get deferred. Role boundaries stay deliberately fuzzy "to keep things flexible." Accountability goes unenforced because it "doesn't feel right."

Leaders doing this think of themselves as kind. The people living inside the ambiguity experience it as neglect.

Unspoken expectations go unmet. Feedback hoarded for annual reviews turns small corrections into major confrontations. Problems nobody owns become failures that everyone experiences personally.

Ambiguity damages relationships far more than directness ever does.

This pattern shows up across organizations. A team member's work isn't quite landing. The leader senses it but the conversation never quite happens. Each check-in returns the same reassurance: "You're doing fine, keep at it." The team member, sensing unease the leader won't name, asks repeatedly what they should adjust. They're told nothing is wrong. Months later, when the assignment finally gets pulled, the leader recalls offering "every chance." The team member recalls being kept in the dark.

This is why the kindness trap is so durable. The warmth is real. The choice to avoid the harder conversation gets framed, to both parties, as care. Only the person living inside the ambiguity can tell the two apart. By the time they can articulate it, they're usually already leaving.

Breaking the equation

If overwhelm is the product of low clarity and high demand, the leverage point is obvious: raise clarity. You may not be able to lower demand (and often shouldn't try). But you can change the conditions in which people meet that demand.

Leaders doing this think of themselves as kind. The people living inside the ambiguity experience it as neglect.

Three mechanisms, grounded in Kim and Spear's framework (they call them slowify, simplify, and amplify):

Make problems visible (amplify). Build feedback loops that surface issues before they're crises. Teach people how to deliver bad news. Make "I don't know" and "this is broken" signals that trigger help instead of blame. Invisible problems compound silently. Visible ones get solved.

Create space for planning (slowify). Under pressure, humans default to reactive thinking, and novel problems need reflection. Protect time for planning before execution, for practice before performance, for learning before the next sprint. Slowing down in the right places is what makes the whole system faster.

Reduce unnecessary complexity (simplify). Not every piece of complexity deserves to be cut; the inherent complexity of the work is where the value lives. But the accumulated processes, approval chains, communication channels, and coordination overhead that nobody ever designed deliberately? That's organizational debt. Audit it. Trim it. Every unnecessary step you remove frees cognitive capacity for work that matters.

The test

A simple diagnostic. Notice how often you answer the same question for different people in a given week. You don't need a tally; you'll feel it. Every recurring question whose answer lives in your head rather than in the organization means you've become the coordination layer the system should have built for itself. That load is what you were feeling.

For a deeper read, ask three questions separately to every person on your team:

1. What's the most important thing we're trying to deliver this quarter?
2. Who decides when it's done?
3. What do we do when we're stuck?

Scattered answers tell you which level is leaking: strategic, operational, or cultural.

If either signal shows up, workload probably isn't the bottleneck. Clarity is, wearing workload's clothes.

Overwhelm that comes from ambiguity is a design failure. Design failures can be fixed.

Continued in Decision Velocity = (Clarity × Confidence) / Complexity: what it takes for clarity to convert into action.