Operate: the discipline that beats one-shot wins

Outcome

By the end of this lesson, you will be able to describe the operate motion and design a weekly + monthly cadence that compounds savings instead of decaying them.

1. Concept

Operate is the third phase, and it is the difference between a company that does this and a company that did it once.

Without it, every saving unwinds. Schedules get switched off and stay off. Tags stop being applied. Commitments come up for renewal and get approved without anyone checking. A year later the avoidable spending is back where it started.

This phase is not a project with an end date. It is a set of recurring checks on a weekly, monthly and quarterly rhythm. Each has a named owner, and each is attached to a number that triggers an action.

What decays without Operate

WHAT WAS DONE                          WHAT DECAYS WITHOUT OPERATE
──────────────────────────────────────────────────────────────────────
Scheduled non-prod off-hours           Schedules disabled "just this once"
Rightsized 30 instances                Re-grown to original size in 6 months
Bought a 1-yr commitment               Renewed without re-baselining floor
Set lifecycle policy on snapshots      Exceptions accumulate, policy weakens
Cleaned untagged spend to 5%           Drifts back to 18% over two reorgs
Established budget per team            Variance reports stop being read

None of this happens because a team is careless. It happens because nobody owns the recurring check. This phase is the part where that ownership gets written down.

The three cadences

Weekly (operational).

• Work through the recommendations. Apply, dismiss, or defer with a reason written down.
• Check the schedules. Is anything switched off with no date to switch it back on?
• Check the spending alerts. Is anything from last week still unexplained?
• Who runs it: one cost specialist and one engineer, rotating.
• How long: 30 to 45 minutes.

Monthly (tactical).

• Close the month. Reconcile billed cost against budget per team.
• Update unit economics dashboards. Unit economics means cost divided by something the business counts: cost per order, per customer, per thousand requests.
• Review the avoidable-spend KPI.
• Update tag-coverage trend.
• Owner: FinOps + finance + each team lead.
• Time: 1 hour.

Quarterly (strategic).

• Re-baseline commitments (RI / SP / CUD coverage and utilization).
• Review the FinOps maturity self-assessment.
• Update the forecast for the next quarter.
• Review the OKRs.
• Owner: FinOps lead + finance + engineering leadership.
• Time: 2 hours.

Five operate KPIs

The five numbers a healthy FinOps practice tracks weekly:

1. Avoidable spend % of bill. Target: below 8%.
2. Tag coverage %. Target: above 95%.
3. Open recommendations dollar value. Trend toward zero.
4. Commitment coverage % and utilization %. Coverage stable; utilization above 90%.
5. Unit economics trend (cost per MAU, per order, per 1K API requests). Direction matters more than absolute number.

These five drive the operate conversation. Anything else is supporting detail.

The compounding effect

A team that runs this phase well sees savings build rather than fade. The mechanism is simple. New recommendations keep appearing as the estate changes. Schedules keep firing. Alerts keep catching sudden events. The weekly rhythm deals with each one while it is still small.

A team that does not practice Operate will run an optimization sprint, claim savings, and find six months later that the savings are partially gone. The post-mortem usually concludes “we need another optimization sprint.” The actual fix was always Operate.

Who owns Operate

A common failure mode is “FinOps owns Operate.” This is principle 3 (ownership) inverted. Central FinOps owns the cadence and tooling; each team owns its own operate work within that cadence.

The right structure is simpler than it sounds. A small central group publishes the standards, the numbers to watch, the weekly template and what to do when spending spikes. It runs the tools and hosts the meeting. Each team brings its own numbers and its own actions.

2. Demo

A sample weekly operate meeting agenda for a mid-size FinOps practice:

WEEKLY FINOPS REVIEW: 30 min, Mondays at 10:30
─────────────────────────────────────────────────────────
1. KPI dashboard read (5 min)
   - Avoidable spend % WoW
   - Tag coverage % WoW
   - Open recommendations $ value WoW
   - Anomaly count last 7d

2. Recommendations triage (10 min)
   - Top 10 open recommendations by savings
   - Apply / dismiss / defer (with reason)
   - Note any new patterns

3. Schedule + autoscaler health (5 min)
   - Any disabled schedules without expiry?
   - Any autoscaler policies in error state?
   - Any overrides expiring this week?

4. Anomaly review (5 min)
   - Last week's anomalies, status check
   - Any unresolved root causes?

5. Open items + parking lot (5 min)
─────────────────────────────────────────────────────────

Thirty minutes per week. The same five sections. The same five KPIs. The discipline is the cadence, not the agenda.

3. Hands-on (6 min)

Design your own weekly cadence. Fill in:

1. WHO is in the room?
   FinOps lead:    ____________
   Eng rep(s):     ____________
   Finance:        ____________ (monthly, not weekly)

2. WHEN does it happen?
   Day / time:     ____________
   Duration:       ____________

3. WHAT is reviewed every week?
   KPI 1:          ____________
   KPI 2:          ____________
   KPI 3:          ____________
   KPI 4:          ____________
   KPI 5:          ____________

4. WHAT decisions can be made in the room?
   ____________ (list 3: these are the decisions that
                make the meeting worth holding)

5. WHO owns the runbook (the document that says how
   to run the meeting)?
   ____________

If items 1, 2, and 5 are not concrete people and times, the cadence does not yet exist. Operate without a calendared meeting is wishful thinking.

4. Knowledge check

Q1

A team ran a successful FinOps sprint and saved $30K monthly. Six months later, the savings are partially gone. Best diagnosis:

A. The savings were over-claimed
B. Without an Operate cadence, schedules drifted, recommendations went unreviewed, and the estate evolved without checks
C. The cloud provider raised its prices partway through the period, which wiped out the gains from the sprint
D. The team got bigger

Q2

“FinOps owns the operate cadence and the per-team numbers.” This statement most directly violates:

A. Principle 1 (collaborate)
B. Principle 6 (variable cost)
C. Principle 3 (ownership)
D. Principle 4 (data accessible, timely, accurate)

Q3

The five Operate KPIs are designed to be reviewed:

A. Annually at a strategic offsite
B. Daily for engineering and monthly for the finance team
C. Whenever someone asks
D. Weekly, with monthly and quarterly deeper cuts on the same set

5. Apply

ZopNight’s Operate-supporting surface:

• Recommendations queue with weekly digest email → drives weekly triage
• Schedules dashboard with disabled-schedule callouts → drives weekly health review
• Cost anomaly stream with 15-min cadence + daily digest → drives weekly review
• Budget thresholds with notifications → drives monthly variance conversation
• Reports → Trends with month-over-month deltas → drives monthly KPI read
• MCP for self-serve KPI queries in Cursor / Claude Code → makes the weekly meeting prep one prompt

The five Operate KPIs each have a home in ZopNight:

Open ZopNight Dashboards → FinOps (deep link)

Related lessons

• L5: Crawl, Walk, Run (next)
• T4.M4.1: FinOps maturity ladder
• T4.M4.5: Cost anomaly response playbook

Glossary terms touched

Operate · Operate cadence · Avoidable spend · Commitment utilization