Hey, Xaviour here. I've talked to many many CTOs about this matrix recently. About the obvious duality of velocity and reliability. About the realisation that speed and reliability were never enemies, that they feed each other. Everyone has either already come to this conclusion or their eyes light up as soon as I say it.
The trouble is the agreeing is the easy part. Almost every team I sit with reckons they're already top-right or basically there, and then the numbers tell a different story.
The one I keep coming back to is the CTO who called his team "top-right, easily," until we pulled the numbers and three of their last five "green" deploys had been quietly hot-patched in the hours after they went out. Their tooling was fine. What they had was a team that had normalised shipping things half-cooked because nobody felt safe slowing down. Getting faster and safer is almost always more of a cultural problem than a technical one, and culture doesn't show up in your CI dashboard.
So I made this. No quiz, no maturity scorecard, just a plot you drop your own numbers into and see where the dot lands. Its a simple invented standard thats in and of itself halfway to a meme. But these things matter and most good metrics cut with occam's razor. I hope you find a conversation worth having in the gap between the quadrant you want to be in and the one your data puts you in. Most teams I work with would rather see it on a graph than hear another consultant explain it at them.