Personas
Personas, not job titles
The FinOps Framework defines personas as the roles that interact with technology cost and usage. A person can hold several personas, and one persona can span many job titles. Core personas include FinOps practitioners, engineering and operations, finance, procurement, product, technology leadership, and IT asset management. Each persona has different decisions, data needs, and incentives.
What each persona needs
Practitioners enable the practice: they build allocation, reporting, forecasting, and optimization routines. Engineers need timely, granular cost and usage data tied to services and changes so they can act. Finance needs accruals, budgets, forecasts, and variance explanations that reconcile to the general ledger. Procurement negotiates commitments, renewals, and vendor terms. Product owners connect spend to unit economics and customer value. Leadership needs decision-oriented summaries, risks, and trade-offs, not raw billing exports. ITAM aligns hardware, software, and licensing inventories with cost.
Traps
A common trap is assuming the FinOps team performs all cost work. Another is giving every persona the same dashboard. Questions may describe a persona by activity rather than title. Also watch for ignoring procurement and ITAM, which matter for commitments, SaaS renewals, and licensing.
Worked example / rule of thumb
An engineer asks for a daily service-level cost view; finance asks for monthly forecast-to-actual; an executive asks for cost per transaction and trend. Same data, different grain and framing. Rule of thumb: design for the decision, not for the data source. Ask what action the persona will take before choosing metrics, cadence, and granularity.