What is CardBoard
CardBoard is a visual planning surface for product teams who think upstream of their tracker. You work on boards made of cards; you pick a map type that matches the conversation; you collaborate with your team in real time; and you sync with Azure DevOps or Jira when execution starts.
What it’s for
Section titled “What it’s for”Story mapping, sitemaps, journeys, kanbans, retros, opportunity solution trees — the kinds of conversations that don’t fit in a backlog. Teams use CardBoard for the thinking part of product work. The tracker is where execution happens.
What it’s not
Section titled “What it’s not”CardBoard is not a tracker. It doesn’t manage sprints, backlogs, capacity, or release pipelines. If you need those, your tracker (Jira, ADO) does them well — CardBoard sits upstream and feeds them.
It’s also not a whiteboard for everything. The map type matters; pick the type that matches your conversation, and the canvas gives you the right structure for it.
The primitives, in one breath
Section titled “The primitives, in one breath”| Primitive | What it is |
|---|---|
| Card | The unit you write on, move, and link |
| Board | The named, shareable container |
| Map type | The kind of canvas (story map, sitemap, kanban…) |
| Outcome | A named group of cards |
| Tracker | The connection to ADO or Jira |
Ready? Create your first map →