Pressure to Performance

Whether Your Incentive Structure Changes Is Already Being Decided. The Only Question Is by Whom

Mon, 15 Jun 2026 22:08:47 GMT

A framework for finding out where it actually stands, and whether the conditions for change are real.

The Moment After the Audit

If you completed the audit in my previous article on incentive structures , you have three answers. First, who got promoted and what behavior preceded it. Second, who made the last significant decision that generated rework and who absorbed the cost. Third, where effort is consistently consumed by rework, shifting priorities, or work that gets invalidated before it lands.

The instinct is to treat each answer as a separate problem with a separate fix. Adjust the promotion criteria. Clarify decision authority. Reduce rework. Three findings, three interventions, move on.

That instinct misses something. The three questions were not designed to produce three separate findings. They were designed to surface a pattern: what the incentive structure is actually doing across promotion, consequence, and effort simultaneously. Read separately, the answers point at symptoms. Read together, they point at something more important than what to fix. They tell you whether the conditions for change are present at all.

What the Pattern Reveals

Every incentive structure that produces misaligned outcomes is somewhere in a trajectory. It started somewhere. It has been running for some time. It has spread to some degree. And it has accumulated a level of investment that determines how hard it would be to change. The three answers from the audit are not just evidence of a problem. They are evidence of where the organization is in that trajectory. And evidence of whether the conditions for change are present right now, or whether the window has already started to close.

Three dimensions help locate where an organization is relative to that change readiness: scope, visibility, and investment.

Scope is how widely the pattern has spread. Is the cost spreading in one function, one decision maker, one part of the organization, or is it the operating logic at every level simultaneously.

Visibility is how much of the cost has already surfaced. Is it still below the waterline, showing up as operational noise, hedged effort, or conversations that were not happening before, or has it concentrated into metrics someone owns.

Investment is how entrenched the architecture has become over time. How long has it been running. How much has been built inside it, rewarded by it, promoted within it. How much resistance would redesign generate, from the people who have advanced inside it, from the political weight of decisions already made, from the time and effort it would take to change something that has been treated as the operating standard. The longer the architecture has been in place, the harder all of that becomes.

Your three answers are not separate data points. Read together, they point to where the organization likely sits on each of these dimensions. That picture is where the organization sits in the trajectory right now. And that position maps onto one of four clusters. Each cluster reflects two things at once: whether the cost has become visible enough to create motivation, and how much investment has accumulated around the architecture producing it.

The Four Clusters

These four clusters are not a severity scale, though severity is part of what distinguishes them. They are a change readiness map. Where you land tells you not just what the architecture is doing but how hard it would be to change it right now. At one end of that range is a cluster where the conditions for change align almost perfectly. At the other is a cluster where the difficulty is highest and hardest to see. The order below moves from that hardest case toward the one where everything aligns.

Investment blindspot. This is the most dangerous cluster. Not because the architecture is the most entrenched. It is because the entrenchment is accelerating while nothing visible suggests it should. Every day the organization waits, the architecture becomes harder to change, and nothing about how things look right now tells anyone that. Sunk cost is building, political weight is accumulating, and decisions that have been publicly backed are consolidating around people and commitments that redesign would call into question. The visible outputs still look acceptable. The leader feels more stability than the situation warrants. Structurally, the conditions for change are present. But by the time the cost becomes visible enough for anyone to notice, the architecture will be significantly harder to change than it is right now.

Systemic. The pattern is the organization. Scope is broad, visibility is high, investment is deep. The cost has surfaced on metrics leaders own. The architecture has been defended, promoted within, and built around long enough that it is difficult to separate from the organization's own history. The conditions for change exist. But changing it now is far harder than it would have been before the pattern became this visible and this widespread. More resistance, more to dismantle, more people with a stake in the current design. Not impossible. Just harder in ways that compound the longer it goes unaddressed.

Early signal. The pattern is present but contained. Scope is narrow, visibility is low, investment is limited. The architecture has not yet been running long enough or publicly validated through enough promotion cycles to make redesign politically costly. The conditions for change are present but the urgency is not. Leaders in early signal face a specific challenge: acting before the cost has given them an external reason to. That requires seeing the pattern clearly enough to treat it as evidence before it becomes undeniable. Most do not act here. Not because they cannot. Because nothing is forcing them to yet.

Visible drift . The cost is starting to surface. Scope has widened. The pattern is recognizable across more than one part of the organization. The investment is real but not yet prohibitive. This is the cluster where the case for change is most likely to be heard. The evidence is visible enough to name, the architecture has not yet been defended so publicly that redesign threatens everyone's record, and the cost of acting has not yet compounded to the point where the effort required makes it feel impossible. It is the easiest entry point for change. Not easy. The easiest.

Visible Drift: Where Diagnosis and Readiness Align

