Ask a CX team where their journey map is and you will usually get a file path. Ask when it was last changed and the room goes quiet. The map was real for a day. Then it became a picture of a day.
It is not a workshop problem
The workshop usually goes well. People argue, sticky notes move, the emotion line dips at checkout and everyone nods. The trouble starts on Monday, when someone has to turn the wall into something the rest of the organisation can see.
That someone opens a slide tool. The map becomes twelve rectangles and a wavy line. It looks fine. It is also dead, because nobody will open a slide to change one card, and nobody owns the file anyway.
Three things that keep a map breathing
A number that changes. When cart completion sits under the Purchase stage and refreshes every morning, people open the map to look at the number. Once they are there, they fix the card next to it.
A backlog, not a gallery. If every pain point has a key (PAT-4) and a score, the map is where the roadmap conversation starts. If pain points are just red stickies, the conversation happens somewhere else and the map is not invited.
A link, not an export. Send stakeholders a saved view, not a PDF. The link is current next month. The PDF is a fossil by Friday.
What this asks of the tool
None of this works if editing the map is a chore. The editor has to save while you talk, move what you drag, and never make you wait. That is the whole reason Journima exists: we think craft in the editor is what separates a living map from a picture of one.
If you have a map that is quietly dying in a shared drive, try putting one real metric in it and see what happens.