7 min read
Bridges: taking observability beyond IT
When observability stays inside the technical team, the project eventually fails. How to open the conversation with the business, the organization and business lines, starting from their questions, with a translation dictionary and a few regular meetings.
For: engineers and SREs · architects · team managers · business and product · finance, risk and compliance · executives and CIOsPrerequisites: None.
Here is an illustrative scene. At a budget committee, the CFO finds out that the bill for the observability platform has doubled in a year. She asks what the company got in return. The technical team shows CPU and response time charts. Nobody else in the room can read them. The budget gets cut.
The tools worked and the data was there. What was missing was a bridge between the technical team and the rest of the company. This page explains how to build one.
Why do observability projects rarely fail because of the tool?
Section titled “Why do observability projects rarely fail because of the tool?”When an observability project fails, it is rarely for technical reasons. The dashboards exist. What you find instead are situations like these. Finance sees a growing bill without understanding what it buys. Business lines do not recognize themselves in charts of CPU (the servers’ processor) and “p99 latency”, the response time of the slowest 1% of requests. Compliance finds out at audit time that the evidence exists but is neither retained nor exportable. Leadership cannot say whether the investment reduced risk. And the technical team, the only one looking, wears itself out defending a budget nobody else owns.
As long as it stays inside IT, observability is seen as a cost center. Its standing changes when other departments use it to make decisions, because it gives them a shared language with the technical team.
Start from other people’s questions
Section titled “Start from other people’s questions”You instrument a system, meaning you make it emit signals about how it works, to answer questions. So I recommend starting a project by listing those questions, before any talk of tools. In my view, most of them come from outside the technical team.
| Who asks | The question rarely asked | What observability can answer |
|---|---|---|
| Business line, product | do our customers succeed at what they came to do? | completed journey rate, end-to-end time, per customer segment |
| Finance | what does a transaction, a customer, a feature cost? | unit cost of infrastructure and observability data, cost per LLM request |
| Risk, compliance, legal | can we prove what happened, to a third party? | tamper-evident logs, retained traces, DORA, NIS2, AI Act evidence matrix |
| Customer service, support | did this customer really suffer the incident they report? | the trace of their request, with the goal of finding it in under a minute |
| Procurement | are we locked in by our vendor? | open standards, data portability, exit cost |
| HR, management | can the team keep this up? | on-call load, alerts per night per person, noise |
| Executive leadership | where should we invest to reduce risk? | quantified exposure of blind spots, avoided loss |
The bridges to build
Section titled “The bridges to build”I see five directions to build a bridge towards. Each has its own people and its own way of talking.
flowchart LR
O(("Observability"))
O --- B["1. Business<br/>value and cost"]
O --- ORG["2. Organization<br/>who decides, who owns"]
O --- MET["3. Business lines<br/>translated signals"]
O --- SUP["4. Support functions<br/>finance, compliance, procurement"]
O --- PER["5. People<br/>language and rituals"]
1. To the business, talking value and cost
Section titled “1. To the business, talking value and cost”An SLO is a service quality target expressed as a number. I recommend phrasing it as a promise made to customers. “99.5% of payments complete in under two seconds” means something to a product director, whereas “API p99 latency under 800 ms” tells them nothing.
The second figure to build is a unit cost, per transaction, per customer or per feature. It is the only one a financial controller can compare month to month. You can also put a figure on avoided loss from incident cost, exposure duration and blind spots. The exposure calculator gives an example for AI.
2. To the organization, saying who decides and who owns
Section titled “2. To the organization, saying who decides and who owns”Who chooses what is collected, who pays for storing the signals, who owns each alert? Until the answer is written down somewhere, nobody takes it on.
Two tools turn these good intentions into rules. A data contract states which signals a team commits to produce and in what form. A RACI is a table that says, for each task, who does it, who is accountable, who is consulted and who is informed. See the organization dimension and part VII of the GenAI method.
3. To business lines, translating the signals
Section titled “3. To business lines, translating the signals”A business event is a moment that matters to the company: an order confirmed, a file processed, a loan granted. I recommend instrumenting these as carefully as technical calls and linking them to traces, the records of a request’s journey from one service to the next. This is sometimes called business observability.
Then keep a translation dictionary between technical and business indicators (see the example below). And build dashboards per audience. An operations dashboard is not built for an executive committee: in my view, it loses more attention there than it gains.
4. To support functions (finance, compliance, procurement)
Section titled “4. To support functions (finance, compliance, procurement)”For finance, the observability budget is tracked like any other, with its drifts and levers. See the business dimension.
For compliance, evidence is a by-product of good instrumentation, provided it is designed in from the start. See log integrity and the evidence matrix.
For procurement, reversibility, meaning the ability to switch providers and take your data with you, is settled during negotiation. Once the contract is signed, it is too late to secure it.
5. To people, with a shared language and shared rituals
Section titled “5. To people, with a shared language and shared rituals”I recommend a monthly review bringing engineering, product and finance together around three figures: service quality as customers see it, unit cost and incidents with their causes.
Post-mortems, the meetings that analyze an incident after the fact, are worth opening to the business lines concerned. They find out how the system works. The technical team learns what the incident actually cost.
A translation example
Section titled “A translation example”| Technical signal | Business indicator | Decision informed |
|---|---|---|
| payment service p95 latency | cart abandonment at the payment step | prioritize optimization or a second payment provider |
| pricing engine error rate | quotes not issued per day, deferred revenue | choose between an immediate fix and degraded mode |
| tokens consumed per AI feature | cost per assisted customer conversation | adjust the model, the cache or the offer’s price |
| faithfulness score of a RAG assistant | complaints caused by wrong information | trigger a knowledge base update |
| night alerts per on-call engineer | team turnover and sick leave | revisit thresholds, rotations, staffing |
Each row connects three people who do not always talk to each other: whoever sees the signal, whoever owns the indicator and whoever decides.
Take the first row. The p95 latency is the time within which 95% of payments complete. If it rises at the same time as cart abandonment, the link becomes visible to everyone and helps decide between optimizing the service and bringing in a second provider. The loop closes when the decision brings the signal back down.
flowchart LR S["Technical signal<br/>payment p95 latency"] -->|"translation"| I["Business indicator<br/>cart abandonment"] I -->|"trade-off"| D["Decision<br/>optimize or second provider"] D -.->|"measured effect"| S
Signs a bridge is missing
Section titled “Signs a bridge is missing”If several of these sentences describe your situation, there is a bridge to build:
- the observability project is owned by IT alone, with no business sponsor;
- dashboards have never been opened by anyone outside the technical team;
- no SLO is phrased in a customer’s words;
- the cost of observability data is discovered on the invoice;
- compliance was not consulted on how long logs are kept;
- post-mortems never leave the operations team.
On this site
Section titled “On this site”Every article and course ends with a Bridges box stating what the topic changes for the business, the organization, teams and business lines. I keep to this on every page, as the manifesto explains.