Visible drift deserves more than a paragraph because it is the cluster where something rare happens. This is the cluster where the problem is visible enough to diagnose and the architecture is not yet entrenched enough to make acting on that diagnosis politically impossible. Both of those things are rarely true at the same time.

The leader in visible drift can already feel something is wrong. Execution is slower than it should be. The people they most need to keep are starting to have different conversations. Strategy is not landing the way it was intended. But the explanations keep shifting. Talent. Market conditions. Competing priorities. The architecture has not yet been named as the source. The cost is visible. The attribution is not.

That attribution is what visible drift requires first. Not a redesign. Not a structural intervention. The recognition that what is surfacing is not a people problem or a strategy problem. It is the predictable output of an architecture that has been selecting for the wrong thing long enough to produce this. Naming that clearly, before the organization forces it, is what makes everything that follows possible.

It is also what makes visible drift the most realistic entry point for change. In investment blindspot, the psychology is already working against examination before the cost has surfaced enough to justify it. The leader feels stable, the outputs look acceptable, and looking harder feels disproportionate to the visible evidence. In systemic, looking clearly is not the obstacle. The obstacle is the scale of what looking reveals and how much of the organization's history is implicated in it. Visible drift has neither problem. The cost is real enough to name. The investment has not yet consolidated to the point where naming it threatens everyone who has built their record inside it.

That window closes. Visible drift does not stay visible drift. Left unexamined, the architecture continues producing the same outputs, the investment continues deepening, and the cost continues spreading. By then the conditions for change have not disappeared. They have just become significantly harder to meet. The same change that could have taken a conversation now requires restructuring the organization.

The Close

Recognizing which cluster you are in does not make action obligatory. A leader who sees the pattern clearly and chooses to wait may have a legitimate reason to do so. Given everything working against action, that can be the reasonable choice. But it is a choice. The architecture doesn't pause while you decide. It keeps doing what it was built to do, deepening the investment, narrowing the window, making the eventual change more expensive than it needs to be. That's not a choice. It's just what happens by default. Before you looked, the architecture was making that decision for you. Now you are.

The audit was the evidence. The cluster is the diagnosis. What comes next begins with the act of looking, clearly enough to see which cluster you are in, and honestly enough to let that change what you do next.

Your Incentive Structures Are Working Perfectly. That Is the Problem.

Sun, 17 May 2026 22:58:40 GMT

How organizations systematically reward the behaviors that erode their own performance capacity.

The System is Working as Designed

When something is not working, the instinct is to look for what is broken in the system. The talent. The structure. The culture. The strategy. Something failed, something needs fixing, and the search is for where the breakdown happened.

The system is rarely broken. The architecture underneath it is working exactly as designed. The problem is what it was designed to do.

The Cost No One Tracks

A senior leader calls a strategy meeting. The framing has shifted. The priorities that shaped the last quarter's work no longer apply, and a new direction is needed. The taxonomy the team built, the analysis they ran, the recommendations they spent the last quarter developing have been rendered obsolete.

The leader is praised for being responsive and agile in a shifting environment. Downstream, however, the people who built the work spend hours rebuilding. Those hours never get traced back to the decision that generated them. The recalibration that happens when people learn their work can be invalidated without consequence to anyone but themselves does not surface in a metric anyone owns. It lands on individuals as frustration, on teams as a subtle withdrawal of discretionary effort, and on the organization as capacity consumed with no one responsible for the loss.

The leader was praised for decisiveness. For agility. For being willing to course-correct when the environment demanded it. Those labels attached to their record. The cost of the decision attached to no one's.

This is not a story about a bad leader. It is a story about what rational behavior looks like inside an architecture that measures decisive action and ignores the cost of disruption.

The Architecture of Rational Behavior

When the person making a decision does not bear the consequence of that decision, the decision optimizes for the wrong thing. Not because the person is careless or self-serving by nature. Because the architecture makes that decision rational. Here is how.

Action is measurable. Decisions made, initiatives launched, pivots executed. These are discrete and attributable. They attach to a person's record and travel upward through the organization in the language of performance.

Operational cost spreads. The hours absorbed by rework, the cognitive load accumulated by teams navigating contradictory priorities, the effort-outcome disconnection that develops when people stop believing their work will survive the next change. None of it aggregates into a number anyone reviews. No one traces it back to the decision that caused it. By the time the cost is visible, the logic that produced it is unchanged and still selecting for the same behavior.

Most people inside the architecture are not doing anything wrong. They are doing what the architecture makes rational. The executive. The middle manager. The team lead. All of them responding to the same signal, at every level, simultaneously. This is why culture initiatives, values statements, and leadership development programs do not change it. They address how people behave. They do not touch what makes that behavior rational in the first place.

The Player and the Rulebook

The system reliably produces that behavior. Swap the leader, the conditions remain. The architecture does not change what it rewards because a different leader is inside it. That is not a leadership problem. It is a design problem. And the person with the authority to fix it is not standing outside the system looking in. They are inside it.

