Three Audience, Three Dashboards
The biggest mistake in FinOps dashboard design: building one dashboard and expecting everyone to use it. Engineers, finance, and executives have fundamentally different questions. Build three distinct views sharing the same underlying data.
Engineering Dashboard
Engineers need to understand the cost impact of the systems they own and see anomalies quickly. Optimal refresh: daily or near-real-time.
Key panels:
- Cost by service/namespace this week vs last week — delta view catches regressions from recent deployments
- Top 10 most expensive resources — name, type, owner tag, cost/day
- Anomaly alerts feed — resources with >20% cost increase day-over-day
- Spot/on-demand ratio — is the Spot fleet healthy?
- Untagged resources count — hygiene metric; should trend toward zero
- RI/SP coverage and utilization — are commitments being used?
Show engineers their team's cost trend, not total company spend. People respond to data they feel ownership over. "Your team spent $14,200 last week, up 8% vs prior week" is actionable. "$450K total cloud spend" is not.
Finance Dashboard
Finance needs budget governance, variance analysis, and forecast accuracy. Optimal refresh: weekly or monthly.
Key panels:
- Budget vs Actual vs Forecast — current month, with projected end-of-month
- Cost by business unit/cost center — aligned to the P&L structure finance already uses
- Month-over-month variance with explanations — annotated with known drivers (new product launch, seasonal traffic, pricing changes)
- Chargeback report — how much each team/product owes for shared services
- Committed spend vs variable spend split — how much is fixed (RIs) vs variable (on-demand)
- Savings realized YTD — total optimization savings vs baseline
Executive Dashboard
Executives need business context, not raw cloud metrics. One page, five numbers. Optimal refresh: weekly.
Key panels:
- Infrastructure Cost Ratio — cloud spend as % of revenue, trending
- Cost per customer/unit — the most important business metric
- Budget status — simple red/amber/green vs monthly budget
- Savings delivered this quarter — ROI of the FinOps practice
- Forecast vs budget for Q — will we hit our cloud cost targets?
Dashboard Tooling Options
| Tool | Best For | Cost | Effort |
|---|---|---|---|
| AWS Cost Explorer | AWS-only, starting out | Free | Low |
| Grafana + CloudWatch | Engineering dashboards | Free/OSS | Medium |
| Looker Studio | Finance/exec reporting | Free | Medium |
| CloudHealth | Enterprise multi-cloud | $$$ | Low |
| Datadog | Observability + cost unified | $$ | Low |
| Custom (BigQuery + Looker) | Full flexibility | $$ | High |
Common Dashboard Mistakes
- Too many metrics: If everything is on the dashboard, nothing is the dashboard. Limit to 6–8 panels per audience.
- No context for numbers: "$45,200 last week" means nothing without last week's number or a budget target. Always show relative change.
- Raw cloud metrics for finance: Finance doesn't know what "EC2 BoxUsage:r5.2xlarge" means. Translate to business language.
- No ownership data: Cost without an owner creates diffuse responsibility. Every panel should point to a team or individual accountable for the number.
- Not automating distribution: A dashboard nobody opens is worthless. Schedule weekly email reports or Slack digests pushing key metrics to relevant teams.
// FAQ
How long does it take to build a good FinOps dashboard from scratch?
With a platform like CloudHealth or Datadog: 1–2 weeks to configure meaningful dashboards. With custom tooling (BigQuery + Looker Studio): 4–8 weeks for a production-quality implementation. The engineering dashboard is fastest; the finance dashboard requires reliable cost allocation data first.
Should dashboards be real-time or daily?
Engineering anomaly detection: as close to real-time as your billing data allows (AWS CUR updates every 8 hours; GCP billing exports update daily). Finance and executive dashboards: daily or weekly is sufficient — the data doesn't need to be real-time for budget governance.