PM Gym

Business Outcomes & Product Outcomes

Connect the features you ship to the results that matter

Shipping features feels like progress — but features are just outputs. This guide draws the chain from outputs to product outcomes (a change in user behavior) to business outcomes (company results), and shows which one your team should actually own.

Step-by-step lessons

Outputs, Outcomes & the Chain

Four short lessons: outputs vs. outcomes, the two kinds of outcome, how they connect, and how to set good targets.

1

Outputs vs. Outcomes

The most important distinction in product: an output is what you build; an outcome is the change it creates. Confusing them is how teams stay busy while nothing improves.

Everyday example — the gym

"I went to the gym 20 times this month" is an output — an activity you did. "I can now run 5k without stopping" is an outcome — the change that activity produced. You can hit the gym 20 times and get nothing if you do it wrong. The gym visits only matter because of the change they're supposed to cause. Same with shipping features: the feature isn't the win; the change it creates is.

What you build

Output

A feature, screen, or release. "We shipped a redesigned dashboard." Easy to count, easy to fake progress with.

What changes

Outcome

A measurable change in behavior or results. "Users now complete setup 30% more often." What actually matters.

A team that measures itself only by outputs is a feature factory — shipping endlessly, learning nothing about whether any of it helped.

Quick check

Which of these is an outcome, not an output?

2

Business vs. Product Outcomes

Not all outcomes are the same. There are two flavors, and knowing which is which tells you what a product team can actually control.

Everyday example — the farmer

A farmer wants money from the harvest — that's the business outcome. But they can't reach out and grow the cash directly. What they can control is watering, healthy soil, and pulling weeds — the product outcomes. Do those well and the harvest (and the money) follows. Product teams are the farmer: you tend the behaviors you can influence, and the business result grows from them.

Company result

Business outcome

Money-and-company metrics: revenue, retention rate, cost, market share. What the business ultimately cares about.

Behavior change

Product outcome

A change in what users do that drives the business result: activation rate, weekly active use, tasks completed.

Teams can rarely move a business outcome directly — but they can move user behavior. That's why product teams own product outcomes.

Quick check

A product team is told to "increase annual revenue by 20%." Why is a product outcome a better target for them?

3

Connecting the Chain

Output, product outcome, and business outcome form a chain. A good plan makes each link plausibly drive the next — and uses the right kind of signal to read progress.

Everyday example — dominoes & weather

Think of falling dominoes: the feature knocks over the behavior change, which knocks over the business result. If there's a gap between two dominoes, the chain breaks — a feature nobody uses never reaches revenue. And on leading vs. lagging: dark clouds are a leading signal (rain is coming, act now — grab an umbrella); being soaked is a lagging signal (it already happened, too late). Steer by the clouds, not the soaking.

Output → product outcome

The feature should change a behavior. Redesigned setup → more users finish setup.

Product outcome → business outcome

The behavior should drive results. More users finishing setup → higher retention → more revenue.

Leading vs. lagging

Product outcomes are leading indicators (move early, predict). Business outcomes are lagging (confirm late).

Quick check

Weekly active use (a product outcome) starts climbing this month; annual retention (a business outcome) won't be measurable for a year. What does this show?

4

Setting Good Outcome Targets

A good product-outcome target passes three tests: it describes behavior, it's measurable, and the team can actually influence it. Miss any one and the target quietly stops working.

Everyday example — the thermostat

"Make the house feel nicer" is a bad target — vague, unmeasurable, and everyone pictures something different. "Set the living room to 21°C by 6pm" is a good one — it's a specific, measurable thing you can actually control with the dial in front of you. A good product outcome is the thermostat setting, not the fuzzy wish. Name the behavior, put a number on it, and make sure your team's hand is on the dial.

Weak target vs. strong target

Weak: "Make users happier." Not behavioral, not measurable, not clearly ours.

Strong: "Increase the share of new users who complete a first project in week one from 22% to 40%."

The strong one names a behavior, gives a number, and sits squarely within what the team can move.

Quick check

Which is the strongest product-outcome target for a team to own?

Review the concepts

