Incentive-Outcome Tracing¶

Why It Matters¶

Organizations constantly produce undesired outcomes while wondering why: products ship with known bugs, sales misrepresent capabilities, teams hoard information, innovation stalls. The default attribution is to individual failures—people aren't working hard enough, aren't competent enough, or don't care enough. Incentive-outcome tracing reveals that individuals are often optimally responding to the actual incentive structure, which differs from the stated goals. The problem isn't the people; it's that the organization is successfully incentivizing the wrong behaviors. Until you make the actual incentives visible, you'll keep replacing individuals while the system produces the same outcomes.

The Key Move¶

Start with an outcome you want to understand. Ask: "What specific behaviors by specific people produced this outcome?" Then for each behavior: "What was this person rewarded or penalized for? What would happen to them if they did the opposite?" Include formal incentives (compensation, promotion criteria, performance metrics) and informal ones (peer approval, manager attention, cultural norms). If the behavior is rational given the incentives, you've found your explanation. Changing the outcome requires changing the incentives, not exhorting people to try harder.

Classic Application¶

Wells Fargo's fake accounts scandal (2016). Outcome: millions of unauthorized customer accounts created by employees. Behavior: frontline workers created accounts without customer knowledge or consent. Tracing to incentives: employees were measured and compensated based on number of new accounts opened, managers were measured on their teams' account metrics, and there was minimal verification of account validity. Employees who missed quotas faced termination; those who hit quotas got bonuses and recognition. The "unethical behavior" was a rational response to the actual incentive structure. The organization was successfully incentivizing exactly the behavior it publicly condemned.

Surprising Application¶

Documentation quality in software projects. Outcome: documentation is perpetually outdated and incomplete. Behavior: engineers don't maintain documentation when code changes. Tracing to incentives: engineers are evaluated on features shipped, bugs fixed, and project milestones hit. Documentation updates don't count toward any measured output. Code review checks for functionality, not documentation. Outdated docs have no immediate consequence for the engineer; delaying a feature to update docs has immediate negative consequence. The organization says it values documentation but incentivizes ignoring it. Demanding "better discipline" fails; measuring documentation coverage in performance reviews and code review would align incentives with stated values.

Failure Modes¶

Assuming all behavior is incentive-driven—some actions reflect values, mistakes, or lack of information independent of incentives. Over-simplifying to monetary incentives—social incentives (respect, belonging, autonomy) are often more powerful. Treating incentive identification as excuse-making—"it's the incentives' fault" doesn't eliminate individual responsibility. Creating complex incentive schemes that game-theory themselves into perverse outcomes. Ignoring that people often misunderstand what they're actually incentivized to do—stated goals don't always reveal actual rewards.

Go Deeper¶

Kerr, "On the Folly of Rewarding A, While Hoping for B," Academy of Management Executive 9(1), 1995; Pfeffer & Sutton, "Evidence-Based Management," Harvard Business Review 84(1), 2006.