FinOps Health Check, Part 2: From Findings to a 90-Day Savings Plan
• 7 min read
In Part 1 we baseline KPIs, tagging, and anomalies. Here, we turn those insights into a prioritized 30/60/90 plan with quantified impact, confidence, owners, and guardrails—so savings actually land.
1) Shape findings into candidate actions
Pull from four streams: rightsizing/scheduling, storage lifecycle & tiers,purchase strategy (SP/RI/commit), and governance guardrails. Each action should have:
- Impact (monthly \$ or %)
- Confidence (High/Med/Low with why)
- Owner (team + person)
- Prereqs (tag coverage, dashboards, approvals)
2) Score & rank
We use a simple model: Score = Impact × Confidence ÷ Effort
. Keep the math boring and the rationale explicit. The top 10 candidates usually explain 70–80% of near-term savings.
3) Build your 30/60/90
- 30 days: Low-risk rightsizing, schedules, obvious tiering, guardrail alerts.
- 60 days: Purchase strategy (SP/RI/commit) with staged coverage. Update budgets & KPIs.
- 90 days: Tagging standard rollout, anomaly process, dashboards for unit economics.
4) Prove it monthly
Publish a one-pager: actions shipped, realized \$, KPI deltas, and the next month’s plan. Executives want trajectory, not a one-off.
A lightweight template
Action: EBS gp2 -> gp3 Owner: Platform (Alex) Impact: $22k/mo | Confidence: High | Effort: Low Prereqs: None Guardrail: Alert if gp3 price > gp2 by 15% on any account
Want a guided 2–3 week baseline with a ready-to-ship 90-day plan? Start with a FinOps Health Check or book a call.