Review questions — Product mission and outcome

Module synthesis: Product mission and outcome

Begin product work by separating the user outcome from the output a team builds and the activity it performs. A customer's feature request does not establish that the feature solves the underlying problem. In the report-sharing case, an old version appeared through a link; diagnosing the job and alternatives came before committing to export, while a commercial promise went to its owner. We then mapped booking from finding a suitable time through understanding terms and confirmation, defining the unit behind each transition before explaining departures. A measurable outcome needs a segment, window, numerator, denominator and guardrails against shifted harm. Fewer missed appointments do not imply a better rate if total due appointments fall faster. For a new request, state the user job, two competing explanations, a task-success measure and a harm measure. Product acts within delegated authority and calls on design, engineering and operations expertise.