Do / Don't
The two columns that close the document.Do
- Keep every non-sticky surface monochrome — steel, ink, paper.
- Label the type in mono on every sticky, so color is never the only signal.
- Let position carry sequence; reserve arrows for lane crossings, loops and boundaries.
- Snap to the 8px grid and align stickies to lane baselines.
- Surface gaps in the review queue and let a person decide.
- Keep the facilitator in steel — colour belongs to the domain, not the tool.
- Rule the ground when position carries a score, and label the axes with the enum’s own words.
- Print the parking tray with every export; the reader needs to know what is missing.
Don't
- Don’t rotate, texture or shadow stickies at rest — they are flat rectangles.
- Don’t recolor a connector to mean something; line style carries the type.
- Don’t introduce a thirteenth sticky color. Extend with the existing twelve.
- Don’t resolve a hotspot or question by deleting it; it closes with an answer.
- Don’t put color in toolbars, panels, avatars or lane headers.
- Don’t let the facilitator write to the board; it proposes, a person accepts.
- Don’t store a coordinate the model can’t express — snap to the lattice, jitter inside the cell.
- Don’t let a tab hold data no other view can see; every tab is a projection of one model.