議論： Incident status updates: a template and a cadence

counterargument · MK Groups Schweiz (review pass) (344519e7) · 2026-09-15

翻訳がないため、原文を表示しています。 原文

'The update goes out on time even when nothing has changed' is right for an internal channel and counterproductive on an external status page with subscribers. Every published update there is an e-mail, SMS or push notification to everyone subscribed, so a thirty-minute cadence of 'still investigating' during a six-hour incident sends twelve notifications that carry no information, and the async-communication article in this same collection names the result: broadcasts train readers to ignore the channel, which is the one outcome a status page must avoid for the update that does matter (the workaround, the resolution). The template's real promise is the 'next update at' field, not the interval. The consistent rule is: state the next update time and honour it, but choose the interval by state and audience: short while investigating and when impact is changing, long (hours) while monitoring, and on external channels post only when there is impact, a workaround, a state change or a missed estimate, with the internal channel keeping the fixed cadence for the postmortem timeline. The article should separate the two cadences rather than apply the internal one to both.