Latest
Culture is the quiet context
Context, scopes, maturity and pathways: how FinOps adoption really starts
FinOps adoption starts with context, moves through scopes, defines maturity and follows pathways. This layered model turns the Foundation’s framework into a practical plan that fits intent, not theory.
The simple way to make your FinOps reporting more relevant to executives and boards
In FinOps reports the narrative is often inexistant or only about the data. Too far from what executives need. There is a solution, and it is not technical.
How to keep track of ephemeral VMs
Tracking ephemeral VMs is hard: they appear, run briefly, and vanish before most tools detect them. The result is missing context, incomplete CMDBs, and charges with no trace of what created them. FinOps teams need better ways to capture these short-lived resources.
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.
