An enterprise is deciding between showback and chargeback for cloud costs. What does each achieve, and what goes wrong with chargeback?

What each achieves

Showback reports cost to the consuming team without moving money. It creates visibility and, in most organisations, most of the behaviour change — because engineers seeing an unexpected number act on it.

Chargeback actually transfers cost to the consuming unit's budget. It creates genuine accountability and makes cost a real constraint on decisions, because the money comes from somewhere the team feels.

What goes wrong with chargeback

1. Optimisation for the metric rather than the outcome. A team charged for compute will move work to a place that is not charged — an untracked environment, a shared cluster, a colleague's account — which increases total cost while improving their number.

2. Disputes consume the value. Apportionment of shared costs becomes a negotiation. Time spent arguing about the allocation model exceeds the savings, and the finance and engineering relationship degrades.

3. Under-investment in shared platforms. If a platform team charges its consumers, teams build their own to avoid the charge, fragmenting the estate — the opposite of the intended effect.

4. Perverse reliability incentives. A team charged for infrastructure may cut redundancy or headroom to reduce its number, with the cost of the resulting incident borne by the business rather than by the team. This is the most dangerous failure mode.

5. It requires accuracy chargeback cannot have. Moving money demands defensible numbers, and shared-cost apportionment is inherently approximate. The gap between required precision and achievable precision is where the disputes live.

The workable position

Showback with accountability, chargeback only where consumption is genuinely discretionary and attributable.

• Showback everywhere, with cost visible to the creating team daily and included in planning.
• Budgets and targets owned by engineering leaders, with variance explained — accountability without the distortions of money movement.
• Chargeback for clearly attributable, elective consumption: a team's own non-production environments, a specific product line's dedicated infrastructure, licences bought for one group.
• Shared platform costs funded centrally, so teams are not incentivised to avoid the paved road.

The principle

The objective is behaviour change, not cost recovery. Showback usually achieves most of the behaviour change at a fraction of the organisational cost. Chargeback is worth its friction only where the consumption is genuinely elective and the attribution is genuinely defensible — and those two conditions are rarer than finance teams expect.