Section 1
The problem is drift, and drift is invisible asset by asset
Every artefact is written to be good on its own terms. The homepage was rewritten last year, the sales deck evolved through the deals it won, the onboarding sequence was built by whoever owned support at the time. Each is defensible. Together they describe slightly different companies. A buyer notices this even when they cannot name it, because the effect is a low-grade sense that the company is not sure what it does. Mapping makes the drift visible in a way that reading assets sequentially does not, because the inconsistencies sit next to each other rather than a week apart in someone's memory. The material for the map usually comes out of a working session, which [Storytelling Workshops for Your Business: How to Start](/blog/storytelling-workshops-for-your-business-how-to-start) describes.
Section 2
How to lay it out
Use two axes. Across the top, the stages of the relationship: unaware, evaluating, deciding, onboarding, renewing. Down the side, the narrative elements: who this is for, the problem, why now, what we do, the proof, the next step. Fill each cell with the actual current wording, copied verbatim rather than paraphrased. Paraphrasing is where the map starts lying, because the person filling it in unconsciously harmonises what they find. The empty cells are as informative as the full ones. Most maps reveal that proof is thin at the deciding stage and that nothing at all addresses why now.
Section 3
The spine that holds the map together
One sentence sits above everything: who it is for, what changes for them, and why this company is credible at it. Every cell should be a consistent expression of that sentence at a different level of detail. Where the founding account is the natural anchor, [How to Find Your Startup's Origin Story](/blog/how-to-find-your-startup-s-origin-story) is a good place to start.
Section 4
Building the first version in a week
Do it in a spreadsheet before considering any dedicated tool. Two people, four hours of collection, one session to arrange it. The value is in the arrangement, not the rendering, and an attractive map built in a design tool is harder to update, which means it will be accurate once. Then prioritise. You will find more inconsistencies than you can fix. Rank by traffic and by revenue proximity: the first two minutes of the sales call and the homepage above the fold usually outrank everything else. Fix two cells, watch what happens to the questions buyers ask, then move to the next two. Rewriting the whole map at once produces consistency and no information about which change mattered.
Section 5
Keeping it from becoming shelfware
Maps decay. Assign an owner and a quarterly review, and tie the review to something that already happens, such as the quarterly planning cycle, so it does not depend on someone remembering. Two other traps. The first is mapping the intended story rather than the live one, which produces a document that describes a company you would like to be and diagnoses nothing. The second is treating the map as an approval gate, at which point teams route around it. It is a diagnostic instrument, not a control mechanism. The distinction between a tool that describes work and a tool that governs it comes up elsewhere too, as [Robotic Process Automation (RPA) vs. AI Automation: What’s the Difference?](/blog/robotic-process-automation-rpa-vs-ai-automation-whats-the-difference) explores.