Design the operation before
you draw the board.

The workshop was perfect. Stakeholders aligned, sticky notes everywhere, the facilitator got a round of applause, the process map looked like art. Two months later it's a file nobody opens. The handoffs it described didn't hold. The roles it implied were never enforced. The decisions it didn't capture are the ones that actually broke.

This is a design problem, not a Miro problem. A sticky note that says "Review PR" is a label, not a design. A designed step tells you who reviews, what quality bar they're applying, what happens when the bar isn't met, what inputs they need, and whether the work should be done by a human, an AI, or both. Miro doesn't ask for any of that — which is why most Miro boards describe an operation that nobody is actually running.

Henry runs the design step. He maps your operation using the AAAERRR methodology from Deliberate Work and specifies every step across three planes. The Miro board your team drafts on top of that design is a diagram of a system that has been thought through — not one they'll have to rebuild in a year. For consultants running workshops, this is the artifact that survives your engagement: a designed operation, rendered visibly in Miro.