
MongoDB's engineers had been told what to build and when to ship it. The product and business owners were arriving at the same time we were, and nobody had yet written down what the thing needed to do.
COMPLEXITY
APPROACH
We drew first. Each prototype was built to move the conversation on, never to be perfect. People could point at a picture and say what was missing, and what they said became the requirements.
The progression
Each one was frozen once it had taught us enough to build the next.
V0
Sketch
Block one moves to block two moves to block three. Our first read of the problem, drawn in days.
What it unlocked
A fast yes: this is where we're going.
V6.8
Crayon
In scope or out. Known or not sure. Sturdy enough to live with for weeks while the requirements were being written.
What it unlocked
Gaps people could see, argue about and settle.
V7.0
Pencil
We knew enough to bring in the visual language and point the work towards production. The journeys stayed as they were.
What it unlocked
One question left to settle: how the AI and chat should behave.
V7.2
Ink
The AI interaction and the chat detail landed. Everyone was looking at the same thing and agreeing with it.
What it unlocked
A design on the path to production.
Meanwhile, MongoDB's requirements: written by their team as each picture gave them something to challenge

A blank page

Being written

Challenged and refined

Documented
The engine
1 · Futuredraft
Draw what we're hearing
2 · Everyone
The gaps show up
3 · Everyone
Gaps become discussion points
4 · Client
Discussion becomes documented requirements
5 · Futuredraft
Requirements change the design
↺ Repeat until the picture has taught us all it can. Freeze it. Start the next one.
2
months
The result
From
A deadline, an outline, and teams still getting up to speed
To
A production design path for the first release
And now a roadmap for what comes after it…