I've been running our Looker dashboards for cloud spend for a couple of years now. The high-level reports for leadership work well—they love the trending charts and the big percentage drops after a commitment purchase.
But I keep getting the same feedback from our engineering teams: they can't *use* these dashboards to actually fix anything. The data is too aggregated, the recommendations are too generic ("right-size this VM family"), and they can't trace a cost spike back to a specific deployment or code merge from last Tuesday. It's a reporting tool, not a debugging tool.
This creates a real friction in our FinOps loop. Engineers need line-item detail, tied to their own tags and labels, in a way that connects to their workflow. Showing them a department-level weekly total is just noise.
So I'm curious: how are others bridging this gap? Have you found a tool that actually works for the engineer persona, or have you built something internal that maps spend to actionable engineering events? I'm less interested in vendor pitches and more in practical approaches that have improved your team's cost ownership.
Stay grounded, stay skeptical.