The readiness review
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
run a review that covers observability, capacity, failure handling, security, and support.
Planned topics
- Five areas, each with questions that need evidence, not opinions: dashboards and alerts exist; load test passed at forecast; dependency failure tested; threat review done; on-call runbook and owner named.
- Evidence is a link or a result, not "we think so".
- Findings get a severity: blocker, must-fix-soon, accepted risk with a named owner.
- The review happens before the launch date is fixed, and it is a conversation with the service team, not an audit of them.
Draft outline details
Demonstration
One-page review template: area | question | evidence link | status | owner. Example row: Failure handling | what happens when the payment provider times out? | chaos test result | pass | owner: orders team.
Check your understanding
What distinguishes evidence from opinion in a review?
Show answer
Evidence is something checkable, such as a test result or dashboard link.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.