← All stories
● Covered by 1 source · 1 reportLow impact1 neutral

Increased Incident Counts Can Signal Improved Incident Management, Not Declining Reliability

🔄 Updated 1d ago
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • Increased incident reports may show better incident management.
  • Improved processes encourage formal declaration of issues.
  • Incident count measures willingness to surface problems, not reliability.
  • Enhanced visibility aids learning and prevents future outages.

Challenging Incident Volume as a Metric

A common assumption in engineering leadership is that more reported incidents mean less reliable systems. However, a recent article from Great Circle suggests that the opposite can be true. An increase in incident counts might indicate an organization's incident management culture is improving, not that its systems are failing more often.

Improved Visibility, Not Deterioration

When teams invest in better processes, tools, training, and operational discipline, they become more willing to formally declare incidents that might have previously been handled informally or hidden. This results in greater visibility into operational issues, which does not necessarily mean a deterioration in the underlying system health.

Incident Count Reflects Management Maturity

The article argues against using incident volume as a key performance indicator for reliability. Instead, incident count measures an organization's willingness to surface and manage operational problems. Mature incident management cultures encourage early incident declaration, stakeholder involvement, and structured post-incident reviews. While this can initially increase reported incidents, it also creates more opportunities for learning and process improvement, potentially preventing larger outages.

Parallel Across Engineering Disciplines

This phenomenon is observed in other engineering fields. For example, stronger vulnerability management often leads to more reported security findings because detection capabilities have improved, not because systems are suddenly less secure. Similarly, better observability can generate more alerts, and enhanced testing uncovers more defects before production. In each case, improved measurement reveals existing problems rather than creating new ones.

Enhanced Resilience Through Visibility

Incident management follows this pattern. Engineers who previously resolved issues quietly may now declare formal incidents, triggering coordinated responses, documentation, and postmortems. Although dashboards may show more incidents, the organization becomes more resilient by making operational knowledge visible and repeatable. This aligns with modern SRE practices that prioritize customer impact and recovery effectiveness over simplistic operational metrics.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~7 min · 6 stories · Aug 15

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

Reporting from

A recent article argues that a rising number of reported incidents often indicates an improvement in an organization's incident management culture, rather than a decline in system reliability. As teams enhance processes and tooling, they become more willing to formally declare incidents, leading to greater visibility into operational issues. This perspective challenges the use of incident volume as a primary performance indicator for system reliability.