The people with the most authority to redesign the system are also the people the system is most actively rewarding. The people below them are paying the cost. It is spread across enough people and enough time that it does not yet concentrate into a number anyone reviews. The behaviors it rewards are making them look good. The case for redesign requires seeing costs that never show up in anything the architecture tracks. That is a difficult thing to see when the visible outputs look acceptable.

The player who absorbs the cost cannot fix the game. They do not have the authority. Only the person at the level where the rules are set can do that. Which means the intervention that matters most is only available to whoever creates the rules. The question is whether they are willing to look before the cost reaches them.

The Window

The cost does not stay where it lands. It moves in a predictable direction.

Early signals are diffuse and easy to misread. Execution takes longer than it should with no clear explanation. High performers start having conversations about scope and ownership that they were not having before. The people closest to the work begin hedging their effort, not visibly disengaging, but no longer going beyond what is required. These signals do not aggregate into a number anyone owns. They read as operational noise. They are not.

In the middle stage, workarounds become the system. Attrition begins among the people the organization can least afford to lose. The ones with enough options to leave and enough self-awareness to understand why they are leaving. What remains is a population increasingly shaped by who could not afford to go.

In the late stage it surfaces on a metric the leader owns. A strategy that never fully lands. An execution failure that cannot be explained by market conditions. A talent problem that hiring cannot solve. By then, the psychology works against action. The leader has defended this architecture, promoted people who operate well within it, staked their credibility on the decisions it rewarded. Redesign now means examining all of that. It is not just operationally difficult. It asks something most leaders find genuinely hard: to hold good intentions and misaligned outcomes in the same hand and act on what the evidence shows rather than what they meant to build.

The intervention window is the distance between when the signal first appears and when the cost is visible enough to have a leader’s name attached to it. Early signals are cheap to act on. The further the cost travels toward the leader, the higher the cost of acting. The longer that takes, the harder it becomes to act, because by then the leader has too much invested in the system to examine it honestly.

The Audit

The questions below will not close the window, but they will tell you where you are within it.

On promotion - Who got promoted in the last cycle, and what behavior preceded it?

Promotions are the moment where stated values and structural rewards either align or diverge. What your last cycle reveals is not what you believe you are selecting for. It is what the architecture is actually selecting for.

On decisions and cost - Who made the last significant decision that generated rework, and who absorbed the cost of it?

If the decision maker and the cost bearer are structurally separated, that gap is your architecture speaking louder than any values statement. Where that separation exists, the behavior this article described is not a question of if. It is a question of how much and for how long.

On effort and outcome - Where in your organization is effort consistently consumed by rework, shifting priorities, or work that gets invalidated before it lands?

That is where the performance cost of the current architecture is landing. It will not appear in a dashboard. But it is real, it is compounding, and it is moving toward a metric with a leader's name on it whether anyone can see it yet or not.

The Lever

Those questions do not have comfortable answers if the architecture is doing what most architectures do. That discomfort is not the problem. It is the beginning of the only diagnosis that can change anything.

Structure outperforms intention. The people inside the system will continue to do what it rewards regardless of what the values statement says or what the offsite concluded. The highest-leverage intervention is an honest audit of what the architecture is selecting for. Before the cost becomes visible enough to have a leader's name on it. Before the window closes.

The leaders who change this are not the ones who waited until the system forced them to see it. They are the ones who looked clearly, early, while the cost of looking was still lower than the cost of not looking. That is where performance recovery begins.

You Cannot Outperform a System Working Against You

Wed, 15 Apr 2026 12:00:15 GMT

High performers do not fail randomly. When they consistently hit a wall, it is not a capability problem. It is a system problem. And most organizations never make that distinction.

When High Performers Hit a Wall

They were exactly the kind of person organizations say they want.

They delivered under pressure. They navigated ambiguity without losing momentum. When priorities shifted, they adjusted without complaint and got back to work. Their track record was real, and they knew it. They were also exactly the kind of person organizations can afford to lose the least.

The priorities were clear at the start of the quarter. They built the plan around them and executed. Six weeks in, the priorities shifted. Not because the work was wrong, but because a decision made three levels up had invalidated the work without anyone saying so out loud. The expectations remained. The conditions that made them achievable did not. They adjusted and got back to work.

Then it happened again.

By the third time, they shifted from trying to solve the problem to just surviving. High performers do not do that. Or they did not used to. The work kept moving. The ground kept shifting. They were delivering, but nothing they delivered seemed to land anywhere stable. Hours of careful execution were quietly invalidated by decisions they had no visibility into and no ability to influence.

They were not failing. But they were starting to feel like they were. And they could not quite locate the moment when that feeling had started to feel normal. What they could not see from inside it was that the environment had failed them systematically.

What High Performance Requires

Sustained high performance depends on conditions beneath the surface: clarity, perceived control, cognitive bandwidth, trust, and recovery. When those conditions erode, performance follows, regardless of talent or effort. This article addresses what leaders can do to restore those conditions, but more importantly, what individuals need to understand and do when leaders will not.

