Observability Practical By Samson Tanimawo, PhD Published Feb 8, 2026 4 min read

The Incident Cost of Bad Observability

Bad observability costs minutes per incident. The cost model and the investment that pays it back.

Cost model

Each incident: detection time + diagnosis time + remediation time. Bad observability inflates the first two.

Median impact: 10-30 minutes per incident from poor observability. Aggregate annually for total cost.

Investment

Engineering time on observability features. Tooling and vendor budget. Training.

Pays back when incident MTTR drops. Most teams: 6-12 month payback.

Track

Per-incident: 'what would have made this faster?' Often: better dashboards, better runbooks, better alerts.

Aggregate over a year: the obs roadmap writes itself.