The Showback Rebellion
A fintech startup has grown to 300 employees and $5M monthly cloud spend. The CFO introduced showback reports by team, but engineering leaders pushed back, claiming the reports are inaccurate and don't reflect their actual usage. The FinOps team used a simple tagging strategy, but many resources are untagged or mis-tagged. Additionally, the shared platform team's costs are allocated based on headcount, which engineering argues is unfair because some teams use more platform services. The CFO is frustrated and considering chargeback to force accountability. The FinOps team needs to improve the showback process to gain buy-in and decide whether to move to chargeback. They have 2 months to present a revised approach.
1. Diagnose the issues with the current showback process and propose improvements to increase accuracy and trust.
Read the worked answer
Issues:
- Inaccurate tagging: Untagged/mis-tagged resources lead to incorrect allocation. Solution: Implement automated tagging via IaC and policies, and use Cloudability's tag governance to enforce.
- Unfair shared cost allocation: Headcount-based allocation doesn't reflect consumption. Solution: Allocate shared platform costs based on actual usage metrics (e.g., API calls, storage, compute hours) tracked via Cloudability's business mapping.
- Lack of transparency: Teams don't understand the methodology. Solution: Publish a clear cost allocation policy and provide drill-down reports.
- No accountability: Showback without consequences may be ignored. Solution: Introduce a chargeback model gradually, starting with a pilot for one team.
Improvements:
- Run a tagging cleanup sprint.
- Implement a shared cost allocation model based on usage drivers.
- Provide self-service dashboards for teams to see their costs.
- Establish a FinOps council with team reps to co-design the process.
2. Should the company move to chargeback? What are the pros and cons, and what prerequisites are needed?
Read the worked answer
Pros: Chargeback drives accountability, encourages cost optimization, and aligns spending with budget owners. Cons: Can create friction, requires accurate allocation, and may lead to under-utilization if teams avoid shared services. It also requires finance integration and may be complex to administer.
Prerequisites:
- High allocation accuracy (>90%).
- Clear, agreed-upon allocation methodology.
- Automated billing integration.
- Executive sponsorship and team buy-in.
- A dispute resolution process.
Recommendation: Don't move to chargeback yet. First, fix showback accuracy and build trust. Pilot chargeback with one willing team for 3 months. Use Cloudability to simulate chargeback impacts. If successful, expand gradually.