The System Is Not Broken. It Is Working as Designed

Most dysfunctional environments were not designed to be dysfunctional.

They were built to solve a real problem at a specific moment. A structure that rewarded autonomy made sense when the organization needed to move fast and trust its people to own their domains. A culture that deferred to senior leadership made sense when decisive direction was what stabilized a company through uncertainty. Those systems worked. They got rewarded. They became the way things are done here.

What rarely gets examined is whether the problem those systems were built to solve still exists. Contexts change. Markets shift. Organizations grow into different challenges than the ones that shaped them. But systems that worked do not dismantle themselves, and the people who rose within them, who were rewarded by them, have little incentive to question them. The system persists not because anyone is defending dysfunction, but because the system continues to serve the people with the authority to change it.

Economists have a name for this dynamic: the principal-agent problem. When the people making decisions (principal) do not bear the consequences of those decisions, the decisions reliably optimize for the wrong things. It is not a character failure. It is a structural one, and it is predictable enough that this dynamic has been studied for decades.

For the person inside that environment (agent), this matters for one reason. The conditions working against their performance are not a reflection of their value, their capability, or their fit. They reflect a system optimizing for something other than their performance. That is a meaningful distinction, and it is where an honest assessment of the environment must begin.

Is Change Structural or Performative?

Leaders who want to change these environments have a specific kind of work ahead of them. Not culture initiatives. Not offsites or engagement surveys or renewed commitments to transparency. Those are not useless, but they do not address the structural problem. What restores performance conditions is deliberate and often uncomfortable: changing what gets rewarded, redistributing decision authority, and absorbing the political cost of removing protections from people whose behavior is degrading the system.

That is harder than it sounds in most organizations. It requires a leader who can see the gap between what the incentive structure is rewarding and what the organization says it values. It requires willingness to name that gap publicly and act on it even when doing so creates friction with peers or threatens relationships that have been useful. And it requires patience for change that does not produce visible results quickly, which runs against almost every pressure a senior leader operates under.

Some leaders are doing this work genuinely. The signs are specific. Decisions about structure and incentives change, not just language about culture. People who were previously protected from consequence start experiencing it. People who were previously absorbing costs without recognition start being seen. The changes are structural and uncomfortable, not smooth and well-received.

Others are managing the appearance of change. Listening sessions happen. Task forces are formed. The language shifts. The conditions do not.

The question worth asking honestly is which one you are watching.

What to Look For

Reading an environment honestly is harder than it sounds. Most people inside a dysfunctional system have spent considerable energy adapting to it, which means they have also spent energy explaining it to themselves in ways that make continued effort feel rational. That is not weakness. It is how capable people survive in conditions that are working against them.

But at some point, honest assessment becomes more important than continued adaptation. The indicators worth paying attention to are patterns, not events.

The same dysfunction recurs. It is not a bad quarter or a difficult transition. It is the third or fourth time the same dynamic has played out with the same structural causes and the same people protected from consequence.

The cognitive cost keeps rising. More attention is being consumed by navigating the environment than by doing the actual work. Clarity, perceived control, and cognitive bandwidth, the conditions that make execution possible, are not temporarily constrained. They are structurally unavailable.

Naming the problem produces a predictable response. When the dysfunction is raised with someone who has the authority to address it, the response is defensiveness, reframing, or performative concern followed by no action. The messenger becomes the problem. The pattern continues.

The workarounds have become the work. When the informal systems people have built to survive the dysfunction are more reliable than the formal ones, the organization has already told you something important about whether it intends to change.

If any of these patterns are present, the next question is not how to fix them. It is what to do with that recognition.

Before moving forward, sit with these:

How many of these patterns are you recognizing?
How long have they been present?
Have they gotten better, stayed the same, or gotten worse?

For many people, the honest answers to those questions arrive before they are ready to act on them.

What Staying Costs

The most serious cost is the one that takes longest to recognize. It is not always self-doubt. More often it is quieter and more corrosive. A capable person who can see the dysfunction clearly, who knows the system is the problem, who has not lost confidence in their ability, arrives at a different conclusion: I cannot do my job here.

That realization does not produce motivation to push harder. It produces disengagement, not from lack of caring but as a rational response to a system that has repeatedly demonstrated that effort does not connect to outcome. It produces cynicism, not pessimism, but the specific kind that develops when someone who once believed the work mattered stops believing the environment will let it matter. And over time it produces something more permanent: a settled sense that no matter what they do, the conditions will undermine it. The person stops trying to change the outcome and starts managing their exposure to the disappointment of it.

The person has not changed. The environment has closed off the conditions that made their performance possible. That distinction matters enormously, and it is one most organizations never make.

Which raises the question most organizations will not ask on your behalf: what do you do when that recognition arrives?

Deciding to Adapt or Exit

