The workshop ends. The story map keeps going.
CardBoard is a user story mapping tool for teams that want the map from a Mural workshop to stay current afterward. In Mural a story map is a template, and changes reach Jira, Azure DevOps, or Linear when someone clicks Sync, with the tracker winning any conflict. CardBoard makes the story map a structured map type and syncs linked fields both ways as they change, with Jira, Azure DevOps, Linear, Shortcut, and Trello. Mural is the better pick when facilitation is the job and the map is one exercise in the session.
Mural is built for the session. CardBoard is built for the months after.
Mural is one of the best tools for running a workshop. Timers, voting, private mode, and a facilitator who can pull everyone to the same spot all come on the free plan. A story mapping session run in Mural usually goes well.
Then the stories go to Jira, sprints start, and the map has to keep up. That's where a template and a sync button start to cost time. CardBoard was built in 2012 by David Hussman alongside Jeff Patton for exactly that stretch: a map the team keeps planning from after the stickies come down.
CardBoard vs Mural for story mapping.
| CardBoard | Mural | |
|---|---|---|
| The story map | ||
| Story map | A structured map type: backbone, stories beneath, release slices across | A user story mapping template on the canvas |
| Inserting a step | Insert a column and everything to the right shifts over | Grid areas snap stickies and grow as you add them |
| Grouping | Name a set of cards anywhere on the map. Nothing moves. | Areas, which hold whatever sits inside them |
| From Mermaid | A Mermaid journey becomes a story map | Not documented |
| Tracker sync | ||
| Direction | Both ways, as edits happen | Both ways. Mural edits reach the tracker when someone clicks Sync. |
| Conflicts | The latest edit wins, and stale edits are rejected | The tracker overwrites Mural |
| Trackers | Jira, Azure DevOps, Linear, Shortcut, Trello | Jira, Azure DevOps, Linear |
| Moving a card | Never changes the tracker | Never changes the tracker |
| AI agents | ||
| MCP server | Every plan | Public preview on paid plans. One mural at a time, and it must stay open in a browser tab. |
| Agent edits | Arrive as proposals a member accepts | Written directly, labeled as AI, and undoable |
| People and plans | ||
| Free plan | Three boards | Three editable murals |
| People outside the team | Guests are free on every plan and can edit | Visitors are free and can edit from Team+. Guests are Business and up. |
| Version history | Activity feed. No restore. | None. Activity log, object recovery, and duplicating murals. |
| Facilitation | Reactions and follow a teammate. No timer or voting. | Timer, voting, private mode, summon, and facilitator lock on every plan |
Mural facts from its own site and help center, checked September 28, 2026: Story map template, Jira integration, Azure DevOps integration, Linear integration, Areas, MCP preview, Collaborator types, Facilitation, Canvas FAQ, Pricing. CardBoard facts from our docs and pricing.
What changes after the workshop.
The map keeps up without a sync button
In Mural, a change on the canvas waits until someone clicks Sync, and when the tracker and the mural disagree, the tracker wins. That's safe for a one-off workshop. For a map you plan from every week, it means someone has to remember. CardBoard sends each edit to Jira or Azure DevOps as it happens, and brings tracker changes back within seconds.
A map, not a picture of one
Mural's story map is a template: stickies in areas, arranged by the person holding the mouse. CardBoard knows which cards are the backbone, which stories sit under each step, and which release slice each one is in. That's what lets you insert a step without moving everything by hand, and what lets an agent read the map correctly.
Agents that work while the tab is closed
Mural's MCP server is in preview, works on one mural at a time, and needs that mural open in a browser tab. CardBoard's MCP server is on every plan and works on any map you can access. Agent changes arrive as proposals, so nothing lands on the team's plan until a member accepts it.
Tracker detail: story mapping with Jira and story mapping with Azure DevOps.
Stay with Mural if:
- Facilitation is the job: timers, voting, private mode, and summoning the room are on every Mural plan. CardBoard has reactions and follow-a-teammate, and no timer.
- Your sessions run to hundreds of people. Mural switches to crowd mode at 500 and supports up to 1,000.
- You use LUMA methods or pick from hundreds of workshop templates.
- Your enterprise needs SCIM, bring-your-own-key encryption, or data residency.
- You export to PowerPoint or HTML.
Frequently asked questions
- Can you do user story mapping in Mural?
- Yes. Mural has a user story mapping template based on Jeff Patton's method, and grid areas keep stickies aligned. It suits a workshop. Keeping it current afterward is manual, because tracker sync runs when someone clicks Sync and the tracker wins conflicts.
- Does Mural sync with Jira both ways?
- Yes, with a manual step. Changes made in Mural reach Jira when someone clicks Sync on the card or syncs in bulk, and if both sides changed, Jira's version wins. CardBoard sends each edit as it happens and receives Jira changes within seconds.
- Can I run a workshop in Mural and keep the map in CardBoard?
- Yes, and some teams do. Run the session in Mural, then rebuild the backbone in CardBoard or paste it as a Mermaid journey. If the stories are already in Jira or Azure DevOps, connect the board to the same project and import them.
- What does CardBoard cost next to Mural?
- Both have a free plan with three boards. CardBoard's tracker sync starts on Pro at $10 a month billed annually, and guests are free on every plan. Mural's Team+ is $9.99 per member a month billed annually.
Comparing more tools? See the best user story mapping tools or CardBoard vs Miro.
Take the map home from the workshop.
Start a CardBoard map free, invite everyone who was in the room, and connect your tracker from $10 a month.