Latest
AWS sells to the tribe, not the board
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.
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.
𝗔𝗪𝗦 𝗷𝘂𝘀𝘁 𝗿𝗼𝗹𝗹𝗲𝗱 𝗼𝘂𝘁 𝘁𝗵𝗿𝗲𝗲 𝗽𝗿𝗶𝗰𝗶𝗻𝗴 𝘁𝗶𝗲𝗿𝘀 𝗳𝗼𝗿 𝗚𝗲𝗻𝗔𝗜 𝗶𝗻𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝗼𝗻 𝗕𝗲𝗱𝗿𝗼𝗰𝗸: 𝗺𝗼𝗿𝗲 𝗳𝗹𝗲𝘅𝗶𝗯𝗶𝗹𝗶𝘁𝘆, 𝗯𝘂𝘁 𝗮𝗹𝘀𝗼 𝗺𝗼𝗿𝗲 𝗼𝗽𝗮𝗰𝗶𝘁𝘆
AWS Bedrock adds Priority, Standard, Flex. Priority: lower latency, ~60–90% pricier. Standard: predictable baseline. Flex: ~50% of Standard, slower. Anthropic stays Standard. Choose by latency vs. cost; benchmark and classify workloads for optimisation discipline.
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.