Before that question can be answered honestly, two things need to be named that make honest assessment harder than it should be.

The first is resilience. Organizations select for it, invoke it under pressure, and treat it as a performance measure. And it is a genuine skill, the ability to absorb difficulty and continue functioning. But resilience is not infinite, and it cannot operate indefinitely in conditions that are actively consuming it. When leaders point to resilience as the reason people should continue absorbing the cost of a system that will not change, they are not describing a performance standard. They are describing a way of avoiding one. The question is not how resilient you are. It is whether the environment is giving resilience anywhere to work.

The second is sunk cost. The more someone has invested in an environment, time, relationships, identity, career capital built inside that specific system, the harder it becomes to weigh the actual cost of staying against the cost of leaving. What has already been spent feels like a reason to continue. It is not. It is a reason the decision feels harder than it is. Recognizing that does not make the decision easier. It makes it clearer. And clarity is the only honest place a decision like this can start.

With those two things named, the question of which approach to take becomes less emotional and more practical. Adaptation makes sense when there is credible evidence that the conditions are improving, when genuine change is underway rather than being performative, and when the cost of staying has not yet started to outpace what the environment is giving back. Adaptation under those circumstances is a legitimate performance strategy, not a failure of resilience.

Exit becomes the rational choice when the conditions are structurally unavailable, and the pattern has repeated across enough moments where change was possible and did not happen. When the cost of staying keeps growing. When the environment has begun closing off not just current performance but who you are still capable of becoming.

Before deciding which approach is best, sit with these:

Has anything structurally changed across the last several quarters or key moments where change was possible, or has the pattern held?
What is adaptation currently costing you that you are not fully accounting for?
If the conditions do not change in the next six months, what will that cost you that you cannot get back?

Where to Start

If you lead one of these organizations, the most useful thing you can do after reading this is examine what your incentive structure is rewarding, and whether the people absorbing the cost of it are the ones you can least afford to lose.

If you are inside one, the most useful thing you can do is stop measuring the environment against what it promised and start measuring it against what it has consistently produced. The evidence is already telling you something. The question is whether you are willing to act on it before the cost becomes one you cannot recover from.

When More Control Makes Performance Worse

Mon, 16 Mar 2026 18:56:54 GMT

How the layers added to protect outcomes create rework, friction, and hidden execution drag.

The signals are easy to miss. Quarterly results are on track. Meetings run smoothly, and decisions appear resolved. But some decisions are revisited weeks later. Fewer hard questions are asked. Strong operators who once challenged assumptions stop doing so. Nothing looks broken. The numbers are acceptable. But sustaining them requires more effort.

This pattern shows up under accelerating change. Markets move faster than planning cycles. Competitive pressure compresses timelines. Investors expect results. Boards expect progress. Conditions are less predictable, yet accountability remains near-term and visible. Slowing down is rarely an option. So the system adapts.

What Accelerating Change Does to Performance Systems

Under accelerating change, organizations move to reduce unpredictability. When conditions are unstable but outcomes must remain predictable, layers of control accumulate. Additional metrics are introduced. Approval checkpoints are added. Status updates become more frequent. Initiatives stack on top of existing priorities.

None of this is irrational. It is a disciplined effort to maintain control over outcomes in unpredictable conditions. If performance cannot slip, more control feels responsible. The assumption is simple: tighter control produces better performance. Over time, attention shifts from improving performance to managing the appearance of control.

The Observable Consequences

When control layers accumulate, nothing fails immediately. Delivery can still look acceptable on paper. Deadlines are met. Dashboards remain green. The cost is not yet visible in the numbers.

As oversight increases, people stop saying what they really think. Hard questions are voiced less often. Assumptions receive less scrutiny. Discussion becomes shorter and more streamlined. The team appears aligned, but the hard conversations have moved elsewhere.

When dissent and friction are filtered out of the room, they do not disappear; they relocate. Decisions that felt resolved resurface when concerns are raised downstream. The system maintains pace, but teams keep reworking the same issues.

The change is also visible in strong operators. They continue to execute, but they stop stretching the work. They deliver what is expected but no longer extend beyond it. The cost is lost discretionary performance.

None of this presents as crisis. It can resemble efficiency. It can even feel like progress. The cost shows up in execution: more rework, later surprises, and more friction during delivery.

This is often the point at which leaders are told to slow down or simplify. When pace cannot slow, simplification becomes the obvious answer. The problem is that simplification requires subtraction.

Why Simplifying Is Hard

Simplifying requires removing something that is already visible: a metric, a meeting, a checkpoint, or an initiative that has already been committed to. In most executive contexts, visible activity signals control. Removing work carries risk. The short-term risk of subtraction is easier to see than the long-term cost of carrying too much.

As a result, systems tend to add oversight rather than remove work. Simplification is correct, but it is harder to execute than it sounds.

What leaders need is not a mandate to simplify, but a way to remove controls without creating unnecessary risk.

