From intent to commit.
Open any backlog. It's a wall of tickets, each one a how with the why scraped off. Nobody threw the reasons out on purpose. The format did it for them.
Dude's Law
CardBoard came out of DevJam. David Hussman and his team built it after years of teaching teams to map their work. They learned the practice alongside Jeff Patton and pressure-tested it on the floor with teams at companies like Target.
David had a law for it. Dude's Law: value is why over how. The better you understand the why, the less how it takes to get there.
His answer was a map. Put the why out in the open, next to the work, where it can't quietly fall off the board.
A good home
When David died, the idea didn't. SEP took CardBoard in and made it hold up for serious teams: the security, the scale, the enterprise weight. They were careful stewards. But a planning tool was never their core business, so it held steady and stayed mostly still.
The bet
I bought CardBoard from SEP because something this good shouldn't sit parked. But that's not the bet.
The bet came later, the hard way.
I started rebuilding CardBoard with agents. And the agents did to me exactly what we'd watched them do to everyone else. The context I'd carefully loaded would just evaporate. The thing would come back confident and wrong. Slop. So I'd re-explain, and re-prompt, and re-explain again.
Somewhere around the fourth re-prompt: holy crap, what did I do?
Then the feeling placed itself. Déjà vu. This was exactly what it felt like to work with engineering when I came up through sales and marketing. Two people, a wall between them, both certain they were being clear.
Agile spent its first decade on that wall. Story mapping was part of how we got over it: a picture two kinds of people could stand around and actually mean the same thing.
Now the wall runs between people and agents. They don't read the same way. Specs are the native tongue of machines: precise, literal, written down. People work the other way. A picture is worth a thousand words.
Most tools make you pick a side. A canvas people can read but an agent can't, or a stack of specs an agent can parse but people won't.
A map is worth a thousand words.
That's the bet. One plan, drawn for people and typed for machines, so a person and an agent can finally hold the same why at the same time.
A bet that size needed a foundation, so I built one: a theory of maps — four things every map is made of, the seven shapes they combine into, the rules that let a person and an agent read the same board. It's the part that makes "typed for machines" true instead of a nice line.
Keep the why
I'm standing on shoulders here. Hussman's. Patton's. Everyone who built CardBoard before it was mine.
The collaboration problem is new. The job is the same one David named.
Keep the why.
Josh Colter