ProductOSDocs

PM Academy

Lesson 8: Did it work?

Outcomes close the loop: record the result, compare it to the hypothesis, and watch your first complete Golden Thread light up.

An outcome is the measured result after shipping: did the metric move? It's the last stage of the Golden Thread and the only one that tells you whether everything upstream was worth it.

Building is the easy half

Shipping feels like the finish line, which is exactly why most builders stop there. But a shipped feature is a question, not an answer. The outcome record is where you write the answer down:

  • Hit: the metric moved as hypothesized. Do more of whatever this was.
  • Missed: it didn't. The bet failed; the learning didn't. What assumption broke?
  • Mixed: moved, but not enough, or moved something else. The most common and most informative result.

Recording a missed outcome honestly is a senior-PM move. The amateurs only log wins; their roadmaps never get smarter.

Do it now

  1. On Outcomes, create an outcome tied to your Lesson 5 initiative.
  2. Carry over the metric from your hypothesis, baseline and target.
  3. Set the result to pending if it's too early; come back when the data lands. Pending-with-a-date beats forgotten.

Then open the Golden Thread one more time and find your thread: the feedback you captured in Lesson 2, the theme from Lesson 3, the feature from Lesson 4, the initiative from Lesson 5, the release from Lesson 7, and now an outcome. End to end, every link real, every link yours.

Where to go from here

  • Run the loop again, it gets faster every cycle. The thread is the job; everything else is tooling.
  • Explore Strategy: OKRs are the same hypothesis discipline, one level up.
  • Keep the glossary close, and the PM Coach closer, ask it "what should I do next?" any time the path forks.

Last reviewed 2026-09-22