Write a model incident update
Draft a model incident update with impact, scope, mitigation, unknowns, and next check time.
The incident channel is busy, but stakeholders do not know who is affected or what the team has done. Impact -> Scope -> Mitigation -> Unknowns -> Next update The common trap is sending theories as updates. Stakeholders need current operating truth, not the team's full debugging stream. Impact Name the user-visible or decision-visible symptom: mobile new-user recommendations show a 9% lower click proxy since 14:10 UTC. Impact answers why the incident matters and prevents cause-only updates. Scope Bound the affected surface: model v31, iOS only, new-user slice, 6% of total traffic. Scope prevents overreaction and helps leaders decide who…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in