High-Frequency Scenario Patterns

The 10 High-Frequency Patterns

• Visibility before optimization: any scenario where an organization wants to optimize without having visibility first—the answer is always build visibility first.
• Showback before chargeback: when Finance wants chargebacks but allocation isn't accurate yet—the answer is showback first with a chargeback roadmap.
• Centralized team enables distributed ownership: apparent tension between central FinOps team and team-level ownership—the answer is the central team provides tooling, teams own decisions.
• Right-size before commit: organization wants to buy Reserved Instances without baseline data—the answer is establish usage baseline first.
• Maturity-appropriate solution: a Run-phase solution offered to a Crawl-phase organization—the answer is always the simpler, more manual option.
• Engineer-friendly accountability: teams not acting on cost signals—the answer is improve signal delivery (timing, format, channel) not enforcement.
• Unit cost over absolute cost: a rising absolute bill is framed as a problem—check if unit cost is actually improving before recommending cuts.
• Shared cost allocation dispute: teams arguing over shared cost allocation—the answer is agree on allocation methodology transparently, not eliminate shared costs.
• Anomaly before optimization: cost spike detected—investigate and resolve the anomaly before starting optimization work.
• Collaboration before unilateral action: any scenario where one team acts alone on a cross-functional cost problem—the answer is engage all affected parties first.