# CardBoard

> CardBoard is a user story mapping tool teams use to build better products — a visual canvas for mapping the user's journey, slicing releases, and keeping specs in sync with the work.

CardBoard maps content is authored as markdown with typed frontmatter (the canonical source); every rendered page is a projection of it. The links below point to the highest-signal pages for understanding the product, the practice of user story mapping, and how to use the app.

## Core pages

- [CardBoard](https://cardboardit.com/): Product overview and homepage.
- [Pricing](https://cardboardit.com/pricing/): Plans and pricing — capacity-based (boards + author seats).
- [About](https://cardboardit.com/about/): What CardBoard is and the team behind it.
- [User Story Mapping Tool](https://cardboardit.com/user-story-mapping-tool/): CardBoard as a dedicated user story mapping tool.
- [Best User Story Mapping Tools](https://cardboardit.com/best-user-story-mapping-tools/): Comparison of user story mapping tools.
- [Jira Story Mapping](https://cardboardit.com/jira-story-mapping/): User story mapping synced with Jira: which fields sync, what stays on the map.
- [Azure DevOps Story Mapping](https://cardboardit.com/azure-devops-story-mapping/): User story mapping synced with Azure DevOps: six fields two-way, position stays on the map.
- [Linear Story Map](https://cardboardit.com/linear-story-mapping/): User story mapping synced with Linear: title, description, status, and sub-issues both ways.
- [StoriesOnBoard Alternative](https://cardboardit.com/storiesonboard-alternative/): CardBoard vs StoriesOnBoard: tracker sync, layout, guests, AI agents, pricing.
- [SpecMap Alternative](https://cardboardit.com/specmap-alternative/): What happened to the SpecMap extension for Azure DevOps, and how to rebuild the map with two-way sync.
- [Easy Agile Alternative](https://cardboardit.com/easy-agile-alternative/): CardBoard vs Easy Agile TeamRhythm for story mapping with Jira.
- [Miro Alternative for Story Mapping](https://cardboardit.com/miro-alternative/): CardBoard vs Miro's User Story Map widget: grouping, guests, trackers, agents.
- [FigJam Alternative for Story Mapping](https://cardboardit.com/figjam-alternative/): CardBoard vs FigJam templates for story mapping and tracker sync.
- [Mural Alternative for Story Mapping](https://cardboardit.com/mural-alternative/): CardBoard vs Mural for story mapping and workshop-to-backlog sync.
- [Spec Mapping](https://cardboardit.com/spec-mapping/): Spec mapping — turning a story map into buildable specs.
- [Theory of Maps](https://cardboardit.com/theory-of-maps/): The thinking behind CardBoard's map types and traits.
- [For Agents](https://cardboardit.com/for-agents/): How AI agents work with CardBoard maps via MCP.
- [Changelog](https://cardboardit.com/changelog/): Release notes, newest first.

## Guides

- [User Story Mapping: The Complete Guide (2026)](https://cardboardit.com/user-story-mapping-guide/): User story mapping arranges a product's work along the user's journey — a backbone of activities, stories and tasks beneath it, release slices across it. What it is, how to run one, and how maps stay alive for teams and AI agents.
- [OKRs and User Story Maps: The Complete Guide](https://cardboardit.com/guides/okrs-and-user-story-maps/): OKRs set the objective and the measures. Story maps turn them into work you can see. What OKRs are, how to write ones that survive contact, and how to connect them to the map your team already builds from.
- [How to Make Diagrams with AI: A Guide to Mermaid](https://cardboardit.com/guides/how-to-make-diagrams-with-ai/): Your AI can already draw. What kinds of diagrams you can ask for, how to get a draft worth keeping, what it costs to keep it — and the point where a picture stops being enough.
- [Spec-Driven Development: The Complete Guide](https://cardboardit.com/guides/spec-driven-development/): What spec-driven development is, where it came from, what a spec has to carry, and why the specs agents build from keep getting longer. How to slice a spec so an agent builds the first release instead of the whole thing.
- [How to Turn a Mermaid Journey Into a Story Map](https://cardboardit.com/guides/mermaid-journey-to-story-map/): Paste a Mermaid user journey into CardBoard and it becomes a user story map. Sections become activities, tasks become cards beneath them, and the scores tell you where to cut the first release.
- [PRD Template for AI Coding Agents](https://cardboardit.com/guides/prd-template-for-ai-coding-agents/): A copy-paste PRD template for Claude Code, Cursor, and other coding agents: what each section is for, how to use it across sessions, and what to do when the PRD gets too long for the agent to read.
- [AI Process Mapping With Mermaid: As-Is to To-Be](https://cardboardit.com/guides/ai-process-mapping-with-mermaid/): How business analysts use ChatGPT or Claude to draft an as-is process map in Mermaid, check it against the people who do the work, and turn it into an editable map for designing the to-be.
- [How Do I Get My Team and Our AI Agents Working From the Same Plan?](https://cardboardit.com/guides/team-and-ai-agents-same-plan/): Everyone's getting good at working with their own AI. The hard part is sharing what comes out of it. Put the work on one map your team can read at a glance, let every agent read it and propose onto it, and stop pasting each other essays from your chats.

## Documentation

- [Docs home](https://cardboardit.com/docs/): Product documentation index.
- [Get started](https://cardboardit.com/docs/get-started/): Create your first map, invite your team, connect a tracker.
- [Concepts](https://cardboardit.com/docs/concepts/): Cards, boards, map types, map traits, outcomes, connections, and more.
- [How-tos](https://cardboardit.com/docs/workflows/): Working with your team, workspaces, and trackers.
- [Integrations](https://cardboardit.com/docs/integrations/): Jira, Azure DevOps, and tracker sync.
- [Reference](https://cardboardit.com/docs/reference/): API, permissions, plan limits, keyboard shortcuts, security.

## Blog

- [Dark mode for whiteboards is harder than it looks](https://cardboardit.com/blog/dark-mode/): CardBoard now has dark mode across the whole app, with a light, medium, dark, or chalkboard background on every board. Miro's most-voted request has been open since 2020, and FigJam's since 2021.
- [Spec-driven development is for machines. Story maps are for us.](https://cardboardit.com/blog/text-is-for-machines-maps-are-for-us/): AI agents made spec-driven development pay off, and made specs too long for people to review. What one story map caught that the spec never would.
- [We rebuilt our sticky note colors like a pack of Post-its](https://cardboardit.com/blog/rebuilding-the-card-palette/): Our toolbar felt disjointed, so I had Claude critique it as David Hussman. The fix: fewer sticky note colors on the toolbar, more in the drawer.
- [How to facilitate a user story mapping session](https://cardboardit.com/blog/the-art-of-facilitating-user-story-mapping-sessions/): How to facilitate a user story mapping session, from who to invite to slicing the first release, and how to end the session with actual decisions.
- [What is Scrum? A product owner's guide to the framework](https://cardboardit.com/blog/why-scrum-a-product-owners-guide-to-agile-success/): What is Scrum? It began in a 1986 HBR article about cars and copiers. Its accountabilities, events, artifacts, and what it asks of a product owner.
- [Kanban vs Scrum: how Kanban fits with agile](https://cardboardit.com/blog/kanban-agile-scrum-or-both-unraveling-the-mystery/): Kanban vs Scrum, and where Agile fits. How a Toyota idea borrowed from supermarkets became the Kanban Method, its six practices, and when to run both.
- [Monte Carlo forecasting for software project estimation](https://cardboardit.com/blog/project-estimation-with-monte-carlo-analysis/): Monte Carlo project estimation replays your backlog 10,000 times to forecast a finish date with odds. The method, a worked example, and its limits.
- [Agile sprints: how to run one without burning out your team](https://cardboardit.com/blog/mastering-sprints-your-guide-to-building-products-without-destroying-your-team/): What an agile sprint is, how to run one from planning to retro, and why the Scrum Guide swapped "commit" for "forecast" in 2011 to protect teams.
- [What product operations (product ops) actually does](https://cardboardit.com/blog/product-operations-a-comprehensive-guide/): What product operations is, the three pillars of product ops, what a product ops manager does all day, and when your team needs one.
- [What is agile? The Manifesto's 4 values and 12 principles](https://cardboardit.com/blog/agile-uncovered-understanding-what-agile-really-means/): What is Agile? In 2001, seventeen people at a Utah ski lodge wrote 68 words. The four values, the twelve principles, and what teams still misread.
- [How to pick the product metrics that matter](https://cardboardit.com/blog/winning-with-product-metrics/): Product metrics that change decisions: AARRR pirate metrics, product vs. growth metrics, examples by stage, and how to choose one to move.
- [The difference between a product backlog and a user story](https://cardboardit.com/blog/understanding-agile-the-difference-between-a-product-backlog-and-a-user-story/): Product backlog vs user story: one is the ordered list, the other is a single item that might be on it. And what a story loses on the way in.
- [Product Backlog Management With a User Story Map](https://cardboardit.com/blog/mastering-product-backlog-management-a-user-story-mapping-approach/): A backlog is a to-do list, and to-do lists forget. How to get a backlog into a user story map, organize it, and manage it there without the two drifting apart.
- [Customer discovery lessons from Airbnb and The Mom Test](https://cardboardit.com/blog/the-ultimate-guide-to-customer-discovery-lessons-from-airbnb-steve-blank-and-the-mom-test/): How to do customer discovery: Airbnb's $400 week, Steve Blank's four steps, The Mom Test's interview rules, and where your notes go after.
- [How to write agile user stories, with examples](https://cardboardit.com/blog/agile-user-stories-made-simple-a-step-by-step-guide-with-cardboard/): How to write agile user stories: the template, the 3 C's, INVEST, acceptance criteria, worked examples, and why a story lands better on a map than in a list.
- [The Hooked model, applied to release slices](https://cardboardit.com/blog/get-users-hooked-by-applying-the-hooked-model-to-release-slices/): Use the Hooked model (trigger, action, variable reward, investment) to plan release slices on a story map, so your first release closes the loop.
- [When will it be done? Software estimation for product managers](https://cardboardit.com/blog/when-will-it-be-done-unpacking-estimation-strategies-for-product-managers/): Software estimation for product managers. Why single dates fail, what points and counts are for, and how a story map turns estimates into learning.
- [Feature bloat is the biggest mistake in building apps](https://cardboardit.com/blog/one-of-the-biggest-mistake-teams-make-when-building-apps/): Feature bloat starts when teams build past the first place a user can succeed. How to spot it, and how a user story map shows where that line sits.
- [A product roadmap template that doesn't promise dates](https://cardboardit.com/blog/online-whiteboard-road-map-template/): A product roadmap template built on horizons, not dates: four focus areas, 3 to 12 months out, and five steps to fill it in on an online whiteboard.
- [How to choose an online whiteboard (and how to leave one)](https://cardboardit.com/blog/how-to-choose-an-online-whiteboard-thats-right-for-you/): Bending Spoons is buying Miro. Five questions for choosing an online whiteboard, starting with the one Miro users are asking now: how would I leave?
- [5 benefits of an online whiteboard over the one on the wall](https://cardboardit.com/blog/5-ways-your-team-can-benefit-from-an-online-whiteboard/): Every office has a whiteboard that says DO NOT ERASE. Five benefits of an online whiteboard, and what each one fixes about the one on the wall.
- [How to make a network diagram in under two hours](https://cardboardit.com/blog/network-diagramming-cardboard-digital-whiteboard/): What a network diagram is, what it's for, and how to make one step by step, with tips from an IT admin who drew one in under two hours.
- [How to run a 4Ls retrospective, step by step](https://cardboardit.com/blog/how-to-hold-4ls-retrospective/): The 4Ls retrospective asks what your team Liked, Learned, Lacked, and Longed for. How to run one step by step, and how to keep the action items alive.
- [How to prioritize user stories by slicing first](https://cardboardit.com/blog/how-to-prioritize-agile-stories/): How to prioritize user stories so your first release leaves someone able to do the job. Ranking by value, effort, or votes only sorts the list.
- [User story mapping in SAFe and PI Planning](https://cardboardit.com/blog/the-scaled-agile-framework-safe-and-user-story-mapping/): Where user story mapping fits in SAFe: bring a map, not a flat ART backlog, to PI Planning, and let its cut line decide what makes the interval.
- [How to make an empathy map, with a worked example](https://cardboardit.com/blog/using-empathy-maps-to-better-understand-your-customers/): An empathy map puts what a customer thinks, feels, hears, sees, says, and does on one page. How to run one with your team, plus a worked example.
- [Hate estimating? Forecast from a user story map instead](https://cardboardit.com/blog/hate-estimating-try-doing-a-user-story-map-instead/): Hate estimating? Build a user story map, count the cards, and run a Monte Carlo forecast. You get a range of dates with odds instead of a guess.
- [How to use the Opportunity Canvas for a feature idea](https://cardboardit.com/blog/solve-problems-and-create-solutions-with-opportunity-canvas-2/): The Opportunity Canvas frames one feature idea for an existing product on a single page. The ten sections, the order to fill them, and what to guess.
- [How to fill in a Business Model Canvas, block by block](https://cardboardit.com/blog/understanding-your-business-through-the-business-model-canvas/): The Business Model Canvas fits a business on one page in nine blocks. Where to start, what each block asks, and the judgment calls in between.