Skip to content
Module
Module 2 of 6Lesson 1 of 2~15 min

Outputs, product outcomes and business outcomes

How to tell what your team ships apart from what actually changes for your customers and for the business. The distinction reshapes the conversation with leadership: instead of reporting on features delivered, you show a measurable effect and give the team a goal it can genuinely influence.

Take this lesson: your first course is freeSee the full syllabus

Lesson objective

By the end of this lesson, you will be able to tell an output, an adoption metric, a product outcome and a business outcome apart, and rewrite a feature list as a chain that links the target business outcome to the behavior changes your team can achieve.

Questions this lesson answers

  • What's the difference between an output, a product outcome and a business outcome?
  • How do you turn a feature-based roadmap into measurable outcomes for your team?

Topics covered

  • output vs outcome
  • product outcome
  • business outcome
  • adoption metric
  • outcome-based roadmap

In the glossary

Full glossary

Where it fits

From outputs to outcomes

What does my team need to move, and how do I write it so everyone aims at the same thing?

Lessons in this module

  1. Outputs, product outcomes and business outcomes (this lesson)
  2. OKRs that help, and their failure modes

What you will learn in this module

This lesson is part of the course Prioritize and build an outcome-based roadmap

  • Tell outputs, product outcomes and business outcomes apart, and phrase a team's goal as a measurable change in behavior it can influence.
  • Write useful OKRs (a qualitative objective, measurable key results, guardrails) and spot their common failure modes.

Related courses