Behavior is information

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?

Incentives are larger than compensation

Money matters, but incentives also include access, praise, promotion, proximity to leadership, relief from scrutiny, and which problems receive resources.

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.

People notice which problems executives personally engage with. Resources follow attention. So does status.

Over time, teams learn which forms of work are considered strategic and which must be justified repeatedly just to exist.

Culture emerges from repeated design

This is why culture work that lives only in values statements has limited reach. Values become operational when they affect staffing, decision rights, metrics, budgets, meeting structures, and what happens after someone says no.

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

If the organization keeps producing a behavior it claims not to want, inspect what the architecture is rewarding before concluding the people have failed the culture.

I once wrote: values are byproducts of the processes we inhabit. If I say I value open collaboration but there is no framework that encourages, rewards, and reinforces it, then it is lip service.

Open collaboration is not the byproduct of an open-door policy. It is the result of established pathways that support movement between functions and people—processes that reward, and sometimes require, collaboration.

I think of values as the operating system and innovation as the code. What an organization repeatedly produces tells me more about its values than the words on the wall.

People respond to the system they are actually in

If a sales team is rewarded for bookings while implementation absorbs the complexity of every exception, the organization should expect more exceptions. If managers are rewarded for hitting a date but not for the cleanup required afterward, the cleanup becomes somebody else’s problem. If collaboration is praised but individual metrics punish the time it requires, collaboration will depend on unusually generous people.

None of this makes people simple. Incentives do not explain every behavior. They do, however, make some behaviors easier to repeat and others more expensive.

Look for the behavior that makes sense

When a pattern frustrates me, I try to ask what would make this behavior rational from the other person’s position. That question is usually more useful than deciding that an entire team lacks accountability. Sometimes the answer is training or judgment. Often the system is paying for exactly what it says it does not want.