---
name: Enterprise Operations & Value-Driver Analysis
description: Diagnose where enterprise value is actually created and lost — a hypothesis-driven, MECE breakdown of the operating model into value drivers, cost-to-serve, and the two or three moves that matter, in the top-down strategy-consulting tradition McKinsey is known for. For founders and operators who need a structured operations diagnosis, not a dashboard.
audience: founder · COO · operations lead · product leader
---

# Enterprise Operations & Value-Driver Analysis

## What this is

A method for finding where value is genuinely created and destroyed in an operating model, structured the way top-down strategy work is done: start from a hypothesis, break the business into a MECE tree of value drivers, size each with the best available data, and converge on the two or three moves that move the number — not a list of forty. It reads the operating model (how the work flows, what it costs to serve, where scale helps and where it doesn't) and answers the "so what" for each finding rather than stopping at the observation.

## What this is NOT

Not affiliated with or endorsed by McKinsey & Company or any consulting firm — it uses the publicly understood analytical discipline (hypothesis-driven, MECE, driver trees, top-down synthesis) as a reference lens, not their proprietary tools or brand. Not a licence to present estimates as facts: every sizing is labelled estimate or measured, and a confident deck built on guessed numbers is the failure this avoids. Not a substitute for the operator's own knowledge of the business, and not financial, legal, or investment advice.

## Method

1. **Start from a hypothesis, not a data dump.** State what you believe is driving value and cost, then test it — a diagnosis that boils the ocean answers nothing.
2. **Break the business MECE.** Decompose the operating model into mutually exclusive, collectively exhaustive value drivers (revenue quality, unit economics, cost-to-serve, capacity utilization) so nothing is double-counted or missed.
3. **Size each driver.** Attach the best available number to each branch — measured where you have it, clearly-labelled estimate where you don't — so the tree shows where the money actually is.
4. **Find the vital few.** Rank drivers by impact and controllability; the answer is usually two or three, not the whole tree. Say which, and why the rest are noise for now.
5. **Read the operating model honestly.** Where does scale help, where does complexity eat the margin, where is cost-to-serve mismatched to price — name the structural cause, not just the symptom.
6. **Pressure-test with disconfirming evidence.** Actively look for the data that would kill the hypothesis; a diagnosis that only collects supporting facts is advocacy, not analysis.
7. **Synthesize top-down.** Lead with the answer and the "so what," then support it — an executive should get the conclusion in the first line, not the last.
8. **Turn it into moves.** Each of the vital few becomes a concrete initiative with an owner, an expected impact (labelled estimate), and how it will be measured — a diagnosis that ends without a decision is trivia.

## Quality bar

The work starts from a testable hypothesis · the business is broken into a MECE driver tree with nothing double-counted · each driver is sized and labelled estimate vs measured · the vital few (2–3) are named and ranked by impact and controllability · structural causes are named, not just symptoms · disconfirming evidence is actively sought · findings are synthesized top-down (answer first) · each priority becomes an owned, measurable move.

## Guardrails & escalation

An analytical method in the top-down strategy tradition — not affiliated with McKinsey or any firm, and not a substitute for the operator's judgment. Every number is labelled estimate or measured; nothing guessed is presented as fact. This is operational analysis, not financial, tax, legal, or investment advice — decisions with those stakes are routed to qualified professionals (CFO, counsel, CPA). Where the data can't support a driver's sizing, the method says so rather than inventing a number to complete the tree.

## References

- Catalogue: https://edwson.com/consumer-design-system.html · Contracts: https://edwson.com/cds/components.json · Agent brief: https://edwson.com/cds/AGENTS.md
- Related within this kit: the Enterprise Health Score, P&L & EBITDA review, multi-lens risk, and revenue-forecast skills. Financial specifics are routed to a CFO/CPA; this method sizes and prioritises, it does not audit.