Epic
A business hypothesis big enough to need a portfolio decision.
01What it's for
An Epic is a bet. It states which customer we serve, which problem or job we improve for them, and which measurable result we expect: For … we improve … and achieve …
It carries a leading indicator that tells us within a quarter whether we are on the right track, an MVP that tests the hypothesis, and a lean business case that is good enough to decide on, not more.
02What it turns into on the old system
The Epic becomes the project charter under a new name. Scope, budget and end date are fixed up front, the business case is written to get the money and is not looked at again, and “done” means delivered, not achieved.
Progress is reported as percentage complete. The Epic belongs to a department, and stopping it feels like failure instead of a decision.
03How you notice
- Epics are named after solutions or systems: “New CRM”, “Platform migration”.
- No Epic has a leading indicator, or nobody looks at it.
- Epics are rarely stopped. They slow down, split, or quietly linger.
- Status reports show milestones and budget burn, not outcome.
04How to make it work
Write every Epic as a hypothesis with a measurable outcome and a leading indicator we can read within one quarter. Anything can be measured; the only question is what it costs to measure it.
Define the MVP that tests the hypothesis. Keep the solution open until the QBR decides to invest.
The portfolio decides three things only: invest, continue or stop. The Epic Owner and the ARTs decide the solution, within the guardrails, as late as responsibly possible.