Write a useful incident update before the cause is known.

Instruction: Produce the actual status update using only the supplied facts.

Context:

Fictional UTC timeline: checkout errors rose at 14:02; incident declared at 14:05; at 14:08, approximately 12% of checkout attempts fail. Browsing is unaffected. A release happened at 13:58, but causation is unconfirmed. The incident commander assigned one responder to evaluate compatible rollback and another to inspect database waits. The next update is due at 14:15. No recovery estimate is established.

Updated

Example Answer

14:08 UTC: We are investigating elevated checkout failures that began at 14:02. Approximately 12% of checkout attempts are failing; browsing remains available. An incident was declared at 14:05.

Responders are evaluating a compatible rollback and investigating database waits. A release occurred shortly before the failures, but the cause is not confirmed. We do not yet have a recovery estimate. Our next update will be at 14:15 UTC, or sooner if the situation changes materially.

Worked reasoning

This update answers impact, time, action, uncertainty and next communication without exposing internal secrets or promising an unverified fix.

For the incident channel, add named operational owners if they are known; none are supplied here, so do not invent them. Keep a decision log with action, owner, timestamp and result. The incident commander coordinates priorities while technical responders investigate; a communications owner keeps stakeholders informed.

If the audience is external, use the approved communication path and appropriate detail. Preparing an interview example does not authorize sending a real status message.

What the interviewer is assessing

Core checks (1 point each):

  • States 12% checkout impact and unaffected browsing accurately.
  • Separates the recent release from a confirmed cause.
  • Gives concrete investigation actions and the 14:15 update time without inventing an ETA.

Stronger (+1 after all core checks): Adapts operational detail to the audience while preserving impact and uncertainty.

Acceptable alternatives: A shorter status-page format is acceptable if it retains the essential facts.

Red flags: Blames the release as confirmed, invents a restoration time or says only that engineers are working on it.

Follow-up

Nothing has changed at 14:15. Do you skip the update?

Example response: No. Confirm the current impact and active actions, say there is no confirmed recovery estimate yet, and set the next update time. The communication commitment remains useful even when diagnosis has not advanced.

Related Questions