Why You Should Build a Data-Driven Product Strategy for Modern Product Management

data-driven product strategy - a SAFe series

Editor’s Note: You’re facing unprecedented business challenges. You need more than theories—you need a blueprint. Welcome to a Leader’s Blueprint, your weekly guide to proven strategies that get results.

You’re in the quarterly strategy meeting. The stakes are high, and a critical decision must be made: which major initiative should be prioritized for funding? The debate is passionate, but it’s driven by compelling arguments and seniority, not data. You have dashboards, but they’re filled with vanity metrics. No one can definitively answer the most important question: “Which of these options will actually move the needle on our business goals?”

When the loudest voice in the room becomes your primary decision-making tool, you’re not strategizing; you’re gambling.

What is a Data-Driven Product Strategy?

A data-driven product strategy is one that relies upon product analytics and qualitative insights to inform decision-making and which direction you should take your products in.

It’s a product management and development approach that aims to improve strategy by ensuring it’s driven by a comprehensive understanding of product usage based on concrete information and evidence, such as usage patterns, customer behavior, and performance metrics, rather than guessing what should be done next using assumptions or intuition.

The Hidden Costs of an Opinion-Driven Culture

Operating without clear, consistent product metrics is like flying a plane without an instrument panel. The risks are immense and go far beyond inefficient meetings:

Strategic Drift

Teams invest significant time and effort into features that feel important but are never tied back to defined outcomes. Over time, this disconnect causes the product to slowly drift away from its original goals and customer needs, as well as market position. Without data to course-correct and identify areas for improvement, even well-intentioned work can pull the product in conflicting directions.

Wasted Investment

When priorities aren’t grounded in measurable impact, precious capital and talent are spread thin across initiatives that don’t really make a difference. Engineering time, design effort, and marketing spend are consumed by features or experiments that fail to improve business performance or user experience and satisfaction. And this is often done without anyone realizing the true cost.

Inability to Learn

Without measuring the results of decisions, product teams lose the ability to learn from their work. Every launch becomes a shot in the dark, with no feedback loop to indicate success or failure. This prevents continuous improvement, making it difficult to refine strategy or build confidence in future decisions.

Slower Decision-Making

In the absence of data, decisions rely heavily on debate to try to reach a consensus. This leads to prolonged discussions and decision paralysis. Instead of moving quickly with clarity, teams spend time defending opinions rather than aligning around evidence and quantitative data.

Erosion of Trust and Alignment

When decisions are driven by opinion, stakeholders often question why certain choices were made. This can erode trust between teams and leadership, which creates friction across functions and makes it harder to align around a shared vision. Product development guided by the right data provides a common language; Without it, alignment becomes fragile and short-lived.

Data-Driven Product Management: From Guesswork to Guidance

The antidote to this uncertainty is building a culture of data-driven decision-making. In SAFe®, this is guided by the Measuring Product Performance competency. This framework provides clarity by viewing your product through four essential lenses: Business Outcomes, User Engagement, Customer Satisfaction, and Technical Performance.

This holistic view is powered by combining two types of metrics:

  • KPIs (Key Performance Indicators): hese are your instruments, providing a continuous pulse-check on the operational health of your product.
  • OKRs (Objectives and Key Results): This is your destination, aligning everyone toward ambitious, strategic goals.

Using both, you always know your current health and where you’re headed.

Benefits of Using Product Data to Make Strategic Decisions

Product management data analytics help PMs in several ways:

Enable Better Product Decisions for Product Managers

For a product manager, data provides the foundation for confident prioritization. By relying on key data instead of intuition alone, teams can optimize product decisions, focusing effort on initiatives that deliver the greatest value to users and the business.

Leverage Data Analysis to Move Faster with Confidence

Strong data analysis helps teams to reduce uncertainty and accelerate decision-making. When evidence is readily available, discussions become more focused, alignment happens faster, and teams can make data-driven decisions without unnecessary debate.

Create a Data-Driven Culture with Shared Metrics

Shared metrics help create a data-driven culture where teams align around outcomes instead of opinions. This common language enables better collaboration across functions and ensures everyone is working toward the same strategic goals.

Reduce Risk and Waste

When teams use product data effectively, they can identify underperforming initiatives early. This reduces risk and avoids wasted investment. It also ensures resources are allocated based on evidence rather than guesswork.

Support a Strategy Framework with Transparency and Accountability

