It's not a quarterly review. It's not an optimization project. It's not something you do when the bill gets uncomfortable
It's the way a team thinks about resources by default
When an engineer spins up a new service and the first question they ask is "what will this cost to run and is that justified by what it delivers" - that's cost culture
When a developer sets a log retention policy without being asked because they know unretained logs are waste - that's cost culture
When a team lead reviews the impact on the cloud bill as part of the definition of done for a new feature - that's cost culture
The difference between teams with cost culture and teams without it is not that the first group cares about money more
It's that the first group has made cost visibility a default condition of how they work
You can't have cost culture without visibility. If engineers can't see what their services cost, they can't factor cost into their decisions. The information isn't there
You can't have cost culture without ownership. If cloud costs belong to "the company" or "DevOps" or "whoever handles billing", they belong to nobody. Cost culture requires cost ownership at the service level, the feature level, the team level
You can't have cost culture without psychological safety. If the only time cost gets discussed is when the bill is already too high, engineers learn that cost conversations are bad news conversations. They stop raising the issues they see early because raising an issue means being associated with a problem
Cost culture is built when people feel safe flagging inefficiencies before they become expensive
When the finding is celebrated, not interrogated
When "I found $800 a month we're wasting on this forgotten service" is received as a win, not a question about how it got there
The environment shapes the behavior
Build the right environment and the behavior follows



