User Journey Map Generator — illustrative example

INPUT
Research note P1: a buyer compared the size table, contacted support because the measurement method was unclear, then returned to checkout after receiving an explanation. Map observed steps and a proposed improvement separately.

RESULT
Observed journey, source P1:
1. Compare size table — uncertainty about how measurements were taken.
2. Contact support — obtain an explanation of the measurement method.
3. Return to checkout — continue with that explanation available.
Proposed improvement: add the verified measurement method beside the table.
Evidence limit: this is one supplied account, not a measured frequency across buyers.

REVIEW
Journey maps should preserve the difference between observed friction and a proposed fix. Include the transitions between channels or teams.

This is a teaching example, not a live execution record.