The map / Portfolio / Epic Refinement
Epic Refinement
Turning a strategic idea into a testable hypothesis before it competes for capacity.
01What it's for
Epic Refinement makes an idea decidable. It names the customer, the problem, the expected outcome, the leading indicator, the MVP and the cost of delay.
It runs when an idea is pulled, not on a fixed calendar, and stops as soon as there is enough to decide at the QBR.
02What it turns into on the old system
Refinement turns into the approval gate of the old system. A committee asks for a complete design, an architecture board adds a review, and the Epic waits in analysis for months.
The solution is fixed before the problem is understood, by people who will not build it.
03How you notice
- Epics wait weeks for the next meeting slot.
- Refinement produces documents, not decisions.
- The people who will deliver the Epic see it for the first time at PI Planning.
- Every Epic gets the same heavy template, whatever its size or risk.
04How to make it work
Keep it small and pulled: Epic Owner, an architect, Product Management and someone from the ARTs that will carry it.
Timebox it. The output is a hypothesis statement, an MVP, a lean business case and a first view on which ARTs are involved. That is enough for the QBR.
Keep solution options open. Detail is decided later, by the people closest to the work.