The Scenario
Your B2B software was completely offline for 6 hours on a Tuesday due to a botched database migration. Customers lost revenue. The CEO wants a public post-mortem published on the blog to rebuild trust.
The Brief
Write the public post-mortem blog post. It must balance technical honesty with sincere apology and clear preventative measures.
Deliverables
- A sincere apology section acknowledging the specific business impact on your customers
- The "What Happened" section (a readable timeline of the technical failure)
- The "What We Are Doing About It" section (3 concrete engineering/process changes to prevent recurrence)
Submission Guidance
A good public post-mortem takes ownership. Never blame an individual engineer. Explain the systems failure clearly enough that technical users respect your honesty, but simple enough that a business owner understands it.
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.