The FinOps Paradox: To Scale Complexity, You Must Start Simple.
- Juanjo Palacios-CRRG
- Apr 3
- 2 min read
As a FinOps practitioner, I’ve realized that the most successful cloud transformations don't start with complex AI-driven forecasting or intricate unit economics. They start with simple (but reliable) systems that work.
There is a fundamental principle in systems theory known as Gall’s Law:
"A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works and cannot be patched up to make it work. You have to start over with a working simple system."
If your organization is in the "Crawl" phase (starting), don't feel pressured to run before you can walk. Your goal is not perfection; it’s building the foundational bases that allow complexity to grow later.
Here are the essential, Crawl-level KPIs that every persona should be able to see today through real-time observability tools:
1. The Engineering Lens: Tagging Hygiene
KPIs:
- % of Resources with Mandatory Tags (compliance).
- Untagged Resource Spend: A daily tracker of the "black hole" spend. Minimizing this last one is the first step towards accountability.
Why it matters: You cannot optimize what you cannot attribute. This is the "simple system" that makes all future reporting possible.
2. The Finance Lens: Unblended Cost Trends
KPIs:
- Daily Spend Variance (Alerting on ±15% spikes).
- Month-to-Date Spend vs. Previous Month:
A high-level pulse check for leadership to ensure there are no surprises at the end of the billing cycle.
Why it matters: Before deep-diving into amortization and accruals, Finance and IT need to catch "accidental" spend before it becomes a monthly disaster.
3. The IT Operations Lens: The "Zombie" Resource Count
KPIs:
- Cost of Unattached Storage and Idle IPs. (waste)
- Immediate Rightsizing Potential: Identifying the top 10 most expensive, underutilized instances (e.g., <5% CPU). We aren't optimizing everything yet (just the obvious outliers).
Why it matters: These are "safe" wins. Deleting a disk that isn't attached to anything doesn't break production, but it builds immediate credit for the team. Estimating rightsizing yields is also a great incentive.
4. The Executive Lens: Budget vs. Actuals
Metric: Total Monthly Spend vs. Forecasted Budget.
Why it matters: At the Crawl stage, Leadership needs confidence that the cloud isn't a runaway train. Visibility creates trust.
The Path Forward: By democratizing these simple metrics across the organization, you aren't just saving money—you are evolving the culture (remember "The Prius effect"?). Complexity will come in the "Walk" and "Run" phases, but only if your "Crawl" foundation is rock solid.
To my fellow FinOps practitioners: What was the first "simple system" you put in place that eventually evolved into something complex?
Comments