Community

translate Automatic translation · View original

And How Do I Build the Strategy for a Product That Already Exists?

And How Do I Build the Strategy for a Product That Already Exists?
The vast majority of product strategy literature starts from scratch: an unsolved problem, a market opportunity, an unserved user. But most teams live a different reality: they have spent months or years developing a product that already has users, technical debt, accumulated features, commitments to clients, and a history that weighs heavily. How is a strategy built in that context? This is perhaps one of the most honest and least answered questions in the product discipline.

There is a pattern that repeats quite frequently in mid-sized organizations. A product was born to solve a specific problem, grew by accumulating requests, a team was formed, and at some point someone asks: But what do we want this product to be in two years? The silence that follows that question is usually diagnostic in itself.

Melissa Perri (2018) describes this phenomenon as the "build trap": organizations that measure success by the number of features delivered, not by the value generated. The result is a product that grows in complexity without necessarily growing in value. Strategy, if it exists at all, is implicit and scattered: it lives in the heads of several people who don't always agree.

This is neither a moral failing nor a sign of incompetence. In many cases, it is the logical result of growing without the time or resources to stop and think strategically. The problem is that, past a certain point, the absence of explicit strategy has a real cost: chaotic prioritization, misaligned teams, clients confused about the value the product provides, and an accumulation of decision debt that someone will eventually have to face.

The good news is that it is possible to build a strategy on top of an existing product. The bad news is that it isn't as clean as starting from a blank page, and it requires working with a reality that already has its own inertia.

Before the strategy: the honest diagnosis


The first mistake many teams make when trying to give themselves a strategy is jumping straight to defining objectives without first making an honest diagnosis of where they stand. Strategy without diagnosis is wishful thinking dressed up as a PowerPoint deck.

Richard Rumelt (2011) argues that a good strategy always has three components: a diagnosis of the situation, a guiding policy that defines how to address it, and a set of coherent actions. The diagnosis is not the least important of these: it is the foundation everything else rests on. Without it, the strategy floats.

What does an honest diagnosis for an existing product involve? At least four dimensions:

1. Who does this product actually exist for today?

Not for whom it was originally designed, but for whom it is really used. This can be surprising. Some products have found their market in a segment different from the original one, or are being used in ways no one anticipated. Teresa Torres (2021) insists that discovery work is not a one-off event but an ongoing practice: talking to users regularly is the only way to keep your understanding of the problem being solved up to date.

2. What value is the product currently delivering?

Not the value we think it delivers, but the value users recognize. This requires going beyond usage metrics and asking about impact. The distinction between output (features delivered), outcome (behavior change in the user), and impact (business result), popularized by Jeff Gothelf together with Josh Seiden in Lean UX (2013) and later developed in Sense & Respond (2017), is especially useful here. A product can have many features nobody uses, or few features that are critical to its users.

3. What is the real state of the product from the inside?

Technical debt, accumulated complexity, areas of the product that nobody wants to touch because "it has always worked this way." This directly affects the capacity for strategic execution. A strategy that ignores the real constraints of the system is a strategy that cannot be implemented.

4. What position does the product hold in its market?

Not necessarily in terms of market share, but in terms of perceived differentiation. Why do users choose this product over others? What would happen if it disappeared tomorrow? The answers to these questions define the strategic space available.

The problem of inherited commitments


One of the specific challenges of working with an existing product is that it comes loaded with commitments: to clients who expect certain features, to technical decisions that limit future options, to internal processes built around the product. Strategy cannot ignore these, but it also cannot be held hostage by them.

Marty Cagan addresses this in Inspired: How to Create Tech Products Customers Love (2018) when he distinguishes between the work of keeping the lights on, meaning keeping what already exists running, and the work of innovation and creating new value. Many product teams discover that between 60% and 80% of their capacity is consumed by the former, leaving little room to build toward the future. There is no magic solution to this, but explicitly recognizing it is the first step toward making conscious decisions about how to distribute investment.

