Finance can see cloud spend. Engineering can change it. FinOps lives in the gap, and the gap is not a reporting gap, it is a product gap.
The metric nobody owns
A monthly invoice is not a metric anyone can act on. Cost per tenant, per request, per model call is. Once you name a unit, the number stops being a bill and starts being a design constraint.
Treat the dashboard as a product
The teams that actually improved their spend treated their cost view like an internal product: a named audience, one primary question per screen, and definitions written down so a number meant the same thing in two meetings.
What to try first
- Pick one unit metric and publish its definition
- Give it an owner who can change the system, not just report on it
- Review it in the same meeting where roadmap trade-offs already happen