← All tools

Proxy Hunt

Before a metric becomes a target, ask how pushing it could damage the outcome you actually want. Keep the intended story, failure theories, reported readings and causal limits visibly separate.

Select a failure theory to inspect its scoped receipt.

Start typing β€” or load an example.

Export
Full hunt Β· all theories Selected theory Β· scoped receipt
Authored theories and reported patterns remain separate Β· full exports omit the live selection Β· the URL carries the hunt and selected receipt

Why hunt the proxy?

Operating measures are useful because they move sooner than the outcomes we care about. That same convenience makes them dangerous targets: a team can improve the number by changing behaviour in ways that do not improve the goal β€” or that quietly damage an outcome the product needs to protect.

Proxy Hunt makes the challenge inspectable. The intended route and each failure route contain actions, mechanisms and outcomes only. The proxy and any reported readings sit outside those routes, so a visual connection cannot smuggle in a causal claim. A co-moving pattern can justify investigation; it cannot establish why the outcomes moved.

The result is a guardrail decision, not an approval stamp. An unfinished hunt stays visibly unfinished. A speculative concern stays speculative. A reasoned mechanism still says what evidence would weaken it. Use Gauge to elicit a room’s judgement, Fermi to test a conditional calculation, and Paths when new knowledge changes what work should happen.