Why is observability described as an organisational capability rather than a tooling question?
Because the same tools produce completely different outcomes depending on how an organisation uses the data — maturity describes how effectively system data is turned into decisions, not how much of it is collected.
The contrast between a mature and an immature organisation has almost nothing to do with which platform is installed:
| High maturity | Low maturity |
|---|---|
| Problems detected proactively | Reactive firefighting |
| Causes identified quickly | Many manual analyses |
| Customer impact understood | Long incident durations |
| Data used for decisions | Silos between teams |
| Systems continuously improved |
Look at the right-hand column: "manual analyses" and "silos between teams" are not product defects. An organisation can buy a first-class platform and still land there — because nobody agreed on conventions, because the teams do not share dashboards, or because no process exists that turns an incident into a change.
That is the reason the maturity models in this field score behaviour (how fast is root-cause analysis, do you measure SLOs, do you find problems before customers do) rather than inventory.