Observability Engineering, 2nd Edition

Chapter 26. The Business Case for Observability

In the AI era, our primary constraint has shifted from developing code to understanding and validating it. To do this swiftly, easily, and consistently, you need to connect developers to their code in production through a single, fast, efficient feedback loop.

Production is where developer intent meets reality. Every deploy is a unique confluence of infrastructure, software, user traffic, and time, which happens once and can never be precisely repeated; observability is how we make sense of that intersection.

This chapter takes the next step: how to get funding support and protect the work that turns feedback loops into sociotechnical change that persists.

Modern observability is rooted in infrastructure, and many leaders are still accustomed to managing it as a cost center. But observability for developers is one of the most powerful levers for accelerating learning and converting engineering labor into product delivery as efficiently as possible. If you’re a leader trying to do just that, this chapter will help you make the business case.

In this chapter, we’ll talk about how to anchor your business case in the feedback loop you want to accelerate, how to quantify value for your organization, and how to frame observability in a way that survives annual planning cycles.

Identifying Your Priorities

Developing the business case for observability shouldn’t start with comparing vendor feature lists. Instead, leadership alignment begins ...