Controlled Subtraction

Controlled subtraction is the deliberate removal of a single control layer, under defined conditions, to test whether it is still producing the outcome it was intended to protect.

Instead of attempting to simplify the entire system, leaders remove a single control layer tied to a specific outcome. A reporting step, a checkpoint, a metric, or a meeting is paused for a defined period while the outcome it was intended to protect continues to be monitored.

The objective is information. The test determines whether the risk of removing a control is real or assumed. If performance deteriorates, the control can be restored. If performance holds, the organization has identified a control that is no longer necessary.

Over time, these small removals reveal which layers are protecting performance and which are simply maintaining the appearance of control.

Recalibration as a Leadership Discipline

Accelerating change will not slow down. Control layers will accumulate again. The discipline is knowing when to remove them.

Controls should not be assumed to be permanent. A control earns its place if the outcome it was designed to protect cannot be sustained without it. The method is straightforward: pause the control, monitor the outcome for four to six weeks, and let the data answer the question.

The natural cadence is the reporting cycle. Leaders are already asking whether the organization is performing. The additional question is whether the controls in place are still necessary to sustain that performance. For most organizations, that means at least quarterly, though the principle scales to whatever rhythm the organization already runs on.

In volatile environments, the real discipline is not adding more control. It is knowing what no longer deserves to stay.

The Capacity Tax of Problemless AI

Sun, 15 Feb 2026 22:24:05 GMT

Why AI Fails When Nothing Comes Off the Plate

A couple of weeks ago, I was asked in an interview how my work on performance under pressure relates to AI. My answer was simple: AI is often rolled out as a solution looking for a problem, and that is how it turns into a pressure amplifier, not a reliever. When nothing comes off the plate, AI becomes one more thing. And in overloaded systems, “one more thing” is usually what gets dropped. This is what I call Problemless AI.

Problemless AI is what happens when AI is implemented before an organization can clearly name the performance bottleneck it meant to relieve. In practice, this makes AI additive rather than enabling. It is introduced alongside existing workflows instead of replacing or simplifying them. Usage stays uneven, and leaders often interpret this as resistance, a performance problem.

But the problem is not motivation or willingness to learn. It is capacity. When workflows, expectations, and incentives remain unchanged, the system around the work never adjusts. AI does not fail because people struggle to learn it. It fails because the system around the work does not change.

When Strategy Isn’t Explicit, Pressure Rises

Many AI initiatives do have a strategy behind them. The problem is not the absence of strategy; it is that the strategy may not be made explicit at the level where the work happens. People are told that AI will improve productivity, accelerate impact, or prepare the organization for the future, but they are not shown what problem it is meant to solve in their role or what is expected to change because of it.

This matters because AI is not replacing a broken system in many organizations. It is being layered onto work that is already functioning, under pressure. Traditional change efforts often begin by naming a clear pain point and replacing an existing tool or process. The relief is visible. With AI, the benefit is often abstract and downstream, while the cost is immediate: learning time, experimentation, cognitive load, and risk.

When strategy remains unclear, individuals are left to interpret it on their own. They must decide how much effort to invest, where AI fits relative to existing priorities, and whether using it will be valued. That uncertainty creates pressure before any performance issue appears. Attention fragments. Engagement becomes cautious. Learning becomes compliance-oriented rather than generative. This is not a failure of mindset or openness to change. It is a predictable response to systems that introduce new demands without clearly redefining what changes in how the work is done.

This Is Not Unique to AI

If this pattern feels familiar, it should. Organizations have long relied on learning initiatives to signal progress when performance problems are difficult to diagnose or slow to resolve. Completion is easy to measure, so it becomes a proxy for progress. Leaders can report attendance, modules finished, and certifications earned.

When outcomes lag, organizations often respond by increasing activity rather than changing conditions. More training is added. Expectations are reinforced. New tools are layered onto existing workflows. The underlying structure of the work remains the same. This creates the appearance of action without changing the conditions that shape performance.

AI inherits this pattern and intensifies it. Because the technology is new and its potential is broad, organizations default to scale. Broad enablement replaces targeted intervention. Adoption metrics stand in for performance impact. At its core, the issue is this: the system is asking for change without changing itself.

What This Looks Like in Practice

In practice, this pattern emerges less as outright failure and more as growing inertia. A team is told to increase AI usage to 80 percent while still meeting the same delivery targets. Nothing is removed. Adoption is tracked weekly. Deadlines remain unchanged.

Over time, usage becomes uneven. A small group experiments actively, while most people use the tools sporadically or only when prompted. The technology exists, but it never fully integrates into the flow of work.

Leaders respond by reinforcing adoption. Participation targets are set. Expectations are reiterated in meetings and communications. Activity becomes another proxy for progress.

At the role level, the experience is different. Employees are still accountable for the same outcomes, under the same timelines, with the same evaluation criteria. AI is framed as optional but encouraged, useful but not essential. Over time, AI use becomes performative rather than transformative . Something to demonstrate awareness of, not something the work depends on.

