Skip to content
MTTL, Mean Time To Learn

Cross-cuttingBeginner

Maturity self-assessment

For: engineers and SREs · architects · team managers · business and product · executives and CIOsPrerequisites: None.

Reading mode

In my view, an observability program rarely fails because the technology is too weak. More often, one of the four dimensions has been left behind. It may be a solid stack that nobody owns, a budget nobody can defend or an on-call rotation wearing itself out. This assessment places you on each of them, from 0 to 5, like the site’s maturity roadmap, and brings out the gap that weakens the whole.

Start by picking your profile. Technical team questions are about what the team builds; business leadership and support function questions are about what actually reaches you. Each answer describes an observable situation. When in doubt between two, pick the lower one.

Where do you stand?

About twenty questions, around ten minutes. Each answer describes an observable situation: pick the one closest to your reality today, not to what is planned.

Your profile

Your answers stay in this browser. Nothing is sent.

Things to try

Section titled “Things to try”
  1. Compare viewpoints. Answer with the technical profile, copy the summary, then start over with the business profile, putting yourself in your leadership’s shoes. If engineering sees itself at 3 and the business sees it at 1, look at translation before you look at tooling.
  2. Spot the gap. A gap of at least 1.5 points between two dimensions is flagged as a risk. Try raising your strongest dimension by one notch in your answers. The gap widens and the named risk stays the same, since the weakest dimension sets how solid the whole is.
  3. Try the AI dimension. If you run LLMs in production, tick the option in the technical profile. This dimension can be the weakest even when the rest of the stack is mature, for instance when LLMs were added outside the existing setup.
  4. Send the summary. The “Copy the summary” button produces plain text with the levels, the next step and the action plan, links included, ready to paste into an email.

How to read the result

Section titled “How to read the result”

Each answer is worth 0 to 3. A dimension’s level is the average of its answers, scaled to a 0 to 5 ladder (flying blind, reactive, structured, managed, shared, closed loop). As with AI maturity, level 3 is a realistic six-month target and level 5 remains rare.

The suggested next step is the weakest dimension, even if progress would be easier elsewhere, because it caps the value of the others. The action plan takes your lowest answers, at most two per dimension, and points to the page of the site that covers each one.

This assessment is indicative and self-reported. It does not replace an audit, nor the conversation it should start. To go further, read Bridges, then the overviews of the technical, business, people and organization planes, or follow the path for your role.