Customer & OpsBeginner 1 to 2 hours

Write Status Page Updates

Draft the public communications during a live payment gateway outage.

The Scenario

It is month-end payday. Your payment gateway goes down. Customers cannot checkout. Engineering says they are "looking into it" but don't have an ETA. You need to update the public Status Page immediately.

The Brief

Write the sequence of 3 status page updates spanning the lifecycle of the incident.

Deliverables

  • Update 1 (Investigating): The initial acknowledgement of the issue
  • Update 2 (Identified): 45 mins later, engineering found the issue and is deploying a fix
  • Update 3 (Resolved): 2 hours later, systems are stable. What the customer should do if a payment got stuck.

Submission Guidance

Status page updates must be factual, calm, and void of jargon. Do not say "Our Redis cluster segfaulted." Say "We are experiencing degraded performance in our checkout flow."

Submit Your Work

Your submission is graded against the rubric on the right. If you pass, you get a public Badge URL you can share on LinkedIn. There is no draft save, so work offline first and paste your finished response here.

This appears on your public Badge.

0/20000 charactersMarkdown supported

One per line or comma separated. Up to 5 links.

By submitting, you agree your submission text, name, and evaluation will appear on a public Badge URL.