From the outside, this can look like resistance or lack of follow-through. From inside the system, it feels like another initiative layered onto already constrained roles. Nothing is explicitly broken, but nothing is meaningfully easier either. Work continues, but it requires more effort than it should. Capacity is quietly eroding.

Why “Problemless AI” Creates a Capacity Tax

Capacity is not skill or motivation. It is the finite ability of a system to absorb demand and still execute reliably. It includes attention, cognitive bandwidth, coordination, decision energy, and the flexibility people have to adapt when conditions change. When capacity is intact, performance holds even under pressure. When it is eroded, execution becomes fragile long before anyone notices a clear failure.

Problemless AI quietly taxes capacity. Learning a new tool requires attention. Deciding when and how to use it adds cognitive load. Switching between old workflows and new possibilities increases coordination costs. Unclear expectations force people to monitor themselves, their peers, and their leaders for signals about what really matters. Taken together, these demands steadily reduce the system’s ability to perform. Because the work still gets done, capacity loss is often misattributed.

AI does not create this dynamic on its own. It exposes it. When new demands are added without subtracting existing ones, capacity is consumed rather than created. AI rarely enters a system at full capacity. More often, it is introduced in response to existing performance strain: missed deadlines, slower execution, rising complexity, or pressure to do more with less. In that context, AI becomes one more attempt to restore capacity without changing the conditions that depleted it in the first place. When added to an already constrained system, the tool compounds the problem it was meant to solve.

The Misdiagnosis Loop

When capacity erodes, the early signs are subtle. Decisions take longer. Execution becomes less consistent. Coordination costs rise. Because the work still gets done, these signals are easy to overlook. Leaders interpret them as a performance problem rather than structural strain.

When performance lags, leaders try to explain why. In most organizations, those explanations default to the most visible causes: skill gaps, inconsistent effort, or lack of accountability. AI adoption becomes part of that story. Uneven usage is interpreted as resistance.

The response is predictable. More training is added. Usage is tracked more closely. Expectations are clarified through targets and reporting. Together, these actions increase demand on a system already operating under reduced capacity.

Over time, the organization becomes trapped in a self-reinforcing cycle. Capacity problems are treated as motivation or capability problems. Each corrective action adds load without changing conditions. What looks like a failure to adopt AI is, in fact, a failure to recognize how performance degrades under cumulative demand.

Treat AI Like a Performance Intervention

The pattern persists because AI is rarely treated as an intervention in a performance system. It is more commonly treated as a capability to be learned, a tool to be adopted, or a technology to be scaled. Those approaches focus attention on exposure and usage rather than on what limits execution.

Performance interventions start from a different place. They identify a specific bottleneck in how work is done. They require something to change in the system, not just something new to be added to it. Treating AI as a performance intervention shifts the question from Are people using it? to What pressure is this meant to relieve, and how will we know if it does? AI does not automatically remove work. Leaders have to deliberately remove something from the system for capacity to be restored.

If AI is meant to reduce effort, something must come off the plate. If it is meant to improve speed or quality, workflows, expectations, or incentives must change. Without those adjustments, the tool may still be impressive, but it will continue to tax capacity rather than restore it.

A Simple Test

Before rolling out an AI initiative, ask three questions:

What specific performance bottleneck is this intended to relieve?
What demand, decision, or coordination cost will be reduced as a result?
What will stop being required once this tool is in place?

If those questions cannot be answered clearly, the initiative is unlikely to create capacity. Instead, it will almost certainly add pressure.

AI does not fail because people are resistant or incapable. It fails when it is asked to solve problems that have not been clearly defined in systems already operating at their limits. When aligned to a clearly defined performance constraint, AI can be a powerful performance lever. When introduced without that alignment, it becomes one more thing. In overloaded systems, adding one more thing is often the most expensive mistake a leader can make.

Stop Spending Money to Make Performance Worse

Wed, 07 Jan 2026 23:43:32 GMT

How Organizations Fund Their Own Performance Decline

Most organizations respond to performance declines with fixes that sound responsible: more metrics, tighter oversight, more training, stronger accountability. The intent is rational; however, the problem is that these moves often make performance worse.

Not because leaders are careless, and not because employees suddenly forgot how to do their jobs. The problem is misdiagnosis. Under sustained pressure, organizations often treat capacity failures as competence problems, then invest in interventions that add pressure and further reduce capacity. The result is a widening performance gap: profit, productivity, engagement, and retention that the organization has already paid for become harder to access.

A Familiar Pattern

In an organization I am familiar with, performance was strong for years. Then market conditions shifted. Pressure increased. Leaders tried to reassure employees that layoffs would not happen, but layoffs eventually occurred and trust eroded. At the moment when clarity and transparency were most needed, priorities competed, decisions stalled, and the strategy kept shifting.

