Part 10: Inform Phase Fundamentals

Main Idea

• The inform phase is where FinOps starts by asking questions, building context, and creating visibility.
• Its purpose is not just to collect data, but to interpret it well enough to guide future optimization and operating decisions.
• Organizations spend much of their FinOps effort here because strong visibility is the foundation for everything that follows.
• FinOps is a cycle, visibility in the inform phase leads to better optimization, which leads to better operating practices, which leads back to better visibility. etc etc.

Why the Inform Phase Matters

• FinOps is cyclical, not linear, so teams repeatedly return to inform as they mature.
• Jumping too quickly to optimization can create expensive mistakes.
• The inform phase helps teams measure first, understand root causes, and then act with better judgment.

Start with Questions

• The inform phase begins by asking practical questions about spend, allocation, ownership, and trends.
• These questions shape reporting, cost allocation, and the broader FinOps operating model.
• A strong question set helps organizations avoid trying to solve everything at once.

The First Question to Answer

• Start with total cloud spend, its forecast, and its growth rate.
• If cloud spend is not yet material to the business, only basic reporting may be necessary at first.
• This keeps effort proportional to business value.

Data Is Meaningless without Context

• Raw spend data is not enough on its own - you need to interpret it.
• Teams need shared context so finance, engineering, and business stakeholders can interpret the data consistently.
• Context improves trust in reporting and reduces the finger-pointing that often appears when teams are misaligned.
• Your goal here is to get some easy wins, tackle some low hanging fruit and gain credibility.

Seek First to Understand

• The first instinct is often to fix obvious waste immediately - a better approach is to ask where the waste comes from and why it happened.
• Understanding the root cause prevents the same issue from recurring later.

Stakeholder Interviews Matter

• One of the best ways to improve the inform phase is to talk directly with stakeholders.
• Their concerns reveal what should be reported, how allocation should work, and what level of accuracy matters.
• These conversations also help build a shared language for cloud financial management.

Questions to Ask Early

• What should spending be reported by: cost center, application, product, or business unit?
• Where is the bulk of spending coming from - which services, teams, or applications?
• Will the organization use showback, chargeback, or both?
• How accurate does allocation need to be at the current maturity level - to the penny?
• How will cost centers, teams, and applications be remapped as the organization changes, and how quickly can FinOps adapt?
• What about people that shift between teams? After the switch how will your team stay apprised of the changes and adapt accordingly?
• What tags are truly needed? Start small, add later when the process is working, and avoid overengineering your tagging strategy.
• How will people be informed when allocation constructs change?
• How will the organization build awareness and education around FinOps practices?

Questions Get Better Over Time

• As FinOps matures, the questions become deeper and more business-relevant.
• Teams begin asking about efficiency, unit metrics, budget management, activity-based costing, tag health, and commitment discount strategy.
• The goal is not to reach an endpoint, but to keep improving the quality of questions and answers over time.

Example questions:

• Which teams are driving the costs? Are they being efficient? Can you link their costs to unit metrics?
• Do you have budgets in place for each team? Are you managing teams to those budgets? Are you able to do activity-based costing?
• What is the state of your tagging strategy? Look at what tags are in place and what they are reporting. Look at coverage gaps. Consider how to allocate untaggable or shared costs.
• How will you keep your allocation constructs in sync and up to date? A spreadsheet? Cadence-based syncing with your CMDB? API integration between your FinOps platform and your CMDB?
• What is the commitment-based discount strategy? What commitment-based discount programs are there? How well are they being used?
• How could they be optimized? Which new ones should you make?

Low-Hanging Fruit Comes First

• The inform phase should focus on practical early wins.
• Teams often begin with visibility, then basic budgets, then stronger budget management, and then more advanced reporting and optimization loops.
• The winning FinOps culture is a village that works together, not a roomful of individuals who are trying to speed through some sweeping changes

Organizational Work in the Inform Phase

• Align executives around cloud-related goals and operating model changes.
• Help engineers understand cost as another important efficiency metric.
• Ensure the right FinOps skills exist on the team.
• Build partnerships with finance, engineering, architecture, procurement, product, security, and IT asset management.
• Evangelize FinOps internally through events, communication, and early wins.
• Let the central FinOps team manage as much rate optimization as possible while engineering teams manage usage optimization.

Transparency and the Feedback Loop

• Timely visibility changes behavior.
• The inform phase depends on a feedback loop where people can see their cloud usage and spending frequently enough to make better decisions.
• Reports should be available on the cadence that best supports real action, whether that means daily, weekly, or alert-based review.

Near-Real-Time Data Is Useful, But Pragmatic

• Cloud environments move too quickly for monthly-only visibility to be enough.
• At the same time, organizations should not overspend effort creating more real-time reporting than their processes can use.
• The right goal is frequent, useful visibility that supports action without overengineering the system.

