Seeing the Limits: Why Organizational Underperformance Persists When Everything Looks Sufficient
Knowledge workers spend 58 percent of their day on what Asana calls “work about work”: meetings, coordination, status checks, information searches, and other activity that surrounds the work they were actually hired to perform. In its 2023 Anatomy of Work Global Index—a survey of 9,615 knowledge workers across six countries—respondents estimated that better processes could save them nearly five hours each week.
Organizations invest heavily in people, technology, systems, and management capacity, yet some of that capacity is consumed before it ever reaches the result leaders actually care about. A product launch may appear fully resourced—people, budget, technology, executive support—yet deadlines keep slipping. The default assumption is that something must be missing: more staff, more time, better tools. Sometimes that diagnosis is correct. Demand can genuinely exceed what is available.
But sometimes the organization already has what it needs.
Authority sits in one place, expertise in another. Critical information arrives too late. Competing priorities pull key people elsewhere. From a distance, the organization looks well resourced; up close, performance tells another story. The question is whether those resources can actually come together when the work requires them.
Management research on resource orchestration makes a related point: possessing resources is not enough. Managers still have to structure, bundle, and leverage them effectively. Possessed capability is not the same as usable capability.
A fighter squadron may have 23 aircraft assigned, but only 20 may be fully mission capable; fewer still may be ready to launch. A company may have the equipment and expertise to print a customer’s book, but if its production schedule is fully committed for the next three months, that capability is not available to that customer today.
What an organization can do in general is not necessarily what it can do here and now for a specific requirement. That distinction is easy to miss from the executive level. Leaders see aggregate figures—staffing, equipment, funding, nominal capacity—that suggest sufficiency. Those figures do not show what is actually available for the need in front of them.
When that gap blocks an otherwise achievable result, the result may still be within reach.
I call this condition suspension.
Suspension is narrower than a general capacity or constraint problem. The outcome is still achievable, but something required to produce it is not available when needed.
Is the Outcome Still Achievable?
Not every unrealized outcome is suspended. Some opportunities are gone, some were deliberately abandoned, and others were never feasible.
Before calling an outcome suspended, three conditions should hold:
The opportunity still exists. The relevant deadline, customer need, mission window, market opportunity, or decision period has not closed.
At least one viable pathway remains. There is still a credible way to produce the outcome.
What that pathway requires can still be made available in time. Resources, authority, information, dependencies, and capacity do not have to be available now, but they must still be obtainable within the relevant window.
If something indispensable can no longer be recovered, substituted, restored, or accessed in time, the outcome has moved from suspension to loss.
This is an achievability test, not an economic one. Something can remain possible and still not be worth pursuing. The money, risk, disruption, or management attention required may outweigh the value of the result.
If the outcome is still achievable, the next step is to identify what is preventing it.
Why the Real Limit Can Stay Hidden
Organizations are remarkably good at keeping things moving. People create informal workarounds, parallel tracking systems, alternate handoffs, and other ways to get around weaknesses in the formal process. These adaptations are often sensible. Sometimes they are why the operation works at all.
They can also make the underlying weakness harder to see. Temporary fixes become part of daily operations, and the official process may stay on paper while the real operating model grows around it.
Key performance indicators may continue to look acceptable even as the hidden cost of sustaining them rises. Leaders see the output, but not necessarily the burden behind it: more coordination, more searching, more escalation, and more management attention just to hold the line. The operation may still appear healthy while becoming more expensive and more fragile to run.
For executives, that can show up as margin erosion, slower response, overloaded managers, greater dependence on a few experienced people, and less capacity to absorb the next disruption. An organization may believe it has room to take on more when much of that capacity is already being used simply to maintain current performance.
These workarounds can hide the problem from leadership. By the time underperformance becomes visible, the place where it shows up may be far removed from the source. Where performance breaks down is not necessarily where the problem began.
Not every source of friction is technical. Incentives, authority, risk, and self-interest can also shape what gets reported, resisted, delayed, or worked around. That deserves a fuller treatment elsewhere.
Start With the Outcome, Then Work Back
Start with the result you expected: What should be happening, but isn’t?
Then work backward. What had to happen for that result to occur? What did not happen? Where did the work slow, stop, or depend on something that was not available when needed?
The goal is not to identify every weakness in the organization. It is to find what is actually preventing the result.
That idea is similar to the Theory of Constraints, which focuses attention on what is limiting overall performance. Here, the question is narrower. We are starting with a specific result that has not occurred and asking whether it is still achievable and, if so, what is preventing the organization from producing it.
The answer may be a capacity constraint, but it may also be a delayed decision, missing information, unavailable expertise, competing priorities, or a dependency that was never resolved.
From there, the work is straightforward: define the outcome, establish that it remains achievable, identify what is holding it back, choose the least burdensome intervention likely to improve the result, trace the consequences that matter, measure what changes, and reassess.
Finding the source of the problem is only half the job. The next decision is what to change and what that change will affect elsewhere.
The First Explanation May Be Wrong
A growing backlog may be interpreted as a staffing problem. But if most of the work is waiting on the same decision point, adding staff may only increase the work piling up in front of it. The organization takes on more payroll and coordination, but if the decision point is left unchanged, work still clears at the same rate.
Before acting on the staffing explanation, ask whether staffing is actually causing the delay.
If the problem is decision capacity, the next question is what can be moved, simplified, delegated, or automated without creating a larger problem. Routine decisions might move elsewhere. Some activity might be standardized. The person with authority may be spending too much time on work that does not require that level of judgment.
Each of those options creates work or cost somewhere else. Delegation shifts work to someone else. Automation brings acquisition, implementation, maintenance, training, and technical dependence. Simplification may remove controls that were put there for a reason.
A change in one part of the system can create new work somewhere else. That does not make the change wrong; it means the trade has to be examined.
How Far Down the Consequence Chain?
You do not have to chase every consequence.
You can stop following the consequences once the remaining effects are small enough to absorb, already fit within available capacity, or cost more to address than they are worth.
Relieving one bottleneck may expose another. That does not mean the first intervention failed. It may simply mean that once one problem is reduced, another becomes more visible.
In the end, the question is whether the change improved the original result enough to justify its cost and disruption.
Did the Outcome Actually Improve?
Organizations are usually better at measuring activities, departments, and functions than at measuring the result those activities are supposed to produce. That can make local improvement look more important than it is.
A faster process step, lower departmental cost, or higher utilization rate may all be legitimate gains. But if the outcome that justified the intervention barely changes, those gains are limited.
Return to the original result. Did performance improve? Did the cost or effort required to achieve it fall? Did the change shift the burden somewhere else? Has a different obstacle now become more important?
Those questions help distinguish real improvement from a local gain that does not materially improve the overall result. If the result improved enough to justify the cost and consequences, the change was probably worthwhile. If not, either the diagnosis, the response, or both need another look.
Seeing the Limit
Organizations can possess substantial capability and still fail to deliver outcomes that remain within reach. The gap often lies between what exists in aggregate and what can actually be assembled and used for a specific requirement. Suspension describes the narrower case in which the opportunity remains achievable but something needed to produce it is unavailable, delayed, committed elsewhere, or otherwise out of reach.
The goal is not to remove every limitation. Some are worth changing; others are not.
Sometimes the answer is more capacity. Sometimes the capability already exists but is unavailable when needed. Sometimes the better decision is to stop spending time, money, or attention on work that contributes too little to the result. And sometimes the limitation should remain.
Leaders do not need organizations without limits. They need to know which limits are worth changing.
That is the limit worth seeing.
Comments