People still wanted to do good work, but execution became less reliable anyway. Coordination weakened. Follow-through slipped. The organization worked harder and got less back.

This pattern is common: performance declines without a sudden drop in talent. The conditions change, pressure rises, and execution becomes harder to sustain.

The Performance Gap

The performance gap is the space between knowing what to do and being able to do it reliably when pressure increases.

In this context, pressure is not “stress” in the casual sense. It is higher stakes and tighter constraints on time, control, or information. In practice, this shows up as compressed timelines, shifting priorities, heightened visibility, and unclear decision rights. Under those conditions, capable teams can start to look inconsistent, not because competence disappears, but because access to competence becomes constrained.

Why Leaders Misread It

When performance erodes, leaders tend to default to familiar explanations:

People do not have the right skills.
People are not motivated.
People do not understand the strategy.
People are not trying hard enough.
People need more rigorous performance management.

These explanations feel intuitive because they focus on what is visible and measurable. They also align with how most organizations are designed to solve problems: training, incentives, oversight, and consequences. So, the response is predictable: add structure, add monitoring, add reporting, add performance management.

The trouble is that many struggling performers were high performers under more stable conditions. From the outside, it looks like a discipline problem. From the inside, it often feels like overload.

What Pressure Does to Execution

The mechanism is straight forward. As pressure increases, people pay more attention to managing the environment and themselves. Worry increases. Self-monitoring increases. Outcome fixation increases. Teams start tracking threats, anticipating consequences, and managing impressions. That costs bandwidth. Less bandwidth remains for judgment, planning, prioritization, and coordination.

Attention can also narrow. Under pressure, people focus on what is urgent, visible, and risky. That can help with simple tasks. However, it tends to hurt performance when work requires flexibility, cross-functional coordination, and good judgment.

When these effects persist, execution gets noisier: more rework, more missed handoffs, more delays, more conflict. People are still competent. The system is making competence harder to access consistently.

The Performance Iceberg

Performance problems show up first as visible symptoms: missed deadlines, weaker execution, conflict, disengagement, slow decisions, inconsistent follow-through. Those symptoms matter, but they are often downstream.

Think of performance as an iceberg. What leaders see above the waterline is shaped by conditions below it. Under sustained pressure, execution becomes increasingly dependent on conditions that are rarely measured directly, such as:

Clarity: priorities, roles, success criteria
Perceived control: decision rights, autonomy, ability to act without excessive friction
Trust: willingness to raise risks early and tell the truth fast
Cognitive bandwidth: attention available for judgment and planning
Emotional regulation: steadiness under scrutiny, uncertainty, and conflict
Recovery: fatigue, pace sustainability, time to reset

When these conditions erode, performance symptoms rise. If leaders intervene only at the symptom level, the underlying conditions remain unchanged.

How Organizations End Up Paying To Make It Worse

Here is the loop that makes this expensive.

Pressure increases (uncertainty, change, visibility, constraints).
Capacity declines (attention, coordination, decision quality).
Performance slips (execution inconsistency, rework, slower cycles).
Leaders add surface-level controls (new metrics, more reporting, additional training, tighter performance management).
Those controls consume bandwidth and increase scrutiny.
Capacity declines further and performance degrades again.

A concrete example: after a downturn, leadership introduces new metrics, adds training, tightens performance management, and increases status reviews to “drive accountability.” The intent is understandable. The effect is often predictable. Meetings multiply. Reporting expands. Decision latency increases. Evaluation pressure increases. Focus fragments. Execution declines further. Leaders interpret that decline as evidence that even more oversight is needed.

This is why misdiagnosis matters. It turns a solvable performance issue into a persistent business cost, and it creates the illusion that the organization is acting while performance erodes in slow motion.

The Diagnostic Shift, Before you Spend

You do not need a new initiative to start seeing this differently. You need a better diagnostic question:

Is this a competence problem, or a capacity problem created by pressure?

A few questions can help you locate the source before you invest in fixes:

What changed recently in clarity (priorities, roles, strategy coherence)?
Where has control decreased (decision rights, autonomy, dependency chains)?
What has increased evaluation pressure (visibility, scrutiny, consequences)?
How much time is being consumed by coordination overhead (status meetings, reporting, approvals, rework)?
What are the signals that recovery is failing (fatigue, irritability, rising cynicism, preventable errors)?

These questions do not solve performance problems by themselves. They prevent you from funding interventions that quietly intensify the conditions causing the problem.

Closing

Yes, the performance gap should be closed, just not in ways organizations traditionally try to close it.

If performance is slipping and the usual fixes are not working, consider the possibility that you are not dealing with a competence problem at all. You may be dealing with a capacity problem created by sustained pressure. In that case, adding pressure will not be the cure. The fastest way to lose money is to keep investing in fixes that widen the gap.

If this pattern is familiar, I am developing a diagnostic assessment to help leaders identify the pressure conditions driving the gap before investing in performance fixes.