Example data. Fieldnote is a fictional company used to fill all 61 boards, so the examples tell one consistent story.
Post-PMF, Ana sketches the three screens of the offline flow in grey so Tom and Karim argue about logic, not colours.
What the team took away
Tom spotted that the Save button on screen 2 was greyed out in the first sketch; it is the one thing that must never depend on the network. Two other screens were cut.
How to run it
Preparation
Invite the designer, the PM and the tech lead. Three people, one screen each on the board, no observers.
Send the user flow or story map slice being designed the day before, plus the list of screens it needs. Wireframing without a flow produces pretty orphan screens.
Prepare one empty frame per screen on the board, labeled with the step it serves. Keep a strict grey palette: no color, no logo, no real typography.
Agenda
15 min
Walk the flow Read the flow step by step and confirm the screen list. Write on each frame the one thing the user must do on that screen. If you cannot write it, the screen does not exist.
30 min
Solo sketch, round one Each person sketches every screen alone with boxes and lines only. Ten minutes per screen. Words in the boxes, no icons.
30 min
Compare Put the three versions of each screen side by side. For each screen, name what the versions agree on (keep it) and the one difference worth discussing. Two minutes per difference, then vote.
45 min
Converge, round two The designer redraws each screen from the winning elements while the other two watch and challenge. Add the empty state and the error state for every screen with a form or a list.
35 min
Content pass Replace every 'Lorem' and every 'Button' with the real words. Real labels reveal half of the layout problems. The PM writes, the designer adjusts.
20 min
Tech check Tech lead marks anything that costs more than a day or needs data the product does not have. Those marks go into the estimate, not into a redesign.
5 min
Close Number the screens in flow order and export. The board is now the reference for the sprint; visual design starts from it, not from scratch.
Pitfalls
Do not open the design system during wireframing. The moment a real button appears, the conversation shifts from logic to style.
Do not skip the empty and error states. They are the half of the screens developers actually ask about.
Do not wireframe a screen nobody can describe in one sentence. Go back to the flow instead.
Afterwards
The numbered wireframes go to visual design and into the sprint as the definition of each story. Test them with three users before high fidelity if the flow is new; skip the test if it is a redesign of a known step.