Founder @turbothq. Building @steampipeio, @flowpipeio, @powerpipeio, @tailpipeio. Father, husband, traveler, nerd, đ-lover.
Maplewood, NJ
Joined August 2007
- Tweets7.1K
- Following1K
- Followers489
- Likes736
Nathan Wallace retweeted
Serious question,
I Love any Trump getting his payback but what Jurisdiction does the BBC have?
Cloud Governance and GRC aren't the same thing.
GRC documents what should happen and proves what did happen. Risk registers, control libraries, audit trails â it's a lagging indicator. The business already made its choices.
Cloud Governance is different. It's not just describing rules â it's deploying them.
Setting guardrails, enforcing policies, nudging teams, blocking risks. It's proactive. It changes the path before the train leaves the station.
The Head of Cloud isnât really in charge. Theyâre not the President. Theyâre the Chief of Staff. No final say, no official control. But somehow, theyâre still responsible for everything running smoothly.
They donât own the budget. They donât own the teams. They donât get to make a decision and slam the table. But they shape the agenda. Build coalitions. Keep the big wheels turning while the chaos swirls. They know where the risk is hiding and whoâs pretending itâs not.
You can have the right intentions: secure the cloud, reduce cost, move fast.
But without governance, things drift. Exceptions pile up. Good ideas go rogue.
If you're on the cloud team, you own the bill. You're expected to explain every charge. You're responsible for every $ â because itâs easier.
Until you have a system to track and allocate spend, every cost is yours.
Tags. Accounts. Metadata. Good governance is the only way out.
The best governance ideas donât fail because theyâre flawed.
They fail because theyâre abandoned.
Focus on function, not form. Build things that get used.
(Inspired by an early morning walk across the abandoned Memphis monorail bridge.)
LLM results depend on two things:
đ§ How smart the model is
đ How well you brief it
Model quality? Thatâs up to OpenAI and friends.
Context? Thatâs your job.
Want Jedi-level performance?
Be like Luke: bring the force and the facts.
FinOps changes happen faster than security. Why? Incentives.
Budget is your problem and opportunity.
But, security is everyoneâs problem â which often means it's no one's.
Blow the budget? It hits your team, your goals, your bonus. Fix it and you see the win.
Fix a security issue? Best case: nothing happens. Worst case: someone else deals with the fallout.
The toughest Cloud Governance problems arenât technical - theyâre human. Our new book How to Herd Clouds and Influence People follows Gary, a cloud architect navigating chaos, silos & shifting priorities. Feel his pain, and joy, of driving real change đ
cloudgovernance.org/library/âŚ