Name the outcome
- Use a 90-day horizon.
- Choose a user behaviour or business state the product can influence.
- Diagnose why it is not happening now.
Shape · Core skill lab
Turn a list of plausible initiatives into one coherent product bet with a mechanism, sacrifice, and evidence gate.
Your work saves in this browser.
Field tools
Copy these into your interview, agent, review, or working document. They are specific to this repetition.
Use this sequence to keep ambition, diagnosis, and action connected.
OUTCOME — changed state in 90 days DIAGNOSIS — mechanism preventing it now + evidence ARENA — segment × workflow × trigger GUIDING CHOICE — how we will create advantage SACRIFICE — what we will not pursue COHERENT ACTIONS — 3–5 reinforcing moves EVIDENCE GATES — commit / adapt / stop + review date
If every option survives, the strategy has not made a choice.
Could a reasonable leader choose a different option? Does the choice deny resources to something attractive? Do the actions reinforce one mechanism? Can a team reject work using this strategy? Is the advantage more specific than “better UX” or “AI”? Can evidence within 90 days overturn the call?
Calibrate judgment
An agency handoff product is under pressure to broaden acquisition and segments.
For 90 days, concentrate on trusted, source-linked agency handoffs. Pause freelancer onboarding and new acquisition integrations. Reinforce the choice with cited extraction quality, source-type UX, five agency partners, and trust instrumentation. Stop if repeat handoff use remains below 20% after the trust gate passes.
Why it works: The diagnosis, arena, advantage, reinforcing actions, sacrifice, and stop condition form one falsifiable system.
Our strategy is to grow engagement by improving onboarding, adding AI, launching integrations, expanding internationally, and investing in enterprise features.
Why it fails: There is no diagnosis, mechanism, priority, sacrifice, or evidence that can reject work.
Review → revise → repeat
Check only standards your current artifact actually meets. Then record one consequential revision before exporting it.