Beginner3 min read
Maturity self-assessment
Place your organization on four observability dimensions (technical, business, people, organization), spot the gap that weakens the whole and leave with an action plan.
For: engineers and SREs · architects · team managers · business and product · executives and CIOsPrerequisites: None.
Picture a company that has invested in very good monitoring tools. The engineers are proud of them. But nobody has been named to run the platform, leadership cannot say what it brings in and on-call sleeps badly. The scenario is illustrative. It shows that technology alone is not enough.
In my view, an observability program rarely fails because the technology is too weak. More often, one of the four dimensions (technical, business, people, organization) has been left behind. Think of a chain: it breaks at its weakest link, however strong the others are. This assessment places you on each dimension, from 0 to 5, like the site’s maturity roadmap and brings out the gap that weakens the whole.
Start by picking your profile. The questions for the technical team are about what it builds. The questions for business leadership and support functions are about what actually reaches you. Each answer describes a situation you can observe. 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 answers stay in this browser. Nothing is sent.
Keyboard: arrow keys to choose, keys 1 to 4 to answer directly, Enter to continue.
Your result
Your next step
Gap between dimensions
Your action plan
Built from your weakest answers, starting with the least advanced dimension.
An indicative self-assessment, not an audit. A dimension’s level is the average of your answers (0 to 3) scaled to the site’s 0 to 5 ladder. A gap is flagged from 1.5 points.
Things to try
Section titled “Things to try”- 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, I would look at translation before tooling.
- 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.
- Try the AI dimension. If you run LLMs (the large language models behind chat assistants) in production, tick the option in the technical profile. This dimension can be the weakest even when the rest is mature, for instance when LLMs were added outside the existing setup.
- 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 do you read the result?
Section titled “How do you 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 rests on what you answer. It does not replace an audit, nor the conversation it should start. Next, I suggest showing the summary to someone from another department, then reading Bridges and the overviews of the technical, business, people and organization planes, or following the path for your role.