Map a product flow

Create the smallest complete flow that lets a product team make interface and implementation decisions without inventing missing behavior.

Establish the job and surfaces

State the user job, entry condition, successful end state, and explicit non-goals. Enumerate actual platforms and native surfaces; reject “cross-platform” as a sufficient specification.

Read existing product requirements, shipped UI, analytics, and support evidence when available. Separate observed behavior, approved requirement, inference, and open decision.

Write structure before diagrams

Give every screen/state a stable short identifier. For each, specify: