The Visual Launch Board (2026): Mapping the Customer Journey Before You Launch

Article Metadata

By Justkay, Documentary Filmmaker and Founder of Storyflow Published September 2, 2026 · 15 min read · Product Launch

Breadcrumb

Home > Blog > Product Launch > Visual Launch Board and Customer Journey 2026

Table of Contents

1. What a Visual Launch Board Is
2. The Four Rows
3. The Nine Journey Steps Most Launches Miss Three Of
4. Building the Board in Ninety Minutes
5. The Kanban Question
6. 8 Tools for a Visual Launch Board
7. How We Evaluated These Tools
8. Tool Reviews
9. Keeping the Board Alive After the Workshop
10. FAQ: Visual Launch Boards and Customer Journeys
11. The Bottom Line
12. Author
13. Related Reading

Key Takeaways

• Draw the customer journey before the asset list. Assets should be a consequence of steps, not a wish list.
• Four rows on one canvas: journey step, asset, owner and date, proof metric. A step with no asset is the finding.
• The step everyone skips is the first ten minutes inside the product, which is where launch traffic is actually lost.
• A workshop board and a living board are different jobs. Most teams use a workshop tool for both and the board is stale in a fortnight.
• The board is not a tracker. Keep owners and dates in a checklist tool and link the two.

What a Visual Launch Board Is

A visual launch board is a single canvas where the customer's path through your launch is laid out left to right, and everything the launch produces is attached to the step it serves.

That is a small idea with a large consequence. Most launch planning starts from the outputs: we need a landing page, an email, a demo video, three social posts. That list is generated by memory of previous launches and by what the team enjoys making, and it is never checked against what a person actually does. So it reliably contains four assets for the awareness step, one for consideration, and nothing at all for the moment a new user is staring at an empty product.

Starting from the journey inverts it. You draw what a stranger does, in order, and then ask what serves each step. Gaps present themselves. So do redundancies: three social posts all serving the same step while two steps have nothing.

The board is not a project tracker and should not try to be. It has no due-date rollups, no dependencies and no burndown. Its entire job is to be looked at, by someone who was not in the meeting, and to make an absence obvious.

The Four Rows

Time runs left to right. Four rows run down.

Row 1: The journey step. What the person is doing, phrased from their side. Not "send launch email" but "reads an email from a product they signed up for four months ago". The phrasing matters more than it sounds; writing it from their side is what surfaces how little context they have.

Row 2: The asset. What we make that serves this step. Sometimes nothing, and the empty cell is the most valuable thing on the board.

Row 3: Owner and date. A name and a day. Kept short here, because the real version lives in the checklist.

Row 4: The proof. The one number that tells you this step worked. Not a vanity number for the whole launch, one number for this step. If you cannot name a number for a step, that is worth knowing before you build an asset for it.

Row 4 is the one teams skip and the one that changes behaviour. A launch measured only at the top ("we got 4,000 visitors") cannot tell you which step leaked. A launch with a number per step can, and the answer is usually a step nobody built anything for.

The Nine Journey Steps Most Launches Miss Three Of

Every launch is different and this is a starting frame, not a template to follow literally. Nine steps, and in the three launches behind this article the same three were missing every time.

1. Hears about it. Email, post, community, word of mouth. Everyone builds for this one.
2. Decides whether it is for them. The landing page's actual job, and where most landing pages talk about the product instead of the reader.
3. Understands what it does. Demo, screenshots, a short video. Usually built.
4. Compares it to what they do now. Almost never built. The reader is silently comparing you to a spreadsheet and you are not in the room for it.
5. Checks the price and what happens after. Pricing page. Built, but rarely answering what happens to existing work or at the end of a trial.
6. Signs up. Built, and usually the most tested path.
7. Opens the product for the first time. Almost never built. The empty state, the first action, the first moment of value. Launch traffic dies here in volume, and no asset in the plan addresses it.
8. Gets to the first real outcome. Sometimes built as onboarding. Rarely measured separately from signup.
9. Comes back a second time. Almost never built. Nothing in the launch plan reaches day two, so the launch is measured as a traffic event.

Steps 4, 7 and 9. Comparison, first run, and return. Every launch produces a beautiful step 2 and nothing for 7, and then the team reads a low activation rate as a marketing problem.

The line worth remembering: a launch that ends at signup is measuring the least interesting half of the journey.

Building the Board in Ninety Minutes

This is the session, and it fits in one sitting with three or four people.

Minutes 0 to 15. One sentence. Write down who this is for and what changes for them. Everyone writes it separately first, then compare. If the three versions disagree, stop and fix that; nothing downstream is worth doing until they agree.

Minutes 15 to 40. The journey, from their side. Sticky per step, phrased as what the person does, left to right. Do not attach anything yet. Push past signup: force at least three steps after it, because the natural instinct is to stop there.

Minutes 40 to 55. Attach what already exists. Existing pages, docs, emails, screenshots. Only things that exist today. The board will look sparse and that is the point.

Minutes 55 to 70. Mark the gaps. Any step with nothing under it. Then argue about which gaps matter, because some genuinely do not.

Minutes 70 to 85. One number per step. What tells you this step worked. Some will be uncomfortable to name, which is a finding.

Minutes 85 to 90. Assign the gaps you decided matter. A name and a date each, and those go into the checklist afterwards, not onto the board.

What comes out is an asset list that is a consequence of the journey rather than a memory of the last launch, and it is usually shorter than the wish list and pointed at different steps.

The Kanban Question

Teams ask whether the launch board should be a kanban. The honest answer is that they are different objects and doing both on one surface produces a bad version of each.

A kanban's axis is state: to do, doing, done. A launch board's axis is the customer's time: what they do first, second, third. Those two axes are not compatible on one canvas. A card cannot be both "in the consideration step" and "in progress" without one of the two meanings being decoration.

What works in practice is both, in two places:

• The journey board stays on a canvas, arranged by the customer's sequence, and it is a weekly artifact.
• The kanban lives in Notion, Linear or Trello, arranged by state, and it is a daily artifact.
• Each kanban card names the journey step it serves. One field, and it keeps the two agreeing.

That single field is worth more than any integration. It means that when a card is cut, you can see which journey step just lost its only asset.

8 Tools for a Visual Launch Board

Prices are publicly listed plans as of early 2026 and change often. Ratings weigh journey mapping quality, whether the board survives past the workshop, cost for three to eight people, and how well the board hands off to a checklist.

How We Evaluated These Tools

Four criteria:

1. Journey mapping quality. Can you lay out steps against time with four rows and keep it readable at a glance on a laptop?
2. Whether it stays current. Measured by opening each board three weeks after the session and checking whether it still described reality. This is where most canvas tools lose points, and it is not a feature problem.
3. Cost at three to eight people, including the contractor you did not plan for. Per-editor pricing changes the answer.
4. Handoff to a checklist. How much work to get from "this gap matters" to "this is a dated, owned item somewhere that nags people".

Testing covered three launches: a feature launch, a standalone product launch, and a rebrand.

Tool Reviews

1. Storyflow

Storyflow is our product. It ranks first here on a narrow claim: keeping the launch board alive after the session, which is the criterion every other canvas tool in this list scores badly on. The reason is not virtue, it is that the board holds the reasoning next to the layout. The positioning, the journey, the asset list and the notes about why a step was cut sit on the same canvas, and the AI reads the whole current board before it answers, so asking what the journey is missing after signup produces an answer about your launch rather than a generic list.

It is not the best tool for the ninety-minute session itself. Miro's facilitation set (timer, voting, private mode) is genuinely better for getting four people to converge in a room, and this article recommends running the session there if that is how your team works.

Storyflow is paid-only during early access; its Free plan launches before the end of 2026, and anyone a paid member invites to a board joins free now.

Key features: AI that reads the whole current board plus up to one Tactic and three documents you mention, story blueprints, brief-to-board generation, unlimited shared boards, flat per-account pricing.

Pricing: Plus $7.99 per month billed annually ($9.99 monthly); Pro $14; Max $39.

Pros: the board and the reasoning stay together, which is why it survives the fortnight; flat pricing so contractors cost nothing extra; invited collaborators join free.

Cons: no facilitation tools (no timer, no voting, no private mode), so it is the wrong tool for a live workshop; no dependencies or due-date rollups, so it cannot be the checklist.

2. Miro

The best ninety minutes you will spend on a launch. The facilitation set is unmatched: private mode stops the first speaker anchoring everyone, voting resolves the "which gaps matter" argument in four minutes, and the timer keeps a journey-mapping session from becoming a two-hour positioning debate.

Its weakness is the one this whole category shares and Miro has it worst, because its boards accumulate. Three weeks after the session the board is a snapshot of a meeting rather than a description of the launch, and the free tier's three-board limit means the previous launch's board is in the way.

Key features: infinite canvas, journey-map templates, private mode, voting, timer, facilitation tools.

Pricing: Free for 3 boards; Starter $8 per member per month billed annually; Business $16.

Pros: the best live session tool by a distance; excellent journey-map templates.

Cons: goes stale fast; three-board free limit bites immediately; per-member pricing.

3. FigJam

The value pick. At $3 per editor it is the cheapest way to put eight people on a canvas, and for journey mapping specifically it does nearly everything Miro does. If the team already pays for Figma, this is free-adjacent and there is no reason to buy something else for the session.

Where it is behind is facilitation depth and the same staleness problem. It is a whiteboard, and whiteboards describe meetings.

Key features: infinite canvas, stickies, sections, templates, Figma integration, cheap seats.

Pricing: Free for up to 3 files; Collab $3 per editor per month billed annually.

Pros: the price is the story; excellent if design already lives in Figma; genuinely capable canvas.

Cons: shallower facilitation than Miro; goes stale; the free tier's file limit arrives quickly.

4. Milanote

Milanote's boards are the calmest to read of anything here, and for a launch board that is meant to be looked at rather than worked in, that matters. It handles the journey row and the asset row well, and it is pleasant enough that people open it voluntarily, which is a real advantage.

It is weaker at the wide left-to-right layouts a nine-step journey needs, and it has no facilitation tools.

Key features: visual boards, columns, note cards, image handling, clean export.

Pricing: Free for 100 items; Pro $9.99 per month.

Pros: the most readable board; good image handling for asset rows; simple pricing.

Cons: cramped on very wide journeys; no facilitation; the free tier's item cap is low for a launch.

5. Mural

Miro's closest competitor and better than Miro at facilitating a large group. If your launch session has ten or more people, or you have a facilitator who knows the craft, Mural's structure is genuinely better. For a team of four it is more apparatus than the work needs.

Key features: facilitation superpowers, private mode, voting, timers, templates.

Pricing: Free for 3 murals; Starter $9.99 per member per month billed annually.

Pros: the strongest facilitation at size; excellent structured templates.

Cons: heavier than a small session needs; same staleness problem; per-member cost.

6. Notion

Notion is on this list to be recommended for the other half. It is a poor canvas and the journey board will be worse there than anywhere else in this list. It is the best home for what the board produces: gaps turned into owned, dated checklist items, with the copy beside them.

Key features: databases, filtered views, docs alongside data, templates.

Pricing: Free for personal use; Plus $10 per user per month billed annually.

Pros: the best destination for the board's output; the launch copy lives beside the checklist.

Cons: genuinely bad as a journey canvas; per-seat pricing.

7. Whimsical

Fast and tidy, and if your journey is closer to a flow diagram than a four-row board, Whimsical draws it more cleanly than anything else here. It is more constrained than an infinite canvas, which is sometimes exactly right and sometimes a wall.

Key features: flowcharts, wireframes, sticky notes, fast keyboard-driven drawing.

Pricing: Free for 3 boards; Pro $10 per editor per month.

Pros: the fastest tool here for a clean diagram; opinionated in a good way.

Cons: constrained for four-row boards with assets attached; three-board free limit.

8. Figma

Right answer only if a designer owns the launch board and will maintain it. A journey map in Figma can be beautiful and precise, and it will be edited by exactly one person, which for a cross-functional launch is usually the wrong shape.

Key features: precise layout, components, prototyping, design system access.

Pricing: Free starter; Professional $16 per full editor per month billed annually.

Pros: the most precise output; already there if design leads the launch.

Cons: the highest editor cost here; non-designers will not edit it; wrong tool for a group session.

Keeping the Board Alive After the Workshop

Every canvas tool in this list goes stale by default. Three things stop it, and none of them is a feature:

Give the board an owner, by name. Not the team. One person, whose weekly job is twenty minutes updating it.

Put the reasoning on the board, not in the meeting. A board with only nouns on it is unreadable in a fortnight because the arguments that produced it are gone. A short note next to a cut step ("no asset here, we decided comparison is handled by the pricing FAQ") is what makes the board survive its authors' memory.

Update it weekly, at a fixed time, and report one sentence. What changed shape. Not what got done.

The staleness problem is why this article ranks a living-board tool above the best workshop tool, and it is worth being honest that the ranking would flip if the only question were which is better in the room.

The Bottom Line

Draw the journey before the asset list. Four rows, one canvas, phrased from the customer's side, and push past signup to at least three steps after it. The empty cells are the finding. Run the session wherever your team facilitates best, keep the board somewhere the reasoning stays attached to the layout, put the gaps that matter into a checklist tool with owners and dates, and give one person twenty minutes a week to keep the picture true.

Author

Justkay is a documentary filmmaker and the founder of Storyflow. The nine-step journey in this article comes from running three launches and finding the same three steps missing every time.