Building a risk board for a strategy workshop

A strategy workshop fails when the board is blank at 09:30 and half the room argues about vocabulary. We spend the week before filling a draft board with candidate journeys pulled from support tags, incident history, and the last three release notes.

Severity language that sticks

We avoid abstract “P0/P1” alone. Each card gets a consequence sentence: “Buyer cannot pay,” “Merchant sees wrong settlement overnight,” “Locale string wrong on settings.” Product can challenge the sentence; engineering can challenge feasibility. Both debates are useful.

Who must be in the room

QA alone cannot rank product risk. We ask for one product voice and one engineer who has on-call scars. If either seat is empty, we reschedule rather than invent consensus.

After lunch

Energy drops. We switch from ranking to “automate / sample / accept” decisions on the top third only. The rest becomes a parking lot with owners. Forcing completeness in one day produces fiction.