FinOps Operating Phases
The inform, optimise and operate cycle through which an organisation builds cost management into normal engineering practice.
FinOps is an operating discipline rather than a cost-cutting exercise, and it is defined by an iterative cycle rather than a project.
Inform. Visibility and allocation: tagging, per-team reporting, unit economics, forecasting and budgets. Nothing else works without it, and most organisations that believe they have a cost problem actually have an attribution problem.
Optimise. Acting on what visibility reveals: rightsizing, instance family and architecture selection, commitment purchases, storage lifecycle, waste elimination, and design changes that alter the cost curve rather than trimming it.
Operate. Making it continuous: budgets and guardrails, cost as a factor in design review, anomaly alerting, and regular review with named owners.
The principle that determines whether it works organisationally: engineering teams own their costs, with finance and a central FinOps function providing tooling, benchmarks and forecasting. A central team that attempts to optimise other teams' architectures has neither the context nor the authority, and it produces resentment and evasion.
The failure mode to avoid is the annual cost-cutting campaign: intense, disruptive, and followed by steady regrowth because nothing changed in how decisions are made day to day.