Platform maturity scorecard
Certified maturity level — Ten areas with four levels each, from "it depends on people" to "it is built in". You end up with a level per area, an overall reading and the next step for the three weakest areas.
Not an audit, not a certificate
This scorecard is a self-assessment, not an examination. It does not know your code, your cluster or your organization — it only knows what you are about to click. There is no grade here, no certificate and no comparison with other companies: we have never measured where "others" stand, so we are not going to claim it. What you get back is an ordered version of your own judgement.
Expect one effect: self-assessments almost always come out kinder than measurements, and a visible ladder makes that worse. When you are torn between two statements, take the lower one. It gets more useful still if two people answer independently and you talk about where they disagree.
Your answers stay in the browser. They are not stored, not transmitted and not evaluated — not even anonymously. What reaches our reach measurement is that the scorecard was displayed, started and completed. Which level you picked, we never find out.
How the number is arrived at
The arithmetic is disclosed and deliberately plain. Each area offers four statements arranged as a ladder: the first is worth zero points, the last three. Ten areas therefore run from zero to thirty. The overall reading is your average level, rounded down — which is why the thresholds sit exactly at ten, twenty and thirty points. Nothing is weighted: a weighting would be a claim about which area costs more, and we have no data behind one. The three lowest areas are the ones discussed in detail; a tie keeps the area listed first. Areas already at the top level never appear there.
The four levels
- Level 0Ad hocIt works when the right people are around.
- Level 1RepeatableThere is a way to do it, but it needs constant attention.
- Level 2EstablishedThe way is set up, written down and followed.
- Level 3Built inIt is a property of the system, not an effort by individuals.
Assessment review steps
Every area belongs to a review step of the Platform Bottleneck Assessment — the short form of what is examined there over days, against your own data.
Ten areas
For each area pick the statement closest to your everyday reality — not the one you are aiming for. Answer for the area you are responsible for, and for a normal day.
Please pick a statement in the areas still open. First one open: —
Your profile
— of 30 points
Average level:Level 0 · Ad hocLevel 1 · RepeatableLevel 2 · EstablishedLevel 3 · Built in
On average: ad hoc
Your ten levels average out to the lowest one. That does not mean nothing works — it means it works because of people rather than because of arrangements. Start at the three places below, not everywhere at once.
On average: repeatable
The essentials are repeatable but cost constant attention. Typical for this position: a few areas hold up the rest. Looking at the weakest ones pays off more than one more step in the strong ones.
On average: established
Your foundations are in place. From here depth beats breadth: a single weak area decides how fast you end up being — and the average hides it.
All ten areas at the top level
It happens, but it is rare — and it is rarer in a measurement than in a self-assessment. Before you pass this result on: have the same statements answered by someone who uses the platform rather than builds it. If the answers differ, that difference is the real result.
Level per area
- Path to productionLevel 0 · Ad hocLevel 1 · RepeatableLevel 2 · EstablishedLevel 3 · Built in
- Platform ownershipLevel 0 · Ad hocLevel 1 · RepeatableLevel 2 · EstablishedLevel 3 · Built in
- Self-serviceLevel 0 · Ad hocLevel 1 · RepeatableLevel 2 · EstablishedLevel 3 · Built in
- SecurityLevel 0 · Ad hocLevel 1 · RepeatableLevel 2 · EstablishedLevel 3 · Built in
- ObservabilityLevel 0 · Ad hocLevel 1 · RepeatableLevel 2 · EstablishedLevel 3 · Built in
- Cost managementLevel 0 · Ad hocLevel 1 · RepeatableLevel 2 · EstablishedLevel 3 · Built in
- Developer experienceLevel 0 · Ad hocLevel 1 · RepeatableLevel 2 · EstablishedLevel 3 · Built in
- ReliabilityLevel 0 · Ad hocLevel 1 · RepeatableLevel 2 · EstablishedLevel 3 · Built in
- GovernanceLevel 0 · Ad hocLevel 1 · RepeatableLevel 2 · EstablishedLevel 3 · Built in
- Team capabilityLevel 0 · Ad hocLevel 1 · RepeatableLevel 2 · EstablishedLevel 3 · Built in
Your areas are far apart — at least two levels separate the strongest from the weakest. In that position the average says little: how fast you ship in the end is decided by the weakest area, not by the mean.
Where to start
The three lowest areas, each with the step from the level you are on to the next one. All three are picked so that you can take them without us and without a budget approval.
You picked the top level everywhere, so there is no next step here. In that case the note in the result box above is the more useful part.
Path to production
Your level
Level 0 · Ad hoc — It works when the right people are around.Level 1 · Repeatable — There is a way to do it, but it needs constant attention.Level 2 · Established — The way is set up, written down and followed.Level 3 · Built in — It is a property of the system, not an effort by individuals.
Next step
Related
Service:DevOps & Platform Engineering
Workshop:GitOps Implementation
Platform ownership
Your level
Level 0 · Ad hoc — It works when the right people are around.Level 1 · Repeatable — There is a way to do it, but it needs constant attention.Level 2 · Established — The way is set up, written down and followed.Level 3 · Built in — It is a property of the system, not an effort by individuals.
Next step
Related
Service:DevOps & Platform Engineering
Workshop:Platform Engineering Foundations
Self-service
Your level
Level 0 · Ad hoc — It works when the right people are around.Level 1 · Repeatable — There is a way to do it, but it needs constant attention.Level 2 · Established — The way is set up, written down and followed.Level 3 · Built in — It is a property of the system, not an effort by individuals.
Next step
Related
Service:DevOps & Platform Engineering
Workshop:Platform Engineering Foundations
Security
Your level
Level 0 · Ad hoc — It works when the right people are around.Level 1 · Repeatable — There is a way to do it, but it needs constant attention.Level 2 · Established — The way is set up, written down and followed.Level 3 · Built in — It is a property of the system, not an effort by individuals.
Next step
Related
Service:Kubernetes & Container Orchestration
Workshop:Kubernetes Operations
Observability
Your level
Level 0 · Ad hoc — It works when the right people are around.Level 1 · Repeatable — There is a way to do it, but it needs constant attention.Level 2 · Established — The way is set up, written down and followed.Level 3 · Built in — It is a property of the system, not an effort by individuals.
Next step
Related
Service:Kubernetes & Container Orchestration
Workshop:Kubernetes Operations
Cost management
Your level
Level 0 · Ad hoc — It works when the right people are around.Level 1 · Repeatable — There is a way to do it, but it needs constant attention.Level 2 · Established — The way is set up, written down and followed.Level 3 · Built in — It is a property of the system, not an effort by individuals.
Next step
Related
Service:AWS Cloud Architecture
Workshop:Cloud-Native Architecture
Developer experience
Your level
Level 0 · Ad hoc — It works when the right people are around.Level 1 · Repeatable — There is a way to do it, but it needs constant attention.Level 2 · Established — The way is set up, written down and followed.Level 3 · Built in — It is a property of the system, not an effort by individuals.
Next step
Related
Service:DevOps & Platform Engineering
Workshop:Platform Engineering Foundations
Reliability
Your level
Level 0 · Ad hoc — It works when the right people are around.Level 1 · Repeatable — There is a way to do it, but it needs constant attention.Level 2 · Established — The way is set up, written down and followed.Level 3 · Built in — It is a property of the system, not an effort by individuals.
Next step
Related
Service:Kubernetes & Container Orchestration
Workshop:Kubernetes Operations
Governance
Your level
Level 0 · Ad hoc — It works when the right people are around.Level 1 · Repeatable — There is a way to do it, but it needs constant attention.Level 2 · Established — The way is set up, written down and followed.Level 3 · Built in — It is a property of the system, not an effort by individuals.
Next step
Related
Service:Architecture Modernization
Workshop:Architecture Decision Workshop
Team capability
Your level
Level 0 · Ad hoc — It works when the right people are around.Level 1 · Repeatable — There is a way to do it, but it needs constant attention.Level 2 · Established — The way is set up, written down and followed.Level 3 · Built in — It is a property of the system, not an effort by individuals.
Next step
Related
Service:DevOps & Platform Engineering
Workshop:Kubernetes Operations
To be clear: this is an ordered self-assessment, not a finding and not an outside opinion. The number works as a basis for a conversation inside your own company — not as evidence towards customers, investors or auditors. Before you move budget, test the three areas above against your own numbers.
What makes sense after this
If you want to know whether your reading holds, the Platform Bottleneck Assessment is the next step. It covers the same areas — but against your pipelines, your cluster, your incidents and your cloud bill rather than a set of choices in a browser. Fixed scope, a written result, prioritized quick wins and a roadmap. If you would rather carry on alone, the services and workshops per area are linked above — that is a legitimate outcome of this page.