Skip to content

4 min read

Paths by role

Six entry points depending on your role, from engineers to leadership by way of business lines and finance, each with its reading order across the four dimensions.

A developer discovering observability and a CFO preparing a budget are not looking for the same thing. The first wants to know how to make her application talk. The second wants to understand what he is paying for. This page suggests a reading order for each role.

The site stays open and can be read in any order. The paths below draw on the site’s four dimensions (technical, business, people, organization). They are not only for technical teams: observability is worth little if business lines, finance and compliance do not know what to expect from it.

New to observability, whatever your role? Start with observability in 10 minutes. If you are not sure where your organization stands, the maturity self-assessment places it on the four dimensions and suggests an action plan. Steps marked “coming soon” are not written yet: they will arrive as the site grows. Each overview flags the chapters still missing.

The aim is to be able to instrument your application (make it emit signals about how it works), collect those signals and troubleshoot a problem on your own.

  1. Technical: signal fundamentals, then OpenTelemetry end to end.
  2. Technical: collection pipelines, with the animated Collector pipeline until the Collector lab is out (coming soon).
  3. Technical: SLOs and alerting.
  4. People: troubleshooting under pressure (coming soon); meanwhile, the blameless post-mortem.
  5. Technical, going further: observing an LLM system.

If you work on generative AI, I recommend this order: AI in cross-section, understanding generative AI observability, the LLM labs, the deployment playbooks and VictoriaMetrics for LLMs, then the GenAI method and beyond the LLM.

This path is about choosing the platform’s tools, sizing it and keeping it standing as volume grows.

  1. Technical: collection pipelines (the animated Collector pipeline), then backends and storage (coming soon).
  2. Business: cost is decided at the Collector (Collector cost simulator), then pricing models (coming soon).
  3. Business: sovereignty and architecture choices (coming soon); meanwhile, the solution scorecard.
  4. Organization: observability data governance and data contracts.
  5. Technical: log integrity if you operate in a regulated environment.

For generative AI, start with understanding generative AI observability, then the deployment playbooks and VictoriaMetrics for LLMs. The GenAI method comes next, once the guide is under your belt. If you run GPUs, read the HPC AI reference architecture too.

This path answers two questions: how to make on-call sustainable and how to get the team to adopt observability.

  1. People: alert fatigue, then sustainable on-call; the leadership view is in the CIO path, lesson 5.
  2. People: blameless post-mortems.
  3. Organization: SLOs, those numeric service quality targets, as a contract between teams, starting from SLOs and alerting.
  4. Organization: team models; for hiring, the profiles and the job description generator; driving adoption (coming soon).

Two tools go with this path: the RACI matrix to set out who does what and the alert fatigue simulator.

You want to know what you can ask of observability and how to get it from your technical team.

  1. What the business can ask of observability: the questions to ask your tech team and a checklist to bring to meetings.
  2. Bridges: the translation dictionary between technical signal and business indicator.
  3. Organization: SLOs as a contract between teams, phrased in your customers’ words: SLOs and alerting, skipping the formulas.
  4. People: blameless post-mortems, where you belong too.
  5. For AI: AI in cross-section, then understanding generative AI observability, chapters 1 and 3.

This path helps you track a unit cost (the cost of one transaction or one customer) and hold evidence that stands up in front of an auditor.

  1. Bridges, section “To support functions”.
  2. Business: the business case, then observability FinOps.
  3. Technical, without reading code: a signed log is not an auditable log, sections 1 to 3.
  4. For AI: evidence matrix and exposure calculator.

The aim is to make trade-offs on budget, risk and sovereignty knowing what you are deciding.

  1. The course Governing observability: the CIO path, written for this profile: business case, compliance, governance, FinOps, people, steering.
  2. Organization: the maturity self-assessment, then team models.
  3. To prepare an executive committee meeting: the toolkit and the executive dashboard.

To get your bearings without a technical background: understanding high performance computing. To put figures on it: the GenAI exposure calculator.

Revised on 4 October 2026: generative AI steps aligned with the progression (AI in cross-section, guide, labs, production, method, beyond the LLM); the architect goes through the guide before the method.