How to use the User Journey Map Generator.
Journey maps should preserve the difference between observed friction and a proposed fix. Include the transitions between channels or teams.
Make the workflow fit your task.
Map stages, actions and transitions from the supplied research, keeping evidence attached to each friction point. Show proposed improvements separately so the map does not turn an interpretation into an observed customer experience.
- What you provide
- Research evidence and journey stages.
- What you get
- Touchpoints, friction and opportunities grounded in observations.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
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.
Completed example
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.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Can a journey map include steps that were not observed?
Mark them as hypotheses or gaps. Do not present a plausible sequence as established research evidence.
Why does the map miss the problem between two screens?
Include handoffs, waiting and channel changes. Friction often occurs between visible interfaces rather than inside a single screen.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