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

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.