When good top-down structure is on the other side
People say, ‘I’m talking with AWS’. It sounds grown-up. It also hides the only thing that matters: you are talking with a human being who has a job title, a quota, and a limited amount of power.
Frank Contrepois
Top-down governance: why paperwork fails and how to enable innovation
Most organisations treat governance as paperwork to be completed before an audit. Policies, slide decks, control libraries and “principles” circulate widely.
Everything looks governed until someone tries to build something.
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
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.
Why most FinOps savings barely register in the boardroom
FinOps often celebrates savings that look big from engineering but invisible to executives. The “splash in the ocean” fallacy shows why bottom-up efforts fail. Only top-down intent turns scattered optimisations into meaningful, strategic impact.
(paid) Graph clarity toolkit
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.