Map the incentive structure before blaming individuals…
When encountering a frustrating recurring behavior in your organization, map the actual incentive structure (what gets rewarded, punished, and measured) before attributing the behavior to individual character, because most problematic behaviors are rational responses to system design.
Why This Is a Rule
The fundamental attribution error (Ross, 1977) describes our tendency to attribute others' behavior to their character ("they're lazy") while attributing our own behavior to circumstances ("I was overloaded"). In organizations, this error is systematic: when someone behaves in a frustrating way, the instinct is to blame their character rather than examine the system that makes their behavior rational.
"Engineers don't write documentation" → character attribution (they're lazy or careless). But what does the system reward? Shipping features (promoted), writing documentation (not measured, not rewarded). The "problematic behavior" is a rational response to the incentive structure. Replacing the person doesn't fix the behavior because the next person faces the same incentives.
Incentive mapping asks three questions before character attribution: What gets rewarded (promoted, celebrated, compensated)? What gets punished (criticized, measured, flagged)? What gets measured (tracked, reported, reviewed)? The behavior you're frustrated by is almost always rational given these three answers.
When This Fires
- When a behavior frustrates you across multiple people in the same organization
- When someone "should know better" but keeps doing the same thing
- Before having a difficult conversation about someone's performance
- Any time individual blame is the first explanation for organizational behavior
Common Failure Mode
Mapping the stated incentives instead of the actual incentives. The organization says it values documentation (stated). But promotions go to people who ship features, not people who write docs (actual). The actual incentive structure — what's rewarded in practice, not what's written in the values document — is what drives behavior.
The Protocol
When frustrated by recurring organizational behavior: (1) Pause the character attribution. (2) Map the actual incentives: What gets rewarded? (promotions, bonuses, praise) What gets punished? (criticism, write-ups, lost opportunities) What gets measured? (metrics, dashboards, reports). (3) Ask: given these incentives, is the frustrating behavior rational? (4) If yes → the fix is system redesign (change the incentives), not individual correction. (5) If no → then (and only then) consider individual factors.