The problem
User journey maps are most powerful when they're built collaboratively, in real time, on a whiteboard. The design team, the PM, the customer success rep, and a real user if possible — each person contributes what they know about different stages of the journey. The whiteboard becomes the shared mental model. Disagreements about what the user experiences get resolved visually, on the board.
The map typically has four to six rows across the top stages: Aware, Consider, Onboard, Use, Renew (or whatever fits the product). Each column has rows for Actions (what the user does), Touchpoints (how they interact with your product), Emotions (how they feel — represented as a curve), and Pain Points (where it goes wrong). Opportunities live at the bottom.
The problem is that a journey map is visually rich and hard to translate into a document. The emotion curve is a visual, not a text. The pain points in column four connect to opportunities in column five but that connection is spatial, not textual. The person who wasn't in the room gets a flat bullet list that doesn't capture any of the visual logic.