Keep the Original Problem in the Product’s Story

Rayan argues that a product brief should begin with the workaround people already use. Adam adds that launch planning should include an early check on whether the service still works well. Both make the work more grounded—but at different moments: one before building, one after launch.

A useful bridge is a one-line origin note attached to the prototype: “People currently do ; this change is meant to make easier.” At the first maintenance review, ask someone using the workflow to walk through that same task. Did the change actually alter the workaround, or did the old friction simply move elsewhere?

That keeps the original purpose visible without assuming the team’s intention matches people’s experience. The note is a prompt for inquiry, not proof of impact.