Cloud costs touch more stakeholders than most engineering projects
And those stakeholders care about very different things
The engineer running the optimization work cares about technical correctness. Is the rightsizing safe? Are the lifecycle policies configured correctly? Will the changes cause any issues?
The engineering manager cares about risk and velocity. Will this break anything? How much time will it take? What else gets delayed while this happens?
The CFO or finance team cares about one thing: when does the bill go down and by how much? They don't understand the technical mechanism. They understand the number and the timeline
The founder or CEO cares about runway. How much longer does this give us? Does this change what we can do next quarter?
The problem with most cost optimization work is that it's communicated in the language of the person doing the work. Technical findings presented to non-technical stakeholders. Savings projections presented without confidence intervals to people who need to make budget decisions
The work gets done. The communication fails. The impact is smaller than it should be because nobody fully understood what happened or why
What actually works is translating the same information into the language of each stakeholder
To engineering: here are the specific changes, the risk level for each, the rollback plan, and the monitoring approach
To the engineering manager: here's the scope, the timeline, the risk to other work, and why it's worth prioritizing now
To finance: here's the current monthly cost, here's the projected cost after changes, here's when the changes will be complete, and here's the confidence level on the projection
To the founder: here's what this does to the runway number and what it makes possible that wasn't possible before
Same work. Four different translations
The teams that get organizational support for cost optimization are the teams that learned to make those translations
The ones that don't are still waiting for someone to understand why their spreadsheet matters
Top comments (0)