Which approach best supports cost governance to prevent cost overruns in a multi-team environment?

Which approach best supports cost governance to prevent cost overruns in a multi-team environment?

• A. Rely on a single company-wide budget with no per-team controls
• B. Use per-incident budgets that reset daily
• C. Define budgets by team, enforce tagging, require approvals for high-cost changes, create automation to shut down idle resources, establish escalation path
• D. Track costs with monthly reviews and no automation

Answer: (C)

In cost governance for a multi‑team setup, the strongest approach ties budgets to each team, uses tagging to accurately allocate costs, requires approvals for high‑cost changes, builds automation to shut down idle resources, and defines a clear escalation path. This combination creates clear accountability—each team manages its own spend, and tagging ensures every dollar is attributed to the right team or project. Approvals for significant changes act as a proper guardrail so surprising or runaway costs don’t slip through, while automation handles routine waste prevention by stopping idle resources without waiting for manual intervention. An escalation path ensures overruns don’t go unchecked and that corrective actions happen quickly. Other approaches miss essential safeguards. A single company‑wide budget with no per‑team controls hides spend drivers and makes it hard to pinpoint overruns or hold teams accountable. Per‑incident budgets that reset daily are impractical and can disrupt legitimate work while still failing to prevent frequent overspending. Monthly reviews with no automation allow cost drift to continue unchecked, delaying detection and remediation.

In cost governance for a multi‑team setup, the strongest approach ties budgets to each team, uses tagging to accurately allocate costs, requires approvals for high‑cost changes, builds automation to shut down idle resources, and defines a clear escalation path. This combination creates clear accountability—each team manages its own spend, and tagging ensures every dollar is attributed to the right team or project. Approvals for significant changes act as a proper guardrail so surprising or runaway costs don’t slip through, while automation handles routine waste prevention by stopping idle resources without waiting for manual intervention. An escalation path ensures overruns don’t go unchecked and that corrective actions happen quickly.

Other approaches miss essential safeguards. A single company‑wide budget with no per‑team controls hides spend drivers and makes it hard to pinpoint overruns or hold teams accountable. Per‑incident budgets that reset daily are impractical and can disrupt legitimate work while still failing to prevent frequent overspending. Monthly reviews with no automation allow cost drift to continue unchecked, delaying detection and remediation.