Inform: what visibility actually means

Outcome

By the end of this lesson, you will be able to distinguish raw visibility from actionable visibility, and design a cost reporting cadence that fits each audience.

1. Concept

Inform is the first phase of the FinOps lifecycle. It answers the question: who knows what about cloud spend, when, in what form, and with what action available? Most FinOps initiatives stall here because raw visibility is mistaken for actionable visibility.

Raw visibility vs. actionable visibility

RAW VISIBILITY                     ACTIONABLE VISIBILITY
────────────────────────────────────────────────────────────────────
A dashboard exists                 The dashboard is opened weekly
The bill is exportable             The bill is parsed by someone who owns the cost
There is a cost report             The report carries a verdict ("we are over budget")
You can see your team's spend      You can compare your team's spend to peers
There is a Slack alert             The alert names a specific action and an owner

The difference is whether the data leads to a decision. A dashboard that nobody opens is not visibility. A weekly report that is forwarded but not read is not visibility. A Slack channel where alerts pile up is not visibility.

The three audiences

Inform fails when one report tries to serve three audiences. Engineering, finance, and leadership each need a different cadence, granularity, and shape.

Trying to serve all three from one dashboard produces a tool that nobody uses. The engineer needs more granularity than the CFO can absorb. The CFO needs more business framing than the engineer wants to maintain.

The four cost-data shapes

Inform produces data in four shapes. Each fits a different decision.

1. Snapshot. “What did we spend last month?” Single number. Useful for top-line communication. Useless for drilling.

2. Trend. “Are we going up or down?” Time series. Useful for catching slow drifts. Misses sharp events.

3. Breakdown. “Where is the money?” Stacked bar or Sankey. Useful for understanding composition. Misses outliers within a stack.

4. Anomaly. “What changed unexpectedly?” Per-dimension deviation alert. Useful for catching sharp events. Useless without root-cause attribution.

A healthy Inform practice produces all four. Most practices produce one or two.

The cadence test

For each cost surface in the organization, answer two questions:

• Who reads this?
• What decision do they make after reading it?

If the answer to either is unknown, the surface is not yet earning its keep. Either find the audience and the decision, or retire it.

What “accurate” means in the Inform principle

Principle 4 emphasizes cost data that is accessible and timely (the canonical wording); accuracy is the practical third leg this lesson adds. Accuracy in cloud cost is a band, not a point. Live calculated cost is the list (rack) price: the calculation itself tracks the pricing API to within a few percent, but rack rate can sit 20–40 percent or more ABOVE billed cost, because the gap between them is exactly your discount stack (commitments, Spot, sustained-use, EDP). Do not read rack rate as within a few percent of what you pay. Daily billing cost is accurate to within ~1 percent of monthly settled. Monthly settled is the closed invoice.

Each band serves a use. “Accurate” means knowing which band you are looking at and labelling it. (See M0.1 L3.)

2. Demo

The same monthly spend question, three audiences, three different surfaces:

Engineering (daily, self-serve):

Dashboard: live cost trend by service, grouped by team. Filter to “my team.” Anomaly markers on the chart. Click a marker → root-cause panel.

Engineering leadership (weekly, one-page):

Email-friendly report: total bill, week-over-week change, top three movers (up and down), open recommendations with savings totals.

Finance (monthly, one-page):

PDF or shareable URL: total spend, variance vs. budget, cost-per-MAU trend, top three cost centers, forecast for next quarter with confidence band.

Same underlying data. Three rendered surfaces. Three usable decisions.

3. Hands-on (6 min)

For each of the three audiences in your organization, answer:

1. What cost surface does this audience use today?
   Engineering team:     ________________
   Engineering leader:   ________________
   Finance / leadership: ________________

2. What is the read cadence?
   Engineering team:     ________________
   Engineering leader:   ________________
   Finance / leadership: ________________

3. What decision does each one make from it?
   Engineering team:     ________________
   Engineering leader:   ________________
   Finance / leadership: ________________

For any cell where the cadence is “rare” or the decision is “none,” the surface is failing. The fix is either to find the right shape, the right granularity, or to retire the surface and replace it with one that fits.

4. Knowledge check

Q1

A monthly cost report is sent as a PDF to engineering teams. Most teams do not open it. Best diagnosis:

A. Engineering teams do not care about cost
B. The shape and cadence are wrong for the audience. Engineering needs daily, self-serve, per-resource granularity. A monthly PDF is finance-shaped.
C. The PDF is not visually appealing
D. Cost is not the team’s job

Q2

A FinOps team launches a Slack channel for cost alerts. After two weeks the channel has 400 messages and is on mute. Most accurate diagnosis:

A. Slack is the wrong tool
B. Alert volume is too high relative to actionability. Each alert needs to name a specific resource, owner, and action. Otherwise the channel becomes noise.
C. Engineers do not check Slack
D. The integration is broken

Q3

An engineering leader asks: “Which teams need help?” Which Inform shape best answers this?

A. Snapshot
B. Trend
C. Breakdown
D. Anomaly

5. Apply

ZopNight’s Inform surface has three personas baked in:

• Engineering team → Reports → Cost Breakdown, Reports → Resources, MCP for self-serve queries
• Engineering leadership → Dashboards → Engineering preset, Weekly summary email
• Finance / leadership → Dashboards → FinOps preset and Executive preset, with the cost-per-unit overlay (see T3.M3.5 L5)

The four shapes are all present: Trend (Reports → Cost Trend), Breakdown (Reports → Cost Flow Sankey), Snapshot (Dashboards), Anomaly (Reports → Anomalies with 15-min cadence).

Open ZopNight Dashboards (deep link)

Related lessons

• L3: Optimize: the four levers (next)
• T3.M3.7: Dashboards as a governance surface
• T2.M2.10: Cost anomaly detection

Glossary terms touched

Inform · Actionable visibility · Cadence · Cost shape