---
title: Understanding Output, Outcome, and Impact
description: What's the difference between Output, Outcome, and Impact. What do they really mean? How are they connected? And why should we care?
date: 2025-02-25
author: Christophe Achouiantz, Joakim Sundén
keywords: output, outcome, impact, customer behavior, empowered team, product model
category: Outcomes
lastModified: 2025-02-25
slug: understanding-output-outcome-impact
---

In product development, **Output, Outcome, and Impact** are often confused or used interchangeably. But understanding their differences \- and how they connect \- is critical for setting the right goals, tracking success, and avoiding wasted effort.

## Defining Output, Outcome, and Impact

Each concept answers a different question:

* **Output** → *What did we build?*  
* **Outcome** → *Did it change customer behavior?*  
* **Impact** → *Did it create value for the business?*

Many organizations focus on **Output**, e.g., measuring success by the number of features shipped. But **most product bets fail**, not because they weren’t built well, but because they didn’t drive meaningful change.

![Outputs generate outcomes that generate impacts](Output-Outcome-Impact.png)

## The Key Differences

### Output: The Work We Produce

This is the **feature, epic, or product delivered**—the tangible thing we ship. While shipping is necessary, it’s only a **means to an end**. A feature is just a **hypothesis** on how to generate customer or business value until we see if it makes a difference.

And most hypotheses are wrong. Companies like Google and Microsoft have found that [only 10-30% of product ideas actually deliver meaningful results](https://hbr.org/2017/09/the-surprising-power-of-online-experiments). This is why focusing on Output alone—without validating whether it leads to meaningful Outcomes and Impact—wastes effort.

> If a feature ships but customer behavior remains unchanged, it’s wasted effort.

### Outcome: The Change in Customer Behavior

A product succeeds when it **creates real value for customers,** solving their problems, making their lives easier, or opening up new possibilities for them. Success means making things easier, safer, better, faster, or cheaper for customers. 

> Outcomes answer the question "How are our customers better off because of what we built?"

### Impact: The Business Results

Even if a product improves customers’ lives, it must also **benefit the business**, e.g., through revenue growth, retention, or strategic advantage. The best products **balance all three**:

> Products (Output) that customers love (Outcome), yet work for the business (Impact) (*)

## How They Connect—and Why We Minimize Output

High-performing teams aim to **minimize Output while maximizing Outcome and Impact**. The key questions are:

1. **Output → Outcome**: Does what we build *improve our customers' lives*?
2. **Outcome → Impact**: Does that change *translate into business success*?

Instead of measuring success by **features shipped**, we should track **whether we’ve moved the right metrics**. That’s what separates **feature factories** from **impact-driven product teams**.

> Is your team measuring success by shipping features or by changing customer behavior? 
> Are your outcomes translating into business impact?

Bringing clarity to these distinctions helps teams focus on what truly matters—delivering **real value**, not just more work.

### Example: Spotify’s Discover Weekly

* **Output:** A new feature \- an automatically generated weekly playlist personalized for each user.  
* **Outcome:** Users discover new music effortlessly, finding songs they love without having to search. This makes Spotify more personalized and valuable in their daily lives.  
* **Impact:** Increased user retention, higher engagement, and more conversions to paid subscriptions, driving business growth.

For a deeper dive into how **Discover Weekly** emerged from empowered product teams working within a strong **Product Operating Model**, check out [The Product Model at Spotify](https://betterproductwork.com/blog/product-model-at-spotify), co-written with Marty Cagan.

---

(*) The phrasing **"Products (Output) that customers love (Outcome), yet work for the business (Impact)"** is our synthesis of **Marty Cagan**’s well-known statement that great product teams build “products that customers love, yet work for the business” and the Output → Outcome → Impact model, which we originally encountered through **Jeff Patton**’s work. The model itself has been widely discussed in product development circles and aligns with frameworks used by thought leaders such as **Gojko Adzic** and **John Cutler**. Its origins likely trace back to broader discussions in systems thinking and outcomes-based planning.