Useful object

Wrong Fix Detector

Use this when the next move feels active but may be aimed at the wrong layer.

The wrong fix usually has three signs: it attacks the visible symptom, avoids the owner-level decision, and cannot name the proof that would show the business changed.

Detector
A fix is not right because it is active.
Tempting fix

Hire, tool, campaign, process.

Assumption

What must be true?

Avoided call

What decision remains open?

Proof

What would change?

Useful objectA fix is not right because it is active.
Short answerWrong Fix Detector

The wrong fix usually has three signs: it attacks the visible symptom, avoids the owner-level decision, and cannot name the proof that would show the business changed.

01

Name the tempting fix

Write the move you are about to buy or assign.

02

Name the problem it assumes

Ask what problem must be true for that fix to make sense.

03

Name the avoided decision

Find the owner-level decision that the fix lets you postpone.

04

Name proof before spend

Decide what must change in customer, cash, team, or owner load before scaling the fix.

Use this four-part check.

Tempting fix

Hire, tool, campaign, process.

Assumption

What must be true?

Avoided call

What decision remains open?

Proof

What would change?

Common questions.

How do I know if I am fixing the wrong thing?

If the fix cannot name the business problem, the owner decision, and the proof of change, it may be aimed at the wrong layer.

Can a useful fix still be wrong?

Yes. A good tool, hire, or consultant can still be wrong for the current constraint.

What should I do before spending?

Name the assumption and run the smallest proof check that could disprove it.

Work with Stan

When the business needs the next move named clearly.

Use monthly coaching when the same business decision keeps returning and the owner needs pressure, rhythm, and proof. Use the smaller session route only when one focused conversation is the right size.

Work with StanRequest scope