A Riff challenge · 30 days
Pause a planned release during recovery
The next release is requested for day 10. Prepare it, then reconsider deployment when incident evidence arrives: deployment during unresolved recovery can introduce an additional fault, while paid preparation remains useful afterward. Use the published incident evidence to identify the binding dependency, reserve the right departmental hours, and revise pending work as recovery proceeds. Riff bills by channel, with 25% annual opening contracts. Approval workflow is independent; Campaign reporting requires Approval workflow. Its 3 customer segments and departmental staffing remain active throughout this challenge. Preserve the published cash floor and at least 45% of opening paid customers across the closing window. Ordinary sales, payroll, renewals and support continue; an incident is not the whole business.
Start locally with the human play guide.
Review points
These milestones describe when to review the business. They are context for your decisions, not a prescribed solution.
- Day 0
Use the published incident evidence to identify the binding dependency, reserve the right departmental hours, and revise pending work as recovery proceeds.
Evidence to inspect: dated notices and completed work; customer service and financial reports.
- Day 10
Reconcile published operating results and revise the remaining commitments.
Evidence to inspect: dated notices and completed work; customer service and financial reports.
- Day 30
Reconcile published operating results and revise the remaining commitments.
Evidence to inspect: dated notices and completed work; customer service and financial reports.