Master the fundamentals of product management, from user research and analytics to strategy, prioritization, communication, and execution.

Learn product management basics through practical lessons in user research, analytics, prioritization, strategy, and execution. Start on web, iOS, or Android.

Product Management Basics

Learn how to leverage AI in product management. Master AI fundamentals, prompt engineering, and practical applications for PMs.

Learn AI for product managers with practical lessons in AI fundamentals, prompt engineering, and everyday PM workflows. Start on web, iOS, or Android.

AI for Product Managers

Learn how to do competitive analysis. Master the fundamentals of competitive analysis and how to use it to make better product decisions.

Learn competitive analysis for product managers with practical lessons in market research and smarter product decisions. Start on web, iOS, or Android.

Competitive Analysis for Product Managers

## Outputs Are What You Ship. Outcomes Are What Change.

PMs help teams care about results, not just activity.

```productme-visual
{"asset":"resource:assets/content/b726bbe4-8a0c-4649-b9ec-489294e35076/pm-output-outcome.visual.json"}
```

The checklist and result represent the hypothetical example below; shipping alone does not prove the cause of a change.

- **Output**: launched a guided checklist
- **Outcome**: setup completion increased from 42% to 55%

Shipping matters because it creates the chance to improve behavior, not because it is the final goal.

<h2>Outputs Are What You Ship. Outcomes Are What Change.</h2>
PMs help teams care about results, not just activity.
<pre><code class="language-productme-visual">{"asset":"/content/b726bbe4-8a0c-4649-b9ec-489294e35076/pm-output-outcome.visual.json"}
</code></pre>
The checklist and result represent the hypothetical example below; shipping alone does not prove the cause of a change.
<ul>
<li>Output: launched a guided checklist</li>
<li>Outcome: setup completion increased from 42% to 55%</li>
</ul>
Shipping matters because it creates the chance to improve behavior, not because it is the final goal.

Which option is an outcome rather than an output?

Which option is an outcome rather than an output?

If a feature launches on time, the PM can assume the work succeeded even if user behavior did not improve.

If a feature launches on time, the PM can assume the work succeeded even if user behavior did not improve.

## Good Outcomes Need Success Criteria

A strong outcome definition usually includes:
- a target user or segment
- a primary success metric
- a time window
- a guardrail when needed

```mermaid
block-beta
  columns 2
  N0["Target segment"]
  N1["Primary metric"]
  N2["Time window"]
  N3["Guardrail"]
```

This prevents teams from calling any change a win.

<h2>Good Outcomes Need Success Criteria</h2>
A strong outcome definition usually includes:
<ul>
<li>a target user or segment</li>
<li>a primary success metric</li>
<li>a time window</li>
<li>a guardrail when needed</li>
</ul>
<pre><code class="language-mermaid">block-beta
 columns 2
 N0["Target segment"]
 N1["Primary metric"]
 N2["Time window"]
 N3["Guardrail"]
</code></pre>
This prevents teams from calling any change a win.

Which success definition is strongest for an AI summary feature?

Which success definition is strongest for an AI summary feature?

A good outcome definition often includes both a primary metric and a guardrail to catch harmful side effects.

A good outcome definition often includes both a primary metric and a guardrail to catch harmful side effects.

## Outcome Thinking Improves Product Judgment

When teams speak in outcomes, they can make sharper calls about:
- whether to continue or stop a bet
- whether a roadmap item needs iteration
- whether a proposed feature is really the best path

```mermaid
flowchart TB
  R["Observed outcome"]
  N0["Continue or expand"]
  R --> N0
  N1["Iterate or stop"]
  R --> N1
```

Outcome thinking makes trade-offs visible.

<h2>Outcome Thinking Improves Product Judgment</h2>
When teams speak in outcomes, they can make sharper calls about:
<ul>
<li>whether to continue or stop a bet</li>
<li>whether a roadmap item needs iteration</li>
<li>whether a proposed feature is really the best path</li>
</ul>
<pre><code class="language-mermaid">flowchart TB
 R["Observed outcome"]
 N0["Continue or expand"]
 R --> N0
 N1["Iterate or stop"]
 R --> N1
</code></pre>
Outcome thinking makes trade-offs visible.

A feature launched two weeks ago and the main metric is flat. What is the strongest PM response?

A feature launched two weeks ago and the main metric is flat. What is the strongest PM response?

Outcome-first roadmaps usually help teams understand why the work matters, not just what is being built.

Outcome-first roadmaps usually help teams understand why the work matters, not just what is being built.