Cartography: The Designer's Private Preparation Stage

Journey work has a stage that most frameworks underemphasize because it is invisible: the period between the kick-off meeting and the first discovery interview, when the designer works alone to structure the map that will hold everything that follows.

This is Cartography — and it is more consequential than it looks.

What Cartography Is (and Is Not)

Cartography is not discovery. It produces no new insights. It is not a workshop or a collaborative exercise. It is the designer's private work of building the intentional structure that will make discovery productive.

Think of it as preparing the terrain before the expedition begins. When discovery starts and a colleague or customer describes a pain, that pain needs somewhere to land. When a stakeholder mentions an emerging solution, it needs a stage to be placed in. Without a prepared structure, every new input goes into an undifferentiated pile — and the effort required to make sense of that pile in the Tidying phase multiplies.

The output of Cartography is an empty but unmistakably structured map — a territory waiting to be explored, with lanes for needs, pains, gains, pressures, opportunities, and solutions already in place. Blank, but purposeful.

"Think of it like preparing the terrain before the expedition begins. Blank canvas? When discovery begins, people should see a map that is empty but unmistakably structured."

The Three Things Cartography Achieves

First, it defines the altitude. Before drawing anything, the designer must decide whether this map covers the full customer lifecycle, a major stage of it, or a sub-journey within a stage. Each choice is legitimate for different purposes. The discipline is making the choice explicitly and being prepared to justify it to stakeholders who will ask.

Second, it establishes the grammar. What counts as a stage versus a step? What is the difference between a pain and a pressure? What does an opportunity look like, and how does it differ from an emerging solution? These distinctions should be clear in the structure of the map itself, not only in the designer's head. When colleagues see the map for the first time in a discovery meeting, the structure should make these distinctions obvious.

Third, it prepares the instruments. Interview guides. Tagging conventions. Note-taking templates. Digital board setup. These are the practical tools through which discovery will be conducted. Cartography is the moment to build them — not during a live interview with a stakeholder watching.

Why This Stage Is Often Skipped

Cartography feels slow because it produces no visible output that stakeholders can see. There are no insights yet. There are no recommendations. There is only a prepared structure — which looks, to the uninitiated, like an empty spreadsheet or an unused Miro board.

This creates pressure to skip directly to discovery: to start interviewing, collecting, and building before the structure exists. The pressure is understandable. It is also counterproductive. Discovery conducted without a prepared map produces material that is harder to cluster, harder to place, and harder to transform into insights. The time saved at the Cartography stage is spent twice over in the Tidying phase.

What the Map Should Look Like Before Discovery

The minimum viable Cartography output is a digital board (Miro, FigJam, or equivalent) with:

• Lifecycle stages laid out horizontally, using AAARRR (Awareness → Acquisition → Activation → Retention → Revenue → Referral) or an agreed equivalent
• Insight lanes running vertically below the stages: Needs, Pains, Gains, Pressures, Experience Score, Opportunities, Emerging Solutions, Big Solutions
• Tagging conventions established and documented: how confidence levels will be marked, how roles will be tagged, what constitutes a validated versus assumed insight
• The first three interview slots confirmed and the interview guide ready

This is the map in its embryonic state. It will be populated, reorganized, debated, and refined across the next several weeks. But its structure — the skeleton of the experience — will remain largely stable because it was built with intention before the first insight arrived.