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 …
Connections
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.
In the comments, Carlo Wejszo, a FinOps expert, commented on LinkedIn, linking to an article he had already written: Pathways to FinOps Adoption.
His post actually came first—and it touched the same nerve:
the missing piece isn’t the framework, it’s the sequence.
Where my focus was on choosing how mature you want to be for each capability, Carlo’s focused on the order of execution.
He defined a series of adoption patterns, self-funding, visibility-first, control-focused, and more, each representing a practical way to roll out FinOps.
It’s a deeply software-like mindset: identify repeatable patterns, package best practices, and assign an order. Pragmatic, composable, and exactly what practitioners need.
Reading Carlo’s work again through that lens made everything click.
What if we layer the approaches?
Context → Scopes → Maturity → Pathways
- Context defines why you start.
- Scopes define where you apply FinOps.
- Maturity defines how far you want to go.
- Pathways define the order to get there.
Together, these layers form a single, human-scale way to approach FinOps adoption—one that honours the Foundation’s framework but makes it usable for every practitioner.
This short piece is the prologue to the main article:
Pathways, scopes, and context: how FinOps adoption really starts.
That article lays out the full model, ten adoption patterns, and the plan to connect them into practical guides.