How FinOps thinking is evolving: from frameworks to pathways
FinOps is evolving fast. The Foundation sets the framework; Carlo Wejszko’s pathways add the missing sequence. This new layer—Context → Scopes → Maturity → Pathways—shows how practitioners can turn structure into real progress.
When I published FinOps wants to eat the world (but most practitioners are still chewing cloud), I wasn’t trying to add yet another model to the FinOps ecosystem.
My point was that the FinOps Foundation is formalising the future—building the frameworks, standards, and vocabulary that will shape how every practitioner works.
That’s fantastic for the field.
But for people entering FinOps, it can also feel overwhelming. There’s a framework, capabilities, domains, and maturity levels to navigate—yet little guidance on where to start or in what order to act.
So I proposed a way to move forward:
take the FinOps Framework, highlight in red the level of maturity you want to reach for each capability and use black to show where you are now. Use that as your personal roadmap, turning a vast reference model into something you can work with, and grow into.
