The objection I hear most often when talking about cost culture with engineering teams
"We move fast. Adding cost review to everything will slow us down"
It's a legitimate concern. It just isn't what actually happens
The teams that move fastest are usually the ones with the clearest understanding of their infrastructure. They know what's running. They know what it costs. They know what it does. When something breaks they know where to look. When they need to scale they know what to scale
The teams that slow down under cost review pressure are the ones where cost review is adversarial
Where an engineer who deploys something that costs more than expected gets questioned instead of the decision getting examined
Where the cost conversation happens after the fact as a performance issue instead of during design as a planning input
Cost culture done right doesn't slow teams down. It adds one question to decisions that are already being made
Before: "does this work?" and "does this ship on time?"
After: "does this work?", "does this ship on time?", and "does this make sense to run at this cost?"
That third question takes 60 seconds to answer for most decisions. The answer is obvious almost every time: yes, it makes sense. The question gets asked. The answer is yes. Everyone moves on
The rare cases where the answer is "actually, no" - those are the cases that prevent the $2,000 a month services that nobody was using showing up on the bill six months later
One minute per decision to catch the ones that matter
That's not slowing down
That's building the habit that means you never need to stop and do a two-week optimization sprint because the bill is out of control again

Top comments (0)