# Check whether the goal of the system is causing the symptom

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Check whether the goal of the system is causing the symptom

ID: MHC-D-RESEARCH-9161 · Version: 0.1.0 · Kind: question
Source: https://vedokrok.com/knowledge/check-whether-the-goal-of-the-system-is-causing-the-symptom

People often optimize the objective they are given.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- When every local fix is rational yet the overall outcome remains bad.

### Avoid when

- Leverage-point and information-value heuristics are prompts, not guaranteed effect sizes. Test interventions, monitor side effects and stop when evidence changes.

### Explanation

Identify the effective goal revealed by rewards, dashboards and escalation behavior, then compare it with the stated purpose. Change measurement or authority if the two conflict.

### Question

What behavior does the current metric reward? · What trade-offs does it ignore? · What would a person do to win the metric while harming the purpose? · Which goal or guardrail needs redesign?

### Example

A support target rewards ticket closure speed, so difficult tickets are bounced instead of solved; the operating goal differs from customer resolution.

### Check

The analysis explains how the effective goal can generate the symptom.

### Limits

- Leverage-point and information-value heuristics are prompts, not guaranteed effect sizes. Test interventions, monitor side effects and stop when evidence changes.

### Evidence and sources

- contextualizes: 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. — RS-EA64347094A93DB4. The proposed ordering is a systems-thinking heuristic, not a universal causal effect-size ranking. (Places to intervene and concluding caveats)
- RS-EA64347094A93DB4: Leverage Points: Places to Intervene in a System — https://donellameadows.org/archives/leverage-points-places-to-intervene-in-a-system/

No review details supplied.
Related (use_before): https://vedokrok.com/knowledge/look-for-incentives-that-reward-the-failure-mode
