How to tell a product strategy from a long wish list

“Launch an AI assistant, redesign the account area, enter enterprise and improve retention.” This can fill a year without explaining how the company plans to win. There is activity, but no visible choice.

Strategy is needed when there are more promising directions than the team can properly test and deliver. Its value shows up in disputed decisions: which request to accept, which contract to decline, where to spend the next month and what evidence would change the choice.

State what is limiting the outcome

Imagine a document-approval service. Paying clients stay, but new workspaces rarely finish their first workflow. The team has three ideas: attract more sign-ups, add integrations or shorten initial setup.

Start with a diagnosis. Suitable customers may struggle to transfer an existing approval route. The website may attract companies with different requirements. A manager may have approved the purchase without assigning a launch owner. These explanations require different strategies despite the same symptom: few active clients.

A diagnosis should rest on observations and acknowledge uncertainty. “We think route migration blocks launch; these requests and scenarios suggest it, but it is not yet tested on new clients.” This is more useful than confidently saying “we need better onboarding”.

Compare moves at different scales

Next Move Theory distinguishes local improvements from changes to the original choice. You can improve the existing product for chosen customers, or reconsider the segment, job or business model. Those decisions carry different uncertainty and cost.

In this example, a local move is a ready-made route template. A broader move is targeting companies that need no custom setup. Paid implementation is another possible direction. Comparing only three interface variants rules those possibilities out before the discussion begins.

For each move, record the expected result, cost, time to first evidence and key assumption. A single ranking with decimal scores is not mandatory. When the cost of being wrong differs greatly, a table of ranges and unknowns is more useful than a falsely precise number.

The chosen direction needs boundaries

Suppose the team chooses ready-to-use setup for small distributed chains. The buyer is an operations lead who needs a standard approval route across locations. The first promise is one working route without custom development.

Strategy now changes daily work. Sales demonstrates this scenario and qualifies requirements early. Research examines failed first launches. Engineers maintain the standard route’s reliability. Marketing stops promising automation for every possible process.

List what is deferred: unique enterprise routes, complex organisational structures and integrations without repeatable demand. This is not a permanent ban. These are boundaries around the current investment, giving the chosen promise a chance to be delivered well.

Write the strategy on one page

A working version can contain six short points:

• Goal: which business result is needed, and over what horizon.
• Diagnosis: what prevents that result now and which facts support the explanation.
• Choice: whose outcome we improve first, and which outcome that is.
• Advantage: why the proposed solution could be preferable to available alternatives.
• Resources and trade-offs: what the team does, stops doing and remains committed to.
• Review conditions: which observations would show that the direction needs to change.

This is a Fermi & Frost working format for discussing decisions, not a requirement of a particular framework. Calculations can support it, but the choice itself should be readable without twenty appendices.

Review conditions matter especially. A standard route might miss a critical constraint for most suitable clients. Implementation savings might be smaller than lost revenue. The team should know in advance that these findings trigger a new choice, not another explanation of why it should simply wait.

Test the strategy against a new request

Take a real request received this week. A prospect offers a large contract in return for a separate architecture. The current strategy helps assess their fit with the segment, the obligation created and what the work would displace.

The answer may be yes. But it is then a deliberate change in resource allocation, with promises and timelines recalculated. If every large request automatically outranks the chosen direction, the inbox is running the strategy.

A good document reduces these hidden turns. The team gains a shared reason for its next decision and a clear moment to test that reason again.