We ran blameless postmortems after every incident. We wrote detailed action items with owners and deadlines. Six months later, 78% of those items were still open — and the same incidents kept happening.
- Published On
incident management
Tags
consulting (55)debugging (23)developer-experience (19)architecture (18)reliability (16)devops (11)ai (10)performance (9)observability (7)code-quality (6)database (5)productivity (4)technical-debt (4)kubernetes (4)postgres (4)tooling (3)security (3)microservices (3)testing (3)engineering-culture (3)infrastructure (2)nodejs (2)code-review (2)deployment (2)databases (2)opentelemetry (2)monitoring (2)postgresql (2)ci-cd (2)javascript (2)goals (2)dns (1)opinion (1)api-design (1)memory (1)configuration (1)error-handling (1)secrets-management (1)webhooks (1)resilience (1)containers (1)environments (1)queues (1)cloud (1)cost-optimization (1)orm (1)refactoring (1)on-call (1)alerting (1)incident-management (1)typescript (1)distributed-systems (1)caching (1)platform-engineering (1)dependencies (1)feature-flags (1)api (1)contracts (1)logging (1)mongodb (1)migration (1)workflow (1)nestjs (1)angular (1)sandbox (1)sonarcube (1)learning (1)journey (1)mdx (1)