Outcomes Flashcards

6 cards covering the essentials. Click a card to flip it.

Core Card 1 of 6

Output

Click to flip

Tip: say the answer out loud before flipping.

Explanation

In practice

1 / 6
Apply what you learned

Practice Scenarios

15 situations that test whether you can separate output from outcome, pick the right target, and read the signals. Choose the strongest move, then read why the rest fall short.

Scenario 1

At your quarterly review, your team proudly reports it shipped 14 features. No one mentions whether any metric moved.

What's the problem with this report?

Scenario 2

Leadership sets your team's sole objective as "increase gross revenue by 15% this year."

How should you reframe it for your team?

Scenario 3

Your redesigned onboarding is live. Signups look flat, but the share of new users who finish setup jumped from 20% to 45% this week.

How do you read this?

Scenario 4

Your roadmap for next quarter is a list: "Build dark mode, build SSO, build a new dashboard, build export-to-PDF." A stakeholder asks, "What will be true for users that isn't true today?"

What does that question expose?

Scenario 5

A designer proposes tracking "number of buttons clicked" as the team's success metric for a new feature.

What's the risk with this metric?

Scenario 6

Your team's product outcome — "weekly active teams" — is climbing nicely. But revenue is flat and the CFO is unhappy.

What's the most likely explanation to investigate first?

Scenario 7

To hit a "daily active users" target, a growth team adds a daily push notification that pulls people in for a two-second glance. DAU rises 25%. Retention and satisfaction don't budge.

What happened to the metric?

Scenario 8

Two teams pitch their quarterly targets. Team A: "Ship the mobile app." Team B: "Raise the share of users active on mobile from 10% to 30%."

Which target is stronger and why?

Scenario 9

An executive says: "I don't want to hear about 'activation rate.' Just tell me the revenue impact of every feature, every sprint."

What's the reasonable pushback?

Scenario 10

Your team target is "improve user satisfaction." Six weeks in, no one can agree on whether you're making progress.

What test does this target fail?

Scenario 11

A PM sets the target: "Reduce world hunger through our food-delivery app." The team feels inspired but paralyzed.

What test does this fail?

Scenario 12

Marketing celebrates: "We got 100,000 app downloads this month!" But weekly active users barely moved.

How do you interpret the download number?

Scenario 13

Your team hit its product outcome (activation up 15 points) but leadership asks: "So what? Prove it mattered to the business."

What's the right way to answer?

Scenario 14

A leader wants the team held accountable to annual net revenue retention as its only quarterly goal — a metric that won't visibly move for many months.

What's the practical problem?

Scenario 15

Your team keeps a scoreboard of "story points completed per sprint" and treats rising points as the main sign of success.

What trap is the team in?

Lock it in

Guess the Term

Read the clues and name the concept. The fewer clues you need, the more points you score.

Round 1 Score 0
Keep it handy

Outcomes Quick Reference

The whole topic on one screen.

The Chain

Each link should plausibly drive the next.

Output

What you ship. A feature or release.

Product outcome

The behavior change it creates. What the team owns.

Business outcome

The company result it drives. Revenue, retention, cost.

Reading the Signals

Leading indicator

Moves early, predicts. Usually a product outcome — steer by it.

Lagging indicator

Confirms late. Usually a business outcome — verify with it.

Avoid the feature factory

If you only count outputs, you're measuring effort, not value.

Is It a Good Target?

A product outcome must pass all three tests.

Behavior

Does it describe something users do, not a feature you ship?

Measurable

Is there a number you can check progress against?

Influenceable

Can this team actually move it? (Is your hand on the dial?)

Template

"Raise [behavior] from X% to Y% by [when]."

Vanity-Metric Red Flags

Numbers that look like value but often aren't.

Downloads / signups alone

Top-of-funnel counts. Meaningless if they don't become active use.

Raw clicks / page views

Can rise because users are confused. Count jobs done instead.

Story points / features shipped

Internal effort. Measures how much you make, not what changed.

Watch for Goodhart

When a proxy becomes the target, it gets gamed. Check it against the real goal.

Notification