An effective strategy depends on having a clear view of how the product is performing. When decisions are grounded in measurable outcomes, it becomes easier to understand the reasoning behind them and assess their impact over time. This shared visibility helps teams stay aligned and reinforces ownership of decisions. What’s more, it allows strategic choices to be evaluated and refined over time.

How to Use Data to Drive Product Growth and Actionable Insights

Start With a Clear, Measurable Question

You can begin this shift with a single question. This week, pick one significant feature on your upcoming roadmap and ask the team:

“If this feature is wildly successful, which single, measurable metric will change, and in what direction?”

If there isn’t a clear answer, the feature’s purpose—and its value—is a mystery.

Define Meaningful Metrics

Metrics should tell you something important about your product, not just fill a report. Think about engagement, retention, revenue impact, or operational efficiency—whatever shows real customer value. The key is choosing measures that are specific and actionable. They should be directly tied to decisions, so you always know which levers to pull next.

Integrate Metrics Into a Strategy Framework

Undertaking the first two steps above brings immediate clarity. But creating a true data-driven engine requires a complete system. The Measuring Product Performance competency provides a full blueprint for defining meaningful metrics across all four lenses and integrating them into powerful OKRs and KPIs. Stop flying blind. Unlock the full framework, competencies, and guidance you need to make every product decision with confidence. Get access by purchasing your SAFe® Insider membership today.

Continuously Measure and Adjust

Data isn’t a one-time check; it’s a constant feedback loop. Track results for every launch, experiment, or update, then analyze what’s working and what’s not. Use these insights to refine priorities, validate assumptions, and make smarter decisions for the next round of features. Your product evolves with each insight.

Embed a Data-Driven Culture

A data-driven strategy only works if the team lives it. Encourage using metrics in discussions and planning. Share results openly to celebrate wins and learn from misses. Over time, using data becomes second nature, helping everyone make better decisions and keeping the product aligned with real customer needs.



In this Series:


1 According to the McKinsey Global Institute, as cited on the Data Ideology website, “Data-Driven Organizations Are 23 Times More Likely to Acquire Customers, Six Times as Likely to Retain Customers, and 19 Times as Likely to Be Profitable as a Result”. Retrieved on October 22, 2025, https://www.dataideology.com/data/data-driven-organizations-are-23-times-more-likely-to-acquire-customers-six-times-as-likely-to-retain-customers-and-19-times-as-likely-to-be-profitable-as-a-result/

Connecting OKRs, KPIs, OVSs, and DVSs – For Successful SAFe® Implementation

The title of my post may read like acronym soup but all of these concepts play a critical role in SAFe, and understanding how they’re connected is important for successful SAFe implementation. After exploring some connections, I will suggest some actions you can take while designing, evaluating, or accelerating your implementation.

KPIs and OKRs

The SAFe Value Stream KPIs article describes Key Performance Indicators (KPIs) as “the quantifiable measures used to evaluate how a value stream is performing against its forecasted business outcomes.

That includes:

  • Health of day-to-day performance
  • Work to create sustainable change in performance

Objectives and Key Results (OKRs) are meant to be about driving and evaluating change rather than maintaining the status quo. Therefore, they are a special kind of KPI. Objectives point towards the desired state. Key results measure progress towards that desired state. 

But how do these different concepts map to SAFe’s Operational Value Streams (OVSs) and Development Value Streams (DVSs)? And why should you care?

Changing and Improving the Operation

Like Strategic Themes, most OKRs point to the desired change in business performance. These OKRs would be the ones that company leadership cares about. And they would be advanced through the efforts of a DVS (or multiple ones). 

For example, if the business wants to move to a subscription/SaaS model, that’s a change in the operating model—a change in how the OVS looks and operates. That change is supported by the development of new systems and capabilities, which is work that will be accomplished by a DVS (or multiple ones). 

This view enables us to recognize the wider application of the DVS concept that we talk about in SAFe 5. Business agility means using Agile and SAFe constructs to develop any sort of changing the business needs, regardless of whether that change includes IT or technology.

Whenever we are trying to change our operation, there’s a question about how much variability we’re expecting around this change. Is there more known than the unknown? Or vice versa? Are we making this change in an environment of volatility, uncertainty, complexity, and ambiguity? If yes, then using a DVS construct that employs empiricism to seek the right answers to how to achieve the OKR is essential, regardless of how much IT or technology is involved. We might have an OKR that requires business change involving mainly legal, marketing, procurement, HR, and so on, that would still benefit from an Agile and SAFe DVS approach.

These OKRs would then find themselves elaborated and advanced through the backlogs and backlog items in the various ARTs and teams involved in this OKR. 

