A Tempo challenge · 30 days
Test the dependency classes before rollout
A product revision appears safe on an isolated route. Team scheduling uses a shared dependency that the narrow canary does not exercise; include the relevant dependency classes before deploying broadly. Choose the scope of the canary, inspect its finding, and gate the broad rollout on evidence that covers the affected product dependencies. Tempo bills by seat, with 45% annual opening contracts. Project boards is independent; Team scheduling requires Project boards; Approval inbox requires Project boards. 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
Choose the scope of the canary, inspect its finding, and gate the broad rollout on evidence that covers the affected product dependencies.
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.