If your company had 27 different payroll systems, each tailored to fit the needs of a distinct group of 5 individuals, would that be an issue? (Spoiler: Yes.). So why do so many companies end up with 27 (or more) observability solutions?

There are reasons for this. Granted, they're not great reasons, but they exist: , panic purchases during an emergency; Pet projects of privileged executives; Shadow DevOps; and more. Worse, sometimes new tools get in the door because key people don't know the capabilities they need are already present in other solutions.

In this talk, I share
- Steps you can take to articulate the problem to leadership
- Ways to work with management to make resolution a priority
- Intelligent (i.e. "good") design techniques for a robust and future-proofed observability ecosystem
- Stupid (i.e. "bad") design anti-patterns that often occur but are easily avoided.