LEARN. PRACTICE. GROW.Concept and mechanism
An epic proposal needs to explain the intended change, for whom, and its strategic contribution. “Migrate to cloud” describes a solution but does not yet explain benefit. Define the hypothesis and a proportionate initial experiment. It may be a limited capability with an effect measure and criteria to continue, change, or stop. Approving the experiment does not demonstrate that benefit will be achieved. The portfolio backlog should make initiatives and commitment decisions visible. As effort and exposure grow, the organization needs enough evidence to choose the next step rather than treating initial approval as an obligation to finish everything.
Guided application
Funding value streams can stabilize capacity and enable priority adaptation within an approved budget. This still needs boundaries and transparency. Discuss the mix of near-term and future investment, capacity for solution integrity, significant decisions, and continuing business-owner involvement. This path prescribes no universal maintenance percentage. Obsolescence and infrastructure need contextual consideration. If many epics start and few demonstrate value, observe states, waiting, and capacity before approving more. A larger queue may merely prolong completion. Remove or redirect initiatives through explicit decisions and retain the rationale for later learning.
Legacy coexistence and retirement belong in the investment comparison even when other teams execute them.
Common pitfalls
Cloud as automatic benefit; approval as validation; adaptive budgeting as no boundaries; started epics as realized value.
Related topics: Governance, AI, and change leadership · Value, flow, and the system view
Fund capacity and learning through boundaries that keep choices and costs understandable.
Reference: Portfolio Backlog · AI-Empowered SA; official study guide May 27 2026; current product page publishes different ranges in three domains