How to Execute Cost Optimization Recommendations

#finops #finopsfoundation

We often think of the process of optimizing resources and technology infrastructure as a constant battle between FinOps teams and technology teams (and sometimes it is). However, after several years working in the field, I’ve discovered some key dynamics that help deliver recommendations without falling into unnecessary workplace conflicts (so no one ends up losing their hair over it).

Here’s a brief overview:

First, remember that every company’s infrastructure—every project, and even every department—is different. For this reason, I strongly recommend conducting thorough analyses based on the actual consumption patterns of your infrastructure. Avoid making generic recommendations commonly found online, such as implementing Saving Plans without proper evaluation, or proposing modernization efforts without analyzing the specific requirements or characteristics of your infrastructure.
Take into account the operational periods and environments where you plan to implement changes. For example, if you host an e-commerce platform, it’s not advisable to make changes in production environments during peak demand periods such as major sales events or product launches. The same applies to environments: it’s not ideal to purchase long-term committed resources for environments or resources that will be removed once testing is completed.
Explore your resources and map them to their respective teams in order to connect actions, infrastructure characteristics, and policy alignment with the users responsible for them. Get to know your teams as well as possible and build strong relationships with them—remember, FinOps works best when approached with a calm and collaborative mindset.
Look for alternative infrastructure options, services, deployment models, providers, and other operational details. This will allow you to introduce changes when they are truly relevant and beneficial.
Promote the adoption of the methodology from a perspective of agility, not just speed driven by artificial intelligence or other automation technologies.
Finally, focus on translating FinOps outcomes into meaningful actions for teams. At the beginning, don’t focus solely on performance metrics or indicators—prioritize the level of ownership and adoption of those indicators by the teams involved.