A Figma customer journey map is usually the polished version: the one a designer builds for the leadership offsite, the investor pack or a client pitch. It looks finished, so people trust it. This article answers one specific question: how do you keep a designed journey map in a design tool honest, by tying every panel to a pipeline stage in the levelpartner.ai platform and refreshing its figures from a dashboard each month, so the good-looking map is also the accurate one.
Why the designed map is the one that misleads
A rough whiteboard map announces that it is a draft. A designed map does the opposite. Clean typography and consistent icons make a guess look like research, and once it sits in a board pack, nobody questions it.
The risk is specific. The design file records how the business believed buyers behaved on the day it was drawn. Six months later the sales process has changed, a new lead source has appeared and one stage has quietly become the bottleneck. The file still shows the old story, beautifully.
The fix is a shared naming system between the design file and the CRM, plus a short monthly routine that copies live figures onto the map. You keep the design team's work and add evidence to it.
Before you start
- A finished journey map in your design tool, with one panel or column per stage.
- A pipeline in Opportunities that the sales team already updates, or the agreement to build one.
- Access to Dashboard, Opportunities and Automation in your account.
- One named owner for the map. In most firms of this size, the marketing lead.
- A short list of the figures you want printed on each panel, agreed before anyone opens the file.
Decide what each panel shows
Each panel on the map should carry three things: the stage name, the event that proves a buyer reached it, and one or two live figures. Good figures are the number of contacts who entered the stage last month and the number of open deals still waiting there. Avoid putting a conversion rate on every panel. Rates between panels are easier to read as small labels on the connecting arrows.
Keep the emotional layer if the designer has added one. Buyer quotes, worries and questions are useful context for copywriters and salespeople. They simply do not get a matching record in the platform, because nothing you can measure proves a feeling.
How to set it up
- List every panel on the design file in order, left to right.
- Give each panel a short stage name that sales already uses.
- Write the proving event under each name, such as a form submission or a booked call.
- In Opportunities > Pipelines, set Stage Names to match the panels exactly.
- Create a tag for any panel that happens before an opportunity exists.
- Add a workflow step that applies each tag or moves each stage when its proving event fires.
- Go to Dashboard and click + Add Dashboard, named after the map.
- Add a Funnel widget showing entries per stage last month.
- Add a Stages Distribution widget for deals waiting in each stage.
- Use the Funnel's next-step conversion for the arrows between panels.
- Ask the designer to add a small figures area to each panel with a dated label.
- Copy the figures from the dashboard into the design file on the first working day of each month.
What this replaces in a company of 10 to 250 people
In a 60-person firm with flat revenue, the designed map tends to be the version leadership quotes and the pipeline is the version sales actually lives in. When the two disagree, the meeting argues about whose picture is right. A shared stage vocabulary ends that argument, because both pictures now count the same things.
It also replaces the annual redesign. Instead of commissioning a fresh map every year, the design file stays current with a 20-minute monthly update and a structural review only when a stage changes.
Say the design file shows six panels: enquiry, fact-find booked, fact-find held, application submitted, offer issued, completion. A first monthly refresh might print 210 enquiries, 96 fact-finds booked, 71 held, 38 applications, 30 offers and 24 completions. On those numbers the arrow from fact-find held to application, where 71 becomes 38, would be the weakest link, and the board should ask about that step before approving more spend on enquiries.
How much time it takes
The first pass takes a day across two people. The operations or sales lead spends half a day aligning stage names and building the dashboard. The designer spends a few hours adding the figures area to every panel. After that, the monthly refresh takes about 20 minutes, and a quarterly check that the panel list still matches the pipeline takes another half hour.
The mistake most people make
Letting the designer name the stages. Design teams pick elegant labels like "Discover" and "Engage". Salespeople say "enquiry" and "proposal sent". If the panel names and the pipeline names differ, the monthly copy becomes a translation exercise, mistakes creep in, and within a quarter nobody trusts the figures. Use the sales team's words on the map, even when they look plainer.
When not to use this approach
Skip the live figures if the map is a one-off concept for a service you have not launched. There is nothing to count yet. It is also overkill if your pipeline is updated only now and then, because the panels would show confident numbers built on incomplete records. Get the pipeline used consistently first, then wire the map to it.
If the map is for internal decision-making rather than presentation, you may not need a design tool at all. A dashboard built for customer journey visualization gives the same picture and updates itself.
Troubleshooting
The panel figures never add up from one stage to the next. Some opportunities are being created directly at later stages. Check who creates deals by hand and agree a single entry point, then read the customer journey stages guide for how to define each stage boundary.
The design file and the pipeline drift apart again. A stage was added in the platform without telling the map owner. Make the map owner the only person who can approve pipeline stage changes.
Pre-opportunity panels show zero. The tag is applied by a workflow that is not published or is listening to the wrong form. Submit a test enquiry and watch the contact record for the tag.
Leadership questions where the panel figures come from. Add a single line of small text to the file naming the dashboard and the date range. Trust follows a visible source.
Frequently asked questions
Can I embed live figures directly in the design file?
Treat the design file as a static document that you refresh by hand. The live version is the dashboard. Linking the two by name and date is more reliable than trying to make a design file behave like a report.
Should every touchpoint appear on the designed map?
No. Put stages on the map and list touchpoints underneath each one as supporting detail. The touchpoints guide explains how to record which touchpoints a buyer actually hit.
How often should the design itself change?
Only when the sales process changes. Monthly updates are figures only. If a stage is added, removed or merged, update the pipeline first and the panel second.
Who should own the map once figures are on it?
Whoever owns the pipeline stages, usually the sales or marketing lead. Ownership of the design and ownership of the numbers should sit with the same person, or the two will drift. For tracking individual contacts through the stages, see customer journey tracking.