Career4 min
I made a mistake in production: how to communicate and help resolve it
A practical playbook for critical moments: how to contain immediate impact, communicate with facts without panic, and turn incidents into technical maturity.
Food service & retail
−50%in cloud costs
Half the cloud bill.
Architecture review across Azure and GCP, costs split by application and right-sized databases.
Cloud cost (baseline = 100)
- Before
- 100
- After
- 50
Engineering decisions+
Cost per application:No visibility Split by application
Context and constraints
National multi-unit food service and retail group with workloads spread across Azure and GCP. The bill did not show what each application cost, which made it impossible to decide where to cut.
Alternatives and decision
Architecture review on both clouds, cost categorization by application and database right-sizing. Financial governance became part of the team’s engineering standard.
Baseline and measurement
50% reduction in cloud costs compared with the period before the project. Absolute values withheld for confidentiality.
Transferable lesson
Cloud costs only fall sustainably when every application has an owner and cost becomes part of the engineering routine.
