Product · Strategy · DecisionMaking

'Where We are NOT Going': Why Product Strategy is the Art of Saying 'No'

How to formalize product boundaries and explain to the team and stakeholders why some directions are off-limits.

'Where We are NOT Going': Why a Strong Strategy is Built on Refusals

Most products die not because they did too little, but because they did everything at once. Saying 'yes' is easy. Saying 'no' is harder, but it's what makes a strategy viable and a team effective.

Why Say 'No'

The idea is simple: every 'yes' has a hidden cost. You're not just taking on a task—you're giving up all other opportunities that could have provided more value.

Why refusal is part of the strategy:

• Maintains focus. The team sees the boundaries: what's important and what's a distraction.
• Reduces noise. The endless stream of 'let's also do this' disappears.
• Speeds up decision-making. When there are off-limits areas, there are fewer arguments and 'politics.'
• Protects the product from overgrowth. The natural desire to expand often kills the core value.

Saying 'no' isn't about being harsh. It's about respecting the team's time and the user.

How to Formalize 'Not Going'

A formalized 'no' is not an emotional refusal, but a structured logic that everyone understands.

1. Define Refusal Criteria

Examples of working filters:

• Doesn't align with the North Star: doesn't enhance core user value.
• The economics don't work: high CAC, low margin, long payback period.
• Unmanageable technical cost: huge debt, complex infrastructure, high risk.
• Wrong audience: a feature for a segment we deliberately don't serve.
• Expansion beyond the mission: danger of the product sprawling in all directions.

Criteria are like a checklist at the entrance: they reduce subjective decisions.

2. Tie 'No' to Data

A refusal without facts causes conflict. A refusal with data brings understanding.

Show:

• the economics (LTV/CAC, margin, impact on profit);
• the effect on the North Star and core value;
• an estimate of technical risks and time;
• the opportunity cost of focus.

3. Offer Alternatives (An Important Element of Trust)

'No' without alternatives is a dead end. 'No' with an alternative is a mature product dialogue.

Working options:

• Manual-first or a temporary workaround;
• Integration through partners instead of in-house development;
• A pool for the next quarter without commitment;
• A limited experiment if the risk is low.

Argumentation Template (3 Points)

1. Problem: what we are trying to solve.
2. Why it's not our priority: data, economics, strategy.
3. What we are doing instead: an alternative, a different path, a temporary solution.

A simple framework that reduces communication conflict.

How to Foster a Culture of 'Healthy Refusals' Within the Team

Add a Game: 'Devil's Advocate' by Lot

Sometimes a team agrees too quickly on ideas because 'it sounds nice' or 'someone important suggested it.' To maintain clear thinking, simple game mechanics can help.

How it works:

1. At the beginning of the meeting, draw lots to appoint a devil's advocate.
2. Their task: to ask a clarifying or critical question for any argument.
3. They are not defending their personal position—they are defending the quality of the decisions.
4. Other participants do not take the criticism as an attack—it's a role, not the person's opinion.
5. In the next meeting, the role passes to someone else.

Why it's needed:

• it breaks groupthink ('if everyone is nodding, I will too');
• it helps uncover hidden risks and dependencies;
• it makes discussions more honest, especially where there's 'deference to authority';
• it teaches how to argue with logic, not sell ideas with emotion;
• it reduces personal conflicts—no one is 'attacking,' the person is playing a role.

This little game adds structure and healthy criticism without destroying the atmosphere.

Not-To-Do Map: A Map of the Product's Off-Limits Zones

Not-To-Do Map is an explicit map of what the product deliberately does not do: segments, features, scenarios, integrations that we don't take on, even if we can.

It's the flip side of the roadmap: if the roadmap answers the question 'where are we going,' the Not-To-Do Map answers 'where are we definitely not going and why.'

What a Not-To-Do Map Consists Of

Usually there are 3–5 blocks:

• Not our users. Who the product is not created for (e.g., enterprise > 5k employees; public sector; freelancers).
• Not our scenarios. What people might want, but we don't support (e.g., fully custom BI, offline mode, white-label).
• Not our money. Monetization models we are forgoing (one-time sales, custom projects, integration business).
• Not our geography/domain. Markets or industries we are consciously not entering.
• Not our technologies. Things we refuse to pull into our stack (our own payment gateway, our own ML platform, etc.).

Each point should have 2 things:

1. A short description.
2. The reason 'why it's outside our scope' (economics, risk, strategy, culture).

How to Draw a Not-To-Do Map with the Team

A simple flow for a 60–90 minute workshop:

1. Gather raw material. Write on sticky notes (or in Miro): what requests, segments, and ideas have come up in the last year and caused 'should we/shouldn't we' debates.

2. Group them. Put them into clusters: users, scenarios, money, geo, technology.

3. Roughly 'no/maybe/yes.' Quickly mark each group:

   • yes — fits the strategy;
   • maybe — need data;
   • no — definitely not us.

4. Analyze the 'no's.' For each 'no' group, answer two questions:

   • why is this not for us (1–2 objective reasons);
   • what simple text will we show stakeholders and the team.

5. Document. Transfer to a clear artifact: a Not-To-Do Map—a document or wiki page with clear wording.

6. Regular review. Once a quarter, check: what is still relevant, what has changed (e.g., monetization model or segment priority).

Example Not-To-Do Map