top of page

FIELD NOTE | 

September 21, 2026

The Organization You Have Is the One Your Incentives Are Building

When the same unwanted behavior appears across many capable people, I become less interested in correcting the people and more interested in the conditions that keep making the behavior make sense.

When the same unwanted behavior appears across many capable people, I become less interested in correcting the people and more interested in the conditions.

What gets rewarded?

What gets attention?

What creates risk?

What can be ignored without consequence?

What makes someone's job easier?

What does someone have to do to succeed here, regardless of what we've told them matters?

Behavior is information.

That doesn't mean people have no agency or that every bad decision can be blamed on the system. Sometimes someone exercises poor judgment. Sometimes a person isn't capable of the work. Sometimes people know exactly what is expected and choose differently.

But when the same pattern keeps appearing across different people, I become suspicious of explanations that require all of them to independently possess the same character flaw.

At some point, I want to look at what they have in common.

Usually, that's the system they're working inside.

Incentives are larger than compensation

We tend to talk about incentives as though they mean money.

Money matters. But organizations contain much larger incentive systems.

Access is an incentive. Praise is an incentive. Promotion is an incentive. Proximity to leadership is an incentive. Relief from scrutiny is an incentive. So is being trusted with interesting work.

Attention may be one of the strongest.

People notice which problems executives personally engage with. They notice what gets discussed in company meetings and what disappears into a backlog. They notice which failures produce an emergency and which ones someone is expected to quietly absorb.

Resources follow attention.

So does status.

An organization can say collaboration matters while consistently rewarding local wins. It can say quality matters while celebrating speed and quietly asking someone else to clean up the defects. It can say long-term thinking matters while requiring every investment to prove itself against this quarter's number.

Eventually people learn what counts.

And they are often learning from much better evidence than the values statement.

The system is teaching all day long

I believe values are byproducts of the processes we inhabit.

If I say I value open collaboration but there is no structure that encourages, rewards, or sometimes requires it, then collaboration depends on individual effort.

An open-door policy isn't a collaboration system.

Collaboration requires actual pathways between functions and people: access to information, shared decisions, time to participate, incentives that don't punish someone for helping another team, and some expectation that crossing a functional boundary is part of the work rather than a distraction from it.

Values become operational when they affect staffing, decision rights, metrics, budgets, meeting structures, promotion, and what happens after someone says no.

Otherwise they remain aspirations.

The system is teaching people how to behave all day long.

And unlike a values presentation, it has consequences.

People respond to the system they are actually in

Imagine a sales organization that says it values profitable, durable customer relationships.

Salespeople are measured on bookings.

A highly customized deal counts toward quota. The implementation work it creates does not count against it. The support burden doesn't appear in the salesperson's metrics. Neither does the engineering work required to maintain the exception.

What should we expect the salesperson to do?

If the organization rewards the booking while distributing its costs somewhere else, more exceptions aren't surprising. They're rational.

The same thing happens outside sales.

Tell a manager that quality matters, then evaluate them on whether they hit the date.

Tell a team to collaborate, then give every function goals it can achieve more easily by protecting its own resources.

Tell people to take thoughtful risks, then make the person associated with a failed experiment spend six months explaining it.

Tell managers to develop their people, then promote the ones whose individual output remains highest.

The organization doesn't need to explicitly tell people which instruction wins.

They'll figure it out.

This doesn't make people simple. Incentives don't explain every behavior, and people don't respond to identical conditions identically.

But systems make some behaviors easier to sustain and others more expensive.

Over enough repetitions, that matters.

Culture emerges from repeated design

This is why I've become skeptical of culture as something separable from operations.

Culture isn't only what people believe.

It's also what becomes normal because the surrounding system keeps reproducing it.

A behavior happens. It works. Nothing bad happens to the person who did it. Maybe they're rewarded. Someone else notices. The behavior becomes a reasonable strategy. Eventually enough people use the strategy that we describe it as part of the culture.

Then we launch an initiative to change the culture.

But if the underlying conditions remain the same, we're asking people to behave against the evidence available to them.

I once thought of values as the operating system and innovation as the code. I still like part of that metaphor, but I think I would put it differently now.

What an organization repeatedly produces tells me more about its operational values than what it says it values.

Not because the stated values are necessarily dishonest.

The organization may genuinely want collaboration, quality, stewardship, experimentation, candor, or customer care.

But wanting something and designing conditions that produce it are different acts.

A value that has no mechanism for expression is mostly aspiration.

Look for the behavior that makes sense

When a pattern frustrates me, I try to ask a different question.

Not:

Why do these people keep doing this?

But:

What would make this behavior rational from where they are standing?

Maybe the answer really is poor training or judgment.

Maybe expectations are unclear.

Maybe someone needs better feedback.

But sometimes the person everyone is frustrated with has understood the system perfectly.

They're maximizing the metric we attached to their work.

They're avoiding the kind of failure we've taught them is dangerous.

They're keeping information because information creates leverage.

They're escalating because making the decision themselves creates more personal risk than waiting.

They're protecting their team's capacity because helping another team will hurt their own performance.

They're doing exactly what the architecture makes sensible.

That doesn't mean the behavior has to be accepted.

It means changing the behavior may require changing what makes it rational.

If an organization keeps producing a behavior it claims not to want, I want to understand what the system is teaching before I conclude that the people have failed the culture.

bottom of page