Sign in Subscribe

The context

The context

In-depth essays and videos exploring the ideas shaping FinOps. Each month focuses on one theme, unpacking patterns, practices, and human stories that reveal how technology, finance, and culture intersect.

FinOps wants to become a discipline, but most teams are still a heroic side quest

FinOps wants to become a discipline, but most teams are still a heroic side quest

Cloud cost management won’t scale as a heroic side-quest run by one FinOps practitioner. Borrow proven management systems, give FinOps a mandate, and add programme management so dashboards turn into decisions, and decisions turn into delivery.

The Shape of Top-down FinOps

The Shape of Top-down FinOps

FinOps fails when it starts at the bottom. Top-down FinOps ties every optimisation to strategy: leadership sets intent, platform allocates time, managers put work in the backlog, and engineers deliver with recognition. That is how cloud savings become real impact.

(paid) Graph clarity toolkit

Why architecture fails to impress executives, and how the FC method solves it

Why architecture fails to impress executives, and how the FC method solves it

Most architecture diagrams fail because they show components, not meaning. The FC method fixes this by mapping use cases and shaping components by cost, revealing how value flows, where money goes and how intent becomes architecture, risk and spend.

(Sub) Are you throwing numbers at people, or telling them a story they can actually use?

(Sub) Are you throwing numbers at people, or telling them a story they can actually use?

Top-down FinOps: why leadership sets the frame

Top-down FinOps: why leadership sets the frame

Top-down FinOps aligns cloud economics with leadership intent. It connects technical decisions to margin, risk and runway, turning cloud from a collection of local choices into a strategic lever. Clear boundaries, better language and smart representation make the work matter.

What's in for you

What's in for you