⭐ Repository → 💼 AWS Well-Architected → 💼 Operational Excellence → 💼 Evolve
💼 Learn, share, and improve
- ID:
/frameworks/aws-well-architected/operational-excellence/evolve/ops11
Description
It’s essential that you regularly provide time for analysis of operations activities, analysis of failures, experimentation, and making improvements. When things fail, you will want to ensure that your team, as well as your larger engineering community, learns from those failures. You should analyze failures to identify lessons learned and plan improvements. You will want to regularly review your lessons learned with other teams to validate your insights.
Similar
Sub Sections
| Section | Sub Sections | Internal Rules | Policies | Flags | Compliance |
|---|---|---|---|---|---|
| 💼 OPS11-BP01 Have a process for continuous improvement | no data | ||||
| 💼 OPS11-BP02 Perform post-incident analysis | no data | ||||
| 💼 OPS11-BP03 Implement feedback loops | no data | ||||
| 💼 OPS11-BP04 Perform knowledge management | no data | ||||
| 💼 OPS11-BP05 Define drivers for improvement | no data | ||||
| 💼 OPS11-BP06 Validate insights | no data | ||||
| 💼 OPS11-BP07 Perform operations metrics reviews | no data | ||||
| 💼 OPS11-BP08 Document and share lessons learned | no data | ||||
| 💼 OPS11-BP09 Allocate time to make improvements | no data |