The concept of a portfolio of strategic bets can be useful here. Instead of trying to solve everything at once, the strategy for an existing product needs to define which areas will be maintained as they are (because they work and don't justify additional investment), which areas will be improved incrementally, and which areas will be bets on innovation or transformation. This distinction, inspired by McKinsey's three horizons model, allows for more concrete and less abstract strategic conversations.

Strategy as hypothesis, not plan


One of the most common traps when building strategy is confusing it with a plan. A plan has defined steps, dates, and owners. A strategy is something else: it is a reasoned bet about how to create value in a context of uncertainty.

This distinction matters especially when the product already exists and there is real data to work with. John Cutler, whose writing on product management has considerably influenced the community in recent years, has repeatedly argued that product strategy should be treated as a set of explicit hypotheses that are validated or invalidated over time, not as a document that is written once and then filed away.

What are the practical implications? That strategy must make its assumptions explicit. Not just "we want to become the reference platform for segment X," but also: we assume that this segment has this problem, that our solution is better than the available alternatives, that we can reach it through these channels, and that the market will grow in this direction. Each of those assumptions is a hypothesis that can be true or false, and it should have some way of being tested.

This connects directly with the continuous discovery work that Teresa Torres proposes. If strategy is a hypothesis, discovery is the mechanism through which you test it. Not sporadically, but in a sustained way.

From diagnosis to strategic direction: the hard part


Once the diagnosis is honest and shared, comes the hardest part: deciding a direction. This inevitably involves choosing. And choosing means not choosing other things.

Marty Cagan and Chris Jones (2020) describe product strategy as the answer to three questions: What are the two or three most important problems we must solve to reach our vision? What makes these problems more important than others? How will we know when we have solved them? The apparent simplicity of these questions hides a real difficulty: they require the team, and the organization's leaders, to agree on a hierarchy of importance that is always debatable.

To get there, some teams use frameworks like Roman Pichler's Product Vision Board, which proposes structuring the vision around four elements: the target group, the needs to be satisfied, the product features that make it possible, and the business goals that justify it. The usefulness of this kind of tool lies less in the artifact itself than in the conversations it generates.

Another approach that can be useful is OKRs applied to product. Christina Wodtke (2016) argues that well-formulated OKRs are not just a measurement system but a way of articulating a bet: "we believe that if we achieve X (key result), this will bring us closer to Y (objective)." For an existing product, OKRs can be a way to make strategic hypotheses explicit and create a regular learning cycle.

The risk of strategy that never lands


There is a frequent problem with strategy exercises: they produce documents that end up in a drawer. The strategy exists on paper, but the team's day-to-day decisions are not guided by it. Why does this happen?

There are several possible reasons. One is that the strategy was built top-down without the participation of the people who have to execute it, generating little sense of ownership. Another is that the strategy is too abstract to be operational: "being the most innovative product on the market" doesn't help decide what to do this week. A third, more uncomfortable reason is that the organization's culture rewards delivery speed over the quality of decisions, which makes strategic thinking seem like a waste of time.

Amy Edmondson (2018) points out something relevant for this context: in organizations where it is not safe to admit uncertainty or question established priorities, strategy tends to become ceremonial. Nobody really challenges it because doing so carries a political cost.

For strategy to land, it needs to be connected to real work. Some teams achieve this through what some call strategy deployment or hoshin kanri adapted to product: a cascading deployment process in which high-level strategy is translated into concrete objectives for each level of the team, with feedback mechanisms that allow information to flow from the bottom up as well.

When strategy first requires an organizational conversation


There are situations where the product team is clear about the direction the product should take, but lacks the mandate or the ability to make certain decisions autonomously. This is especially common in organizations where the product has no clear executive champion, where functional silos resist changes to the business model, or where commitments to large clients act as strategic anchors.

In these cases, the product manager's job is not only to build a product strategy but also to make visible the strategic conversation the organization needs to have. This requires influence skills without authority and the ability to raise systemic problems in a way that is productive rather than defensive.

Cagan calls this the "product manager like a feature factory manager" problem: when the person responsible for product does not have the space or organizational support to do their job properly, strategy cannot flourish, regardless of which frameworks or tools are used. Recognizing this is not an excuse, but a prerequisite for being able to work on it.

A practical starting point: four questions before the plan


If we had to propose a concrete starting point for a team that needs to build or rebuild the strategy of an existing product, without promising a universal recipe, it could be working through these four questions before writing any document:

  • What problem are we still solving? Not the one we thought we were solving at the beginning, but the one the product solves today for its most valuable users. This question requires recent discovery work, not assumptions.
  • What are we not solving that should be part of our value proposition? There are gaps between what users need and what the product offers. Identifying them with data is different from listing them by intuition.
  • What are we doing that we shouldn't be doing? This is the most uncomfortable and most necessary question. There are features, product areas, and commitments that consume capacity without generating proportional value. Strategy is also about deciding what not to do.
  • What should be true about our context for this direction to make sense? Making the assumptions behind the strategy explicit allows you to identify which ones need to be validated first, and which learnings should update the course.

These four questions don't generate a roadmap, but they generate something more valuable: a team aligned on the diagnosis and with shared criteria for making future decisions.

Conclusions


Building the strategy for a product that already exists is no simpler than doing it from scratch; in many ways, it is harder. It requires working with reality as it is, not as we would like it to be. It requires asking uncomfortable questions about the value being generated and the value being left on the table. And in many cases, it requires organizational conversations that go beyond the product team.

There is no single answer or framework that works in every context. What seems consistent in both theory and practice is that strategy starts with diagnosis, not objectives; that it is a hypothesis, not a plan; and that it only has value if it connects with the team's real decisions.

What is your experience? Have you tried to build or rebuild the strategy of a product with a history?

Bibliography


  • Blank, S. (2019). Why the Lean Start-Up Changes Everything. Harvard Business Review. [Original reference: HBR, May 2013. The critique of the three-horizons model was developed in later posts on his blog at steveblank.com]
  • Cagan, M. (2018). Inspired: How to Create Tech Products Customers Love (2nd ed.). Wiley.
  • Cagan, M., & Jones, C. (2020). Empowered: Ordinary People, Extraordinary Products. Wiley.
  • Edmondson, A. (2018). The Fearless Organization: Creating Psychological Safety in the Workplace for Learning, Innovation, and Growth. Wiley.
  • Gothelf, J., & Seiden, J.
    • (2013). Lean UX: Applying Lean Principles to Improve User Experience. O'Reilly Media.
    • (2017). Sense & Respond: How Successful Organizations Listen to Customers and Create New Products Continuously. Harvard Business Review Press.
  • Perri, M. (2018). Escaping the Build Trap: How Effective Product Management Creates Real Value. O'Reilly Media.
  • Pichler, R. (2016). Strategize: Product Strategy and Product Roadmap Practices for the Digital Age. Pichler Consulting.
  • Rumelt, R. (2011). Good Strategy / Bad Strategy: The Difference and Why It Matters. Crown Business.
  • Torres, T. (2021). Continuous Discovery Habits: Discover Products That Create Customer Value and Business Value. Product Talk LLC.
  • Wodtke, C. (2016). Radical Focus: Achieving Your Most Important Goals with Objectives and Key Results. Cucina Media.

Take part in the poll

This article includes an active poll in the Scrum Manager community.

poll View the poll in the community