Anomaly Detection Is Critical

• A core capability of the inform phase is identifying spend anomalies.
• Anomalies can appear as spikes, unusual slopes, or seasonality changes.
• Because cloud bills are large and complex, anomalies can hide inside broader spend movement unless teams actively monitor for them.

There's a nice story on page 237 about the importance of anomaly detection. A team had a spike in spend that they ignored because it was only a small percentage of their overall spend. However, that spike was actually a major dollar amount and represented a significant waste that could have been avoided if they had caught it sooner.

Managing Anomalies

• Have a solid cost allocation strategy.
• Review anomaly reporting frequently or triage it programmatically.
• Route anomalies to the team responsible for the spend.
• Follow a clear process for investigation and closure.

Why Anomalies Matter

• Even relatively small percentage changes can represent major dollar impact.
• Strong anomaly detection helps organizations catch problems before they become expensive long-running waste.
• Visibility into anomalies is one of the fastest ways to improve cloud cost awareness.

Benchmarking Team Performance

• Scorecards are one of the best ways to compare teams and identify opportunity.
• They help reveal which teams are efficient, which teams are lagging, and where executives should focus attention.
• Good scorecards create accountability and help teams improve through comparison and visibility.

Useful Scorecard Metrics

• Rightsizing efficiency.
• Commitment coverage and efficiency.
• Elasticity and the ability to scale resources up and down appropriately.
• Team-level and executive-level rollups for visibility across the organization.

What Great Looks Like

• High-performing FinOps organizations answer complex spend and forecast questions quickly.
• They understand how deployment changes affect unit economics.
• They retain granular data, allocate spend accurately, and use that visibility to identify targeted improvements.

Maturity Across Key Capabilities

Capability	Low Performer	Medium Performer	High Performer
Visibility and allocation	Relies on vendor invoices and manual reconciliation.	Has delayed or partial visibility with limited historical detail.	Has near-real-time visibility with current and historical spend retained.
Showback or chargeback	Cannot provide accurate team-level spend accountability.	Allocates spend using estimates.	Allocates spend to teams based on actual consumption.
Budgets	Teams have no budgets.	Teams have budgets.	Teams track spend actively against budgets.
Reservation and commitment management	Low use of reservations or commitments.	Moderate use of reservations or commitments.	Strong use of reservations or commitments across major services.
Underutilized service cleanup	Cleanup happens only occasionally.	Cleanup happens regularly.	Cleanup is automated or policy-driven.
Unit economics	May not use unit economics at all.	Uses technical unit metrics.	Uses business-oriented unit metrics such as cost per customer.

Business Value of a Strong Inform Phase

• Strong visibility improves competitiveness by supporting faster and smarter decisions.
• Leadership gains better understanding of cloud costs, COGS, and service economics.
• Teams know where to focus optimization work because they can see both spend and responsibility more clearly.

Strategic Lessons

• The inform phase is the natural resting state of the FinOps lifecycle.
• Context matters as much as the raw numbers.
• Mature FinOps practices ask better questions each time through the loop.
• Visibility, accountability, and shared understanding must come before more advanced optimization.

Key Takeaways

• Start FinOps by asking questions, not by rushing to make changes.
• Build context around spend data so different teams can trust and use it.
• Use feedback loops and anomaly detection to keep visibility actionable.
• Benchmark teams with scorecards to uncover improvement opportunities.
• Improve iteratively as maturity grows rather than trying to become high-performing immediately.

Conclusion

Glossary

Term	Definition
Activity-based costing	A costing approach that links spending to the activities or workloads driving that spend.
Anomaly detection	The practice of identifying unusual changes in cloud spend or usage patterns that may require investigation.
CCoE	A Cloud Center of Excellence, often used to promote standards, education, and best practices across cloud teams.
Chargeback	A model where cloud costs are billed back directly to the teams or business units responsible for using them.
CMDB	A configuration management database used to track assets, systems, and organizational mapping data.
COGS	Cost of goods sold; in cloud contexts, this can include the cloud cost associated with delivering a product or service.
Feedback loop	A process where timely data influences behavior and improves future decisions.
Inform phase	The FinOps lifecycle phase focused on visibility, context, allocation, accountability, and understanding.
Low-hanging fruit	Simple, high-value improvements that can be achieved early in a FinOps practice.
Near-real-time visibility	Cloud spend and usage visibility that is updated quickly enough to support practical decision-making.
Scorecard	A benchmarking tool used to compare teams across efficiency, optimization, and cost metrics.
Seasonality	A repeating usage or spending pattern that occurs over time and can affect anomaly detection.
Showback	A reporting model that exposes team-level cloud costs without formally billing them back.
Unit economics	Cost measures tied to a business outcome, such as cost per customer or cost per transaction.