20 January 2026
When a readiness workshop should say hold
A green pipeline is not a release decision. Workshops earn their keep when they name conditions that still block a safe window—missing rollback owners, unresolved flaky suites on the critical path, or an on-call rota that leaves the busiest hour uncovered.
We treat three signals as strong hold criteria: no practiced rollback in the last two months, an open severity-one defect in a dependency the release touches, or a soak environment that has been unavailable for more than half the planned observation period.
Saying hold is easier when the scorecard is visible to product and engineering together. The workshop then becomes a shared record, not a late-night argument in a chat channel.
If you leave with a conditional-go, assign owners and deadlines before anyone leaves the room. Unowned conditions tend to reappear as production surprises.