Diagnose the System Before You Blame

[!quote] Field Note When behavior keeps failing, inspect the system that rewards, permits, or overloads it before blaming the person.

[!summary] The Reader Promise Use a four-part check to separate harmful intent from bad rules, weak capacity, and hidden pressure.

The Field Note

[!example] Diagnose Before You Respond Before choosing punishment, training, or redesign, inspect intent, the rule, the incentive, and the person’s capacity to comply.

Large companies can publish responsible-business policies without carrying them into purchasing decisions. A rule can be broken for personal gain, but also under pressure, from helpful intent, or because the rule itself is defective. An inclusion policy can exist while a school lacks the resources and conditions to make inclusion work.

Repeated behavior is information about both the person and the system.

Before responding, use a four-part check:

1. Intent: What evidence shows deliberate harm, neglect, or a good-faith mistake?
2. Rule: Is the expectation clear, useful, and possible to follow?
3. Incentive: What does the operating system reward or pressure people to do?
4. Capacity: Do people have the time, skill, tools, and support the expectation requires?

The check does not erase accountability. Evidence of deliberate harm still requires a direct response. The point is to avoid treating punishment or retraining as a complete fix when the same conditions will reproduce the failure.

Diagnose first, then choose the response that fits the cause: accountability, clarification, redesign, support, or a combination.

Mental Model Lens

[!tip] Thinking Tool: Hanlon’s Razor Mental model: Hanlon’s Razor
Useful idea: Do not assign harmful intent before checking neglect, unclear expectations, weak capacity, or bad incentives.
Short quote: “Never attribute to malice what neglect can explain.”
Use today: Ask what condition made the behavior likely before deciding how to correct it.

[!note] Evidence Limit System conditions do not explain every harmful act or remove individual accountability.

Use It Today

[!question] For Students When a project fails, ask whether the cause was missing skill, missing support, a poor rule, or a deliberate choice before recommending a fix.

[!question] For Managers And Founders Take one repeated behavior problem through the intent-rule-incentive-capacity check before adding punishment or another training session.

[!question] For Educators And Advisors Test whether the learning environment can support the behavior you require, then separate an access problem from an accountability problem.

Useful Copy

Signal Text

[!abstract] Social Copy When behavior keeps failing, inspect the system before blaming the person. Check intent, the rule, the incentive, and capacity—then match the response to the cause.

Vantage Circle’s Lens

[!sponsor] Sponsor Field Note Recognition should include the people who improve the system, not only those who work around it. Notice the teammate who clarifies a rule, surfaces a bad incentive, or builds the support others need to meet the standard.

Explore the AIRe Framework (created by Vantage Circle) to be sure your employees feel recognized and rewarded for their valuable efforts.

Sources

• OECD — Turn Responsible-Business Commitments Into Action
• Harvard Business Review — How the Best Leaders Respond to Rule Breaking
• U.S. Government Accountability Office — Special Education
• MIT News — How MIT Students Are Helping to Prevent Cyberattacks
• Farnam Street — Hanlon’s Razor