Protocol
Look for incentives that reward the failure mode
Repeated behavior can be locally rewarded by the system.
Before you use it
- Use when
- When a recurring failure persists despite training and reminders.
Keep this limit in mind
- Leverage-point and information-value heuristics are prompts, not guaranteed effect sizes. Test interventions, monitor side effects and stop when evidence changes.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
List what the actor gains or avoids by the failing behavior: time, metric performance, risk transfer, status or workload. Remove the perverse incentive or add a countervailing control.
Steps
- Name the recurring failure.
- Identify local benefits of that behavior.
- Identify who bears the delayed cost.
- Redesign the incentive or feedback path.
An example
Teams skip early documentation because delivery metrics count releases but not future support effort; reminders alone do not change the payoff.
Check your result
The corrective action changes the local payoff or information, not only the message.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingLook for incentives that reward the failure mode
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Use before this ideaCheck whether the goal of the system is causing the symptom
Evidence and sources
Meadows' leverage-points framework widens intervention search from parameters and buffers toward information flows, rules, goals and paradigms while explicitly cautioning that the list is not a recipe.
The proposed ordering is a systems-thinking heuristic, not a universal causal effect-size ranking.
Leverage Points: Places to Intervene in a System · Places to intervene and concluding caveats
All sources (1)
Edition and review
Version 0.1.0
No review details are supplied for this edition.