In some cases, an OKR would drive the creation of a focused DVS. This is the culmination of the Organize around Value Lean-Agile SAFe Principle. This is why Strategic Themes and OKRs should be an important consideration when trying to identify value streams and ARTs (in the Value Stream and ART identification workshop). And a significant new theme/OKR should trigger some rethinking of whether the current DVS network is optimally organized to support the new value creation goals set by the organization.

Maintaining the Health of the Operation

As mentioned earlier, maintaining the health of the operation is also tracked through KPIs. Here we expect stability and predictability in performance. It’s crucial work but it’s not what OKRs or Strategic Themes are about. 

This work can be simple, complex, or even chaotic depending on the domain. The desire of any organization is to bring its operation under as much control as possible and minimize variability as it makes sense in the business domain. What this means is that in many cases, we don’t need Agile and empiricism in order to actually run the operation. Lean and flow techniques can still be useful to create sustainable, healthy flow (see more in the Organizational Agility competency). 

Whenever people working in the OVS switch to improving the OVS (or in other words working on versus in the operation), they are, in essence, moving over implicitly to a DVS. 

Some organizations make this duality explicit by creating a DVS that involves a combination of people who spend some of their time in the OVS and some of their time working on it together with people who are focused on working on the OVS. For example, an orthopedic clinic network in New England created a DVS comprising clinicians, doctors, PAs, and billing managers (that work the majority of their time in the OVS) together with IT professionals. Major improvements to the OVS happen in this DVS.

Improving the Development Value Stream

The DVS needs to relentlessly improve and learn as well. Examples of OKRs in this space could be: improving time-to-market, as measured by improved flow time or by improving the predictability of business value delivered, as measured by improved flow predictability. It could also be: organize around value, measured by the number of dependencies and the reduction in the number of Solution Trains required. 

This is also where the SAFe transformation or Agile journey lives. There are ways to improve DVSs or the overall network of DVSs, creating a much-improved business capability to enhance its operation and advance business OKRs. 

Implementing OKRs in this space relates more to enablers in the SAFe backlogs than to features or capabilities. Again, these OKRs change the way the DVS works.

Running the Development Value Stream

Similar metrics can be used as KPIs that help maintain the health of the DVS on an ongoing basis. For example, if technical debt is currently under control, a KPI monitoring it might suffice and hopefully will help avoid a major technical debt crisis. If we weren’t diligent enough to avoid the crisis, an objective could be put in place to significantly reduce the amount of technical debt. Achieving a certain threshold for a tech debt KPI could serve as a key result (KR) for this objective. Once it’s achieved, we might leave the tech debt KPI in place to maintain health. 

It’s like continuing to monitor your weight after you’ve gone on a serious diet. During the diet, you have an objective of achieving a healthy weight with a KR tracking BMI and aiming to get below 25. After achieving your objective, you continue to track your BMI as a KPI.

Taking Action to Advance Your Implementation Using OKRs

In this blog post, we explored the relationship between operational and development value streams and the Strategic Themes and OKRs. We’ve seen OVS KPIs and OKRs as well as DVS OKRs and KPIs. 

A key step in accelerating business agility is to continually assess whether you’re optimally organized around value. OKRs can provide a very useful lens to use for this assessment. 

Start by reviewing your OKRs and KPIs and categorize them according to OVS/DVS/Change/Run.

You can use the matrix below.

Run-focused OKRs

If you find some OKRs on the left side of the matrix, it’s time to rethink. 

Run-focused OKRs should actually be described as KPIs. Discuss the difference and whether you’re actually looking for meaningful change to these KPIs (in which case it really can be an OKR—but make sure it is well described as one) or are happy to just maintain a healthy status quo. 

You can then consider your DVS network/ART/team topology. Is it sufficiently aligned with your OKRs/KPIs? Are there interesting opportunities to reorganize around value?

This process can also be used in a Value Stream Identification workshop for the initial design of the implementation or whenever you want to inspect and adapt it.

Find me on LinkedIn to learn more about making these connections in your SAFe context via an OKR workshop.

About Yuval Yeret

Yuval is a SAFe Fellow and the head of AgileSparks

Yuval is a SAFe Fellow and the head of AgileSparks (a Scaled Agile Partner) in the United States where he leads enterprise-level Agile implementations. He’s also the steward of The AgileSparks Way and the firm’s SAFe, Flow/Kanban, and Agile Marketing. Find Yuval on LinkedIn.

Share:

Back to: All Blog Posts

Next: Aligning Global Teams Through Agile Program Management: A Case Study