A theory of maps.
Most tools hand you fifty templates and call it a feature. A template is a starting picture — it doesn't know what it is, so nothing can read it, check it, or turn it into something else. We went the other way and asked a simpler question: what is a map actually made of?
Four things every map is made of.
Strip any map to its bones and it's answering four questions. Not fifty. Four.
- What a card is. Does its look — shape, color, icon — tell you its kind?
- How cards connect. Do the lines between them carry meaning, or are they just decoration?
- Where a card sits. Does position mean something — and in what frame of reference?
- How the surface is framed. Do cards share a full grid, a single line, or nothing at all?
These four aren't a list we happened to like. They fall out of two questions: are you describing the things on the map or the space they sit in — and does the meaning stand alone or only between things? Two cuts, four answers.
Derived, not chosen. That's the whole point — a map's anatomy is discoverable, like the periodic table, not invented one template at a time.
They combine into seven shapes.
Take those four traits, and only so many combinations actually hold together. Seven. Every map you've ever drawn — a story map, a kanban, a business model canvas, a mind map — is one of them wearing different labels.
Here's the test that tells two shapes apart: move a card halfway between two others — does that mean something new? If yes, position is a coordinate and you're plotting. If no, position is membership and you're bucketing. Six of the seven bucket. One plots.
- The lane grid — story maps, swimlane kanban
- The column — kanban, retros
- The zoned canvas — business model canvas, SWOT, persona
- The tree — mind maps, sitemaps
- The plot — Wardley maps, process flows
- The cluster — affinity groups
- The open canvas — freeform, anything goes
Seven is reserved. Adding an eighth isn't a new template — it's real engineering, because the whole system has to learn the shape. That discipline is exactly why the shapes carry weight: each one knows what it allows, and what it refuses.
One canvas, every phase of thinking.
Because every map is the same handful of shapes underneath, you can move through the phases of product work without switching tools. Map the landscape to find where to play, explore the directions worth taking, commit to a plan, schedule it. Make sense of research, build empathy, trace a flow.
Each map unlocks a kind of thinking the others can't do cleanly — and they all live on one canvas. That's not a marketing line. It's why CardBoard is the mapping company: there's a theory underneath, not a pile of templates.
Two doors into it: start from the user's journey with story mapping, or start from an AI conversation, spec, or flowchart with spec mapping. Same canvas underneath.
A map that knows what it is can be read by anyone — or anything.
When a map carries its own rules, two things follow. A person reads the picture. An agent reads the rules — what goes where, what's allowed — and proposes work that fits, instead of guessing and handing you slop. Paste a diagram your AI generated and it restructures into a real, structured map, not a flat sketch you have to redraw.
One plan, drawn for people and typed for machines.
This is the thinking behind CardBoard — four traits from two cuts, seven shapes, one substrate. The "keep the why" lineage I inherited from David Hussman and Jeff Patton; the theory of maps is what I built on top of it to make the why survive the handoff to machines.
Want the full derivation — every trait, every shape, and the exact rules each one enforces? That lives in map traits, where what this page asserts, the product enforces.
Josh Colter