Skip to content

Product Learning

What are we here to learn this cycle?

Series identity. Learn in cycles. Move in a line. The product keeps moving forward, while understanding improves through repeated PDSA learning loops.

Use this guide to: turn a requirements conversation into a focused learning cycle.

PDSA emphasis: Plan, with explicit preparation for Do, Study, and Act.

Purpose

This guide helps a team begin a cycle by naming the learning objective before jumping to requirements. It is especially useful for product managers, designers, engineers, operators, and subject-matter experts who need a shared frame for uncertainty.

When To Use It

  • Before a discovery session, requirements workshop, or kickoff.
  • When the team has many feature ideas but no clear learning question.
  • When stakeholders are debating solutions before agreeing on the uncertainty that matters.

Core Questions

  • What are we here to learn this cycle?
  • What decision will this learning support?
  • What do we already know, and how do we know it?
  • What are we assuming because it is convenient?
  • What would surprise us?

Facilitation Pattern

  1. Open with the decision the cycle is meant to improve.
  2. Build three columns: known, assumed, unknown.
  3. Ask each participant to nominate one uncertainty worth reducing.
  4. Rank uncertainties by decision impact and reversibility.
  5. Close with one learning objective, one prediction, and one next action.

Working Example

A team planning account alerts begins with the question: What must we learn about which events customers consider urgent? The first cycle does not try to specify every alert. It predicts that failed payments and suspicious logins will be treated differently by different customer segments, then designs the next slice to test that prediction.

Common Traps

  • Writing requirements before naming the decision they serve.
  • Letting the loudest stakeholder define learning for everyone.
  • Collecting a long list of unknowns without choosing the next one.
  • Skipping prediction because the team wants to stay flexible.

Outputs And Artifacts

  • Learning objective for this cycle.
  • Knowns, assumptions, and unknowns list.
  • Decision to inform.
  • Prediction and evidence plan.
  • Next guide or session to use.

PDSA Linkage

This guide is the front door to Plan. It does not finish Plan by itself; it gives Plan a clear learning objective so the rest of the cycle has a reason to exist.

Working Worksheet

  • Write the learning question at the top of the board.
  • Separate facts from assumptions.
  • Select one uncertainty that matters now.
  • Write a prediction in plain language.
  • Name what will be observed during or after Do.
  • Schedule the Study conversation before starting the work.

Lineage Notes

Direct lineage: Walter Shewhart's statistical view of process learning influenced W. Edwards Deming, and Deming made PDSA a disciplined loop for prediction, action, study, and adjustment. Complementary quality thinkers - Juran, Ishikawa, Feigenbaum, and Taguchi - sharpen the product team's attention to fitness for use, causes, total systems, and variation. Ackoff, Drucker, Ries, and Blank are useful adjacent thinkers for systems, management, and product discovery, but they are not presented here as the historical source of PDSA.

References