# AI Product Strategy: How to Decide Where AI Goes

> An AI product strategy is a portfolio of bets with measured value, data and risk. Learn how to score initiatives and decide where to invest first.

*Tags: ai, strategy, product, roadmap*

---


> [!info] Quick Definition
> An **AI product strategy** is the plan that decides where AI is used inside a product, with which data, at what risk and against which success criteria. It is treated as a portfolio of bets reviewed regularly, not as a list of chat features.


## What changes from a normal product strategy?

A traditional feature behaves in a fixed way: when the user clicks, something predictable happens. An AI feature produces outputs that vary and sometimes get things wrong. That changes three things: how you measure success, how you manage risk and how you plan the roadmap.

Gocious, a company that sells product portfolio management software, argues in its April 2026 guide that static roadmaps can't keep pace with AI. It also warns that evaluating initiatives one by one hides trade-offs, such as cannibalization between products or overlapping capabilities. Its proposal is to look at them all together, as a portfolio. It is a source with a commercial interest, but the idea is useful. To bring it into your roadmap, see [[ai-roadmap|AI roadmap]].

## How do you decide where AI goes?

Start from the business and the user, not from the technology. A practical order:

1. **Map the current process** and mark the points where users lose time or make mistakes.
2. **Check that AI is necessary.** Google's People + AI Guidebook (PAIR) reminds us that a rule-based or heuristic solution often works just as well as an AI version, or better. If that is your case, go to [[when-to-use-ai-in-a-product|when to use AI in a product]].
3. **Decide whether to automate or augment.** PAIR suggests automating tasks that are difficult or unpleasant, and augmenting (helping without replacing) those people enjoy, those with personal responsibility and those with high stakes. A useful question for your interviews: "If you had a human assistant for this task, what would you hand over?"
4. **Score each initiative** on the same criteria (next section).
5. **Prioritize what uses proprietary data or supports your differentiation**, and buy generic capabilities while requiring clear terms on data handling and contract exit. More detail in [[build-vs-buy-models|build vs. buy models]].
6. **Reallocate investment** when a bet matures, when it stalls or when regulation and model performance change.

Presta, a product agency, offers a quick filter for candidates: prioritize problems that take a human expert more than two minutes, that repeat and that depend on a lot of data. It is a vendor's heuristic, not a standard; use it only to order the list.

## How do you score each initiative?

Gocious proposes six criteria for a portfolio scorecard. The questions in the right-hand column are our adaptation for your team, not text from the source:

| Criterion | Question for the team |
|---|---|
| Customer and business value | What real problem does it solve and how will we see it in the business? |
| Strategic differentiation | Does it set us apart, or can any competitor copy it tomorrow? |
| AI and data readiness | Do we have the data, clean and with permission to use it? |
| Risk and governance | What happens if it is wrong? Who is accountable? |
| Time to value | When will we see the first measurable result? |
| Portfolio balance | Does it overlap with another bet or depend on the same technical approach? |

Gocious doesn't define scales or weights, so your team must set them (for example, 1 to 5) and agree on them before scoring. Consistency matters most: the same criteria at every review, and rules agreed in advance for deciding whether an experiment advances, is redirected or is retired.

## Which metrics make sense?

Presta proposes prioritizing **learning velocity** over release speed: how fast the system improves with use. Its framework includes two more ideas. The first is observability: knowing why the AI made each decision (with audit logs of agent decisions) and defining fallback logic for when the model is unsure. The second is outcome-driven iteration: measuring "problem resolution speed" instead of time on screen. Among its metrics are the task completion rate and how often people correct the AI.

These are a vendor's opinions, and the page doesn't explain how to calculate learning velocity, but they make a useful starting point. PAIR adds something that is often forgotten: weigh false positives and false negatives by their real-world consequences, and set thresholds along with the action the team will take if they are crossed. To go deeper, see [[ai-product-metrics|AI product metrics]] and [[ai-feature-roi|ROI of AI features]].

## What limits should you set?

Gocious warns about three mistakes: bolting AI onto workflows that weren't redesigned, giving autonomous agents the power to execute high-impact actions (deleting data, moving money) without human verification, and letting compute costs grow through duplicated or unauthorized projects.

For the last point, keep an inventory of all AI work, including "shadow" projects outside the formal roadmap, with one owner for each. Gocious also describes a Product Ops role that centralizes access to data, standardizes the AI stack to avoid paying for redundant compute, and feeds telemetry back to PMs, such as latency or hallucination rates. If you are defining an agent's scope, review [[autonomy-levels|autonomy levels]] and [[guardrails|guardrails]] before deciding what the system may do without asking.

## Example

Illustrative example: an insurer has four AI ideas: a support chat, an automatic claims summary, a marketing copy generator and a quoting assistant. The team scores each one. The chat has high volume, but its value depends on policy data that isn't clean yet. The claims summary uses proprietary data and saves adjusters time, so it goes first. The copy generator is bought from a vendor with clear data terms. The quoting assistant is postponed until the team has fallbacks and audit logs for decisions involving money. The roadmap ends with one strong bet, one exploration and two purchase decisions, each with a written review rule.

## Common mistakes

- Building a list of AI features without a user problem behind each one.
- Measuring the strategy by how many features shipped.
- Building in-house what is a commodity and buying what differentiates you.
- Giving an agent full autonomy without limits on what it can do.
- Not defining what happens when the model fails or is unsure.
- Scoring with different criteria at each review, so nothing is comparable.
- Reviewing the roadmap once a year when change happens monthly.

## When does an AI strategy not fit?

When the product has no clear problem that AI can solve better than a simple solution, or when there is no data and no capacity to measure results. In those cases, improving the flow without AI often delivers more value with less risk.

## Sources

- [Gocious, AI in product management: guide for 2026](https://gocious.com/blog/ai-in-product-management-guide-for-2026-for-product-leaders): Kevin Jankay, April 13, 2026. A source from a portfolio software vendor.
- [Presta, AI product strategy in 2026](https://wearepresta.com/ai-product-strategy-2026/): a product agency; the page names no author. Its figures and frameworks are opinions with no cited studies.
- [Google PAIR, People + AI Guidebook: User Needs + Defining Success](https://pair.withgoogle.com/chapter/user-needs/)


---

Source: https://www.fernandoux.com/en/wiki/ai/ai-product-strategy/