FinOps Foundations · Module 05

Manage the FinOps Practice

Make FinOps last: run it as an operating rhythm with clear roles, govern spend with policies and guardrails instead of approvals, move from showback to chargeback when the data is ready, and automate the repetitive work with tools.

Practice interactively →

What you will learn

• Set up a FinOps operating cadence, roles and practice goals
• Apply governance with tagging, budget and resource policies that guide rather than block
• Design showback and chargeback with cost categories and shared-cost rules
• Choose and automate FinOps tooling, from native consoles to policy-as-code

Lessons

1. Running the Practice: Cadence, Roles and Goals

   A FinOps practice runs on a rhythm — daily anomaly checks, weekly team reviews, monthly business reviews, quarterly planning — with a small central team, team champions, executive sponsorship and measurable goals.

2. Governance, Policy and Guardrails

   FinOps governance sets the rules for spending — required tags, allowed regions and sizes, budget thresholds, commitment approval — and enforces them with preventive and detective guardrails rather than manual approvals.

3. Invoicing, Showback and Chargeback

   Invoicing reconciles provider invoices with allocated cost; chargeback moves that cost into team or product budgets using agreed rules, cost categories and shared-cost splits — once allocation is trusted.

4. Automation, Tools and Services

   Automate what repeats — scheduling non-production, cleaning up orphans, tag remediation, reports and alerts — with native schedulers, serverless functions and policy engines like Cloud Custodian, and pick FinOps tools by the data and decisions they support.