Build a journey map stage by stage. Define persona and scenario, then add stages with user goal, actions, thoughts, emotions, pain and opportunities. Reorder with the arrows; delete with the ×. Export as markdown or CSV, or print the whole map on one wide page.
A journey map is only useful if it changes design or operational decisions. The two things that make the difference between a map that gets referenced and a map that gets filed:
Populate from research, not opinion. Base each row on evidence — session recordings, interview transcripts, support tickets, analytics funnels. Where you're inferring (especially under "thoughts" and "emotions"), say so. Opinion-only maps mislead; evidence-backed maps compound.
One map per critical moment, not one per persona. A user behaves differently in onboarding vs. recovery vs. repeat purchase. One average map hides that variance. Build the three or four maps that cover the critical moments; skip the ones where the design response would be the same anyway.
Related: journey map glossary, service blueprint (goes below the line of visibility), printable template, interviews as the primary evidence source, method finder → journeys.