Identify perverse incentives in a proposed policy
Expose unintended consequences, metric gaming, and perverse incentives hidden inside proposed rules. Perfect for managers drafting new KPIs or policies.
You getPrimary Vulnerabilities, unintended Casualties and countermeasures
Prompt
Act as a systems thinker and behavioral economist. Analyze the policy draft pasted below to uncover hidden perverse incentives, metric gaming, and unintended behavioral side effects.
- Map out 3 distinct ways rational actors will exploit or game the rules to meet targets while hurting overall value.
- Identify who bears the hidden operational cost or burden when this policy is enforced.
- Provide concrete revisions or counter-metrics to neutralize these loopholes without adding bureaucracy.
Output format:
1. Primary Vulnerabilities (how people will game this)
2. Unintended Casualties (teams or metrics harmed)
3. Countermeasures (revised rules or pairing metrics)
My policy draft is below:Example output
Paste your proposed policy or KPI rules after the prompt in ChatGPT, Claude, or Gemini. As a follow-up, ask the model to draft an edge-case test scenario with specific worker personas.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Detect scope creep hidden in quick requests
Flag hidden architectural, operational, and delivery risks concealed inside seemingly harmless, small project additions.
Expose unstated assumptions in a business plan
Stress-test projects and commercial plans by uncovering implicit dependencies, fragile beliefs, and hidden points of failure.
Stress test an optimistic project timeline
Expose hidden friction, coordination overhead, and missing buffers in your project schedule. Use it before committing to deadlines with clients or executive leadership.
Distinguish enduring workplace tools from trend hype
Filter enterprise software and process fads through enduring utility principles. Use it before approving new software licenses or department overhauls.
Find the root cause of an operational issue
Drill down through recurring symptoms to identify systemic causes and design prevention fixes rather than temporary patches.
Stress test a strong gut feeling
Pressure-test an instinctive business decision against hidden assumptions and worst-case realities. Use it before signing a contract or greenlighting spend.