Outcome
By the end of this lesson, you will be able to recognize Run-stage characteristics, explain the compounding effect of weekly Operate cadence, and assess whether your org’s practice is sustainable Run or aspirational Walk-with-Run-rhetoric.
| Tier | Engineer |
| JTBD | ”Sustain Run-stage practice over years, not just claim Run status in a quarterly review.” |
| Personas | FinOps Lead · Engineering Leader · FinOps Analyst |
| Prerequisites | M4.1.L1 (Crawl) · M4.1.L2 (Walk) |
| Time | 9 minutes |
| Bloom verb | Recognize (Remember), Explain (Understand), Assess (Evaluate) |
1. Concept
Run is the third and final stage in the FinOps Foundation maturity model. Run is the only stage where savings compound rather than decay. Each week’s Operate review surfaces the next optimization opportunity; each quarter’s accumulated wins build on the previous quarters. The hallmark of Run is not how much was saved last sprint; it’s how much has been saved every quarter, with the rate increasing rather than flattening.
RUN SIGNATURE──────────────────────────────────────────────────────────────────Weekly Operate cadence (30-45 min) ✓ consistentThe 5 Operate KPIs tracked + trended weekly ✓ measuredRecommendations triaged weekly (<7-day age) ✓ backlog managedAnomalies acted on within 24 hours ✓ fast responseTag coverage > 95% ✓ hygieneUnit economics tracked + reported ✓ business framingForecasting accuracy ±10% ✓ predictabilityBudget pyramid in place + reviewed ✓ governancePre-merge cost estimation ✓ shift-leftEach property reinforces the others. The combination is what makes the practice sustainable.
The compounding effect
The most important Run characteristic is compounding: savings build on previous savings rather than replacing them.
QUARTERLY SAVINGS PROGRESSION (Run-stage org):
Q1 of Run: $40K/mo realized savings (foundation)Q2: $52K/mo (+$12K: schedule expansion + new recs)Q3: $68K/mo (+$16K: commitments + right-sizing)Q4: $85K/mo (+$17K: unit-economics-driven re-arch)Q5: $105K/mo (+$20K: anomaly response + tagging hygiene)Q6: $130K/mo (+$25K: accelerating)Q7-Q8: $160K/mo, $195K/mo (compounding plateau begins)
CONTRAST: Walk org over same 8 quarters:Q1: $40K, Q2: $35K, Q3: $30K, Q4: $25K, then re-sprint to $50K,decay to $35K by Q8.
Run produces ~3-5× the cumulative savings over 2 years vs Walk.The compounding isn’t magic. It comes from continuous incremental improvement enabled by the operating rhythm.
How compounding works in practice
WEEKLY (the engine): Triage 5-15 new recommendations → 3-8 typically applied → backlog stays manageable Confirm schedules working as intended → catch failures within a week, not a quarter Anomaly review → identify and fix patterns before they recur
MONTHLY (the consolidation): Variance analysis (budget vs actual) Re-baseline forecast based on latest data Identify trend issues that emerge across the four weeks
QUARTERLY (the strategic): Major design reviews (e.g., should we go multi-region?) Re-evaluate maturity stage (am I still at Run?) Plan next-quarter goals Quarterly budget re-baseline Commitment portfolio rebalance
ANNUAL (the scope): Architecture-level optimization Vendor negotiation Major commitment purchases (3-year EDP renegotiation) Org-wide unit economics reviewEach layer reinforces the others. Weekly catches what monthly cannot afford to wait for; monthly identifies trends that quarterly addresses with bigger interventions; quarterly aligns with annual strategy.
Why Run is hard to reach
Most orgs do not reach Run in their first attempt. The reasons:
- Requires deliberate practice (not just tools) Tools support the practice but don't replace it
- Requires organizational commitment Engineering leadership has to value cost as a priority alongside reliability, security, and features
- Requires leadership buy-in "Cost is everyone's problem" must be backed by org incentives
- Takes 6-18 months to fully establish The cadence has to survive turnover, reorgs, busy quarters
- Cultural shift is harder than technical shift Engineers used to "FinOps's problem" have to take ownershipMost orgs that try the Walk → Run transition take 6-12 months. The “12 months in” version usually has the cadence sustaining itself; the “6 months in” version usually has the cadence depending on one or two committed individuals.
Signs Run is sustainable vs aspirational
The test of “is this Run or aspirational Run”:
SUSTAINABLE RUN SIGNAL TEST──────────────────────────────────────────────────────────────────Weekly meeting happens consistently Pick a random 6-month-ago week; did the meeting happen? Was it 30+ min? Did it produce action items?
Action items get done Pick a random 3-month-ago action item; is it completed or still "pending"?
The practice survives turnover Has the FinOps Lead or a key team owner changed in the past year? Did the cadence survive?
KPI dashboard is visited Look at the dashboard widget analytics: is it visited weekly?
Recommendations don't pile up Recent backlog count vs year-ago backlog countIf the answers are “yes” consistently over 6+ months, Run is real. If “depends on availability” or “varied,” still in Walk.
What pulls Run orgs back
Even Run orgs can backslide. The pull-backs:
- A key practitioner leaves The cadence depends on people; turnover can dissolve practice
- Org reorg dissolves team cost ownership New team boundaries; cost owners unclear; rebuild needed
- A major incident consumes attention Operate cadence skipped during incident response; hard to restart
- Leadership priority shifts Cost de-emphasized when revenue or product moves higher
- Tool migration disrupts cadence New cost platform; rebuild dashboards, KPIs, ritualsThe defensive move: document the practice. A team wiki describing the weekly cadence, the 5 KPIs, the agenda template, and the escalation paths makes the practice less dependent on any one person.
How ZopNight uses Run-stage practice
ZopNight’s Operate dashboard supports the weekly meeting directly; bookmark the dashboard, open it during the meeting, walk through the 5 KPIs in order. The meeting can stay under 30 minutes when the dashboard does the heavy lifting.
For sustained Run practice, ZopNight surfaces longitudinal metrics: not just “this week’s savings” but “savings trend over 12 months.” The compounding pattern is visible in the trend.
2. Demo
A Run org’s 2-year practice profile:
ORG: B2B SaaS, 250 engineers, $300K/month spend at start of RunTIMELINE: 24 months of consistent Run practice
PRACTICE METRICS: Weekly Operate meetings: 96+ (out of 104; rare skips) Recommendations reviewed: 4,800 cumulative (avg 92/month) Anomalies investigated: 65 (avg 5/quarter) Postmortems written: 48 (75% of anomalies) Tag coverage: Stable 96-98% the whole period Forecast accuracy: ±8% average (peak: ±4%)
COST OUTCOMES: Starting spend: $300K/month Cumulative savings realized: $1.2M total End-of-period efficiency: Cost-per-MAU down 23% YoY
LEADERSHIP CONFIDENCE: "We know what next month's spend will be within 8%." "We know which teams are growing and why." "We know which optimizations are next."
ENGINEERING CULTURE: Cost is in the PR description for non-trivial changes Engineers self-serve cost answers via dashboards (or MCP) New engineers learn cost discipline in their first month Pre-merge cost estimation catches surprises before deploy
RECOVERY FROM INCIDENT: Cost incident in month 18: anomaly detected at +2K/mo run rate Investigation completed in 90 minutes Root cause: misconfigured HPA scaling Action: HPA limits added; incident over within 2 hours Postmortem produced 3 action items; all completed in 2 weeks
CONTRAST with Walk-stage handling of the same incident type: detection at 3-5 days, $30K+ overrun before resolution.The compounding shows up everywhere: in the savings, in the predictability, in the speed of incident response, in the culture.
3. Hands-on (5 min)
Audit your Run practice (or aspirations):
RUN PRACTICE CHECK: □ Weekly Operate meeting (consistent over 6+ months) □ 5 Operate KPIs tracked □ Recommendation backlog under 50 open / under 30 days old □ Anomalies resolved within 24 hours typical □ Tag coverage > 95% and stable □ Forecast accuracy ±10% or better □ Quarterly budget re-baseline practice □ Documentation of the practice (team wiki)
SUSTAINABILITY CHECK: □ Has practice survived turnover in past year? □ Has practice survived a reorg in past year? □ Has practice survived a major incident in past year?
SCORE: All 8 + 3 sustainability = Run (mature) 6-7 + 2 sustainability = Run (early) 3-5 = Walk with Run aspirations <3 = Walk
NEXT IMPROVEMENT: __________________________________________________________4. Knowledge check
Q1
Run-stage cadence is:
A. Monthly is sufficient
B. Weekly. Monthly is Walk maturity at best. The weekly cadence is what catches drift before it compounds and what makes savings compound rather than decay. Monthly cycles are the additional layer for variance analysis and forecast re-baselining, but weekly is the engine.
C. Quarterly
D. Random
Show answer
Correct: B. Weekly is the Run cadence. Monthly + quarterly + annual layer on top, but weekly is the foundation.
Q2
Compounding savings in Run come from:
A. One bigger optimization sprint per quarter
B. Continuous incremental optimization. Each week surfaces the next opportunity; each quarter the accumulated wins build on previous wins. The compounding effect over 2 years produces 3-5× the cumulative savings vs Walk-stage sprint-and-decay cycles.
C. Cloud rate-card changes
D. Random
Show answer
Correct: B. Incremental + sustained. The cadence is what produces compounding.
Q3
Establishing Run typically takes:
A. 1 month
B. 6-18 months from Walk. Cultural and operational change is gradual. The “12 months in” version usually has the cadence self-sustaining; the “6 months in” version typically depends on one or two committed individuals: fragile to turnover.
C. Years
D. Random
Show answer
Correct: B. Months, not weeks. The cultural shift is what takes the time.
5. Apply
Use Reports → Operate as the weekly meeting’s canvas: the 5 KPIs in one view. Bookmark it; open it during the meeting; walk through.
Document your team’s Run practice in your wiki. The documentation is what makes the practice survive turnover.
Related lessons
- L1: Crawl: visibility-only orgs
- L2: Walk: optimization motion
- L4: Maturity anti-patterns (next)
- L5: 90-day move-up plan
- T0.M0.2.L4: The 5 Operate KPIs
Glossary terms touched
Run stage · Compounding savings · Operate cadence · Sustainable practice