Portfolio Decisions
Updated 15 May 2026
This practice document describes the four distinct decision types that portfolio governance produces — gate, ratification, exception, and reallocation. For each, it specifies when the decision happens, who has the authority to take it, what the substantive criterion is, and where the mandate boundary sits.
The capability that owns the decision discipline is Portfolio Governance and Decision-Making; this practice describes the concrete structure the capability is exercised through.
The four decision types
| Decision type | When it happens | Authority | Substantive question |
|---|---|---|---|
| Gate decision | Gate 1 (admission to Discovery Queue); Gate 2 (admission to Delivery Queue) | Portfolio Leadership Group | Gate 1: is this strategically relevant and articulated enough to warrant analytical investment? Gate 2: is the Lean Business Case sound enough to warrant delivery investment? |
| Ratification decision | An Initiative Owner brings a continue, pivot, or stop recommendation forward during Implementing | Portfolio Leadership Group | Does the recommendation reflect the evidence and the system’s forward-looking interest? |
| Exception decision | A decision request falls outside an established mandate — a guardrail breach, an intra-cycle reallocation, a scope expansion beyond the LBC envelope | Portfolio Leadership Group | Does the strategic case for granting the exception outweigh the disruption it produces, and what is the cost of maintaining the current mandate’s integrity? |
| Reallocation decision | A material change in capacity allocation between value streams is proposed — typically at allocation cycle, occasionally intra-cycle as an exception | Portfolio Leadership Group, with Value Stream Owners participating | Does the proposed allocation reflect current strategic priorities and observed delivery system state, and is the disruption of moving capacity justified by the expected outcome? |
Substantive criteria per decision type
Each decision type has a substantive criterion that decisions are weighed against. Articulating the criterion explicitly — and consistently applying it — is what distinguishes a governance structure from a series of ad hoc judgments.
Gate 1 — admission to discovery domain
The criterion is direction fit and articulation sufficiency — not value, not feasibility. Gate 1 asks: is this candidate aligned with the portfolio’s strategic direction, and is its problem statement articulated well enough to warrant the analytical investment of taking it into the discovery domain? Value and feasibility are not yet assessable; they will be developed during discovery. A Gate 1 decision that judges value or feasibility is doing Gate 2’s work prematurely.
Gate 2 — admission to delivery
The criterion is the soundness of the investment hypothesis carried in the Lean Business Case. Gate 2 asks: given what is now known after discovery, is the proposed investment a sound use of delivery capacity? Soundness includes value hypothesis, MVP definition, cost estimate, and go/no-go criteria — but the criterion is integrative, not item-checked. A Gate 2 decision asks whether the case holds together as an investment proposition, not whether each form field is filled in.
Ratification — continue, pivot, or stop
The criterion is whether the recommendation reflects the evidence and the system’s forward-looking interest. Ratification is not a re-litigation of Gate 2; it is a deliberate act on the Initiative Owner’s recommendation given what has been learned during delivery. A pivot recommendation passes if the revised hypothesis is supported by accumulated evidence; a stop recommendation passes if the forward-looking expected value no longer warrants the capacity it would consume. Continue is the default — no ratification needed unless the picture has changed.
Exception — outside mandate
The criterion is strategic case versus mandate integrity. Exceptions are granted when the strategic case for the specific exception outweighs the cost of weakening the mandate it breaches. Frequent exceptions of one type signal that the mandate boundary itself may need adjustment — handled through mandate revision, not through accumulating exceptions.
Reallocation — capacity movement between value streams
The criterion is strategic priority alignment weighed against disruption cost. Reallocation moves capacity from one value stream to another — typically at allocation cycle when the portfolio resets its bets. Intra-cycle reallocation is treated as an exception. The substantive question includes both whether the reallocation reflects current strategy and whether the disruption of moving capacity is justified by the expected outcome.
Mandate boundaries
Authority is allocated by decision type. Each role decides within a bounded space; decisions outside that space require escalation as exceptions.
Portfolio Leadership Group
Holds formal authority for:
- All Gate 1 and Gate 2 decisions
- Pivot and stop ratification
- Exception decisions outside any other role’s mandate
- Material reallocation between value streams
Value Stream Owner
Holds authority for:
- Decisions within funded Budget Guardrails
- Implementation choices within the scope of approved Lean Business Cases assigned to the value stream
- Tactical reallocation of capacity within the value stream’s own portfolio
Escalation triggers:
- Budget Guardrail breach (cost mix, single-initiative exposure, spend category requiring portfolio visibility)
- Scope change that exceeds an LBC envelope
Initiative Owner
Holds authority for:
- Recommendations (not decisions) on continue, pivot, or stop
- Scope adjustments within the LBC envelope
- Tactical implementation choices
Escalation triggers:
- Recommendation requires ratification (always — for pivot and stop)
- Scope change that exceeds the LBC envelope
- Cost or timeline shifts that materially change the investment hypothesis
The pattern: each role decides what is reversible within its scope; what is not reversible, or what affects scope beyond its own, escalates. Decisions within mandate proceed without further authorization. Decisions outside mandate are exceptions handled at the next level up.
Pull is not a decision type
Pull is deliberately absent from this taxonomy. When Gate 2 has been passed, the initiative is prioritized in the Delivery Queue, and capacity opens in a value stream — the system pulls. No separate portfolio-level decision is required to do so. Pull is an event that follows from already-made decisions, not a decision in its own right.
Portfolio Kanban Flow describes the pull mechanism; Initiative Prioritization sequences what gets pulled; this practice ensures the upstream decisions that make pull meaningful have been structured well.
Worked examples
These examples illustrate how a decision is classified and handled in practice.
Example 1 — A Gate 1 decision
A registered candidate “Customer self-service for invoice queries” has been triaged. The recommendation from Strategic Relevance Assessment is that the candidate fits the current portfolio theme of reducing support cost and improving customer autonomy, and the problem statement is articulated clearly enough to support analytical work.
The Portfolio Leadership Group reviews the candidate at the Portfolio Kanban Review. The criterion is direction fit and articulation sufficiency. Value, feasibility, and design are not assessed — they will be developed during discovery.
Decision: Gate 1 passed. The candidate enters the Discovery Queue.
Example 2 — An exception decision
A value stream is mid-cycle. Its Budget Guardrail allocates 60–70% of capacity to new-capability work and the rest to technical enablement. An unexpected production incident has revealed accumulated technical debt in a critical component. The Value Stream Owner proposes shifting 12% of next quarter’s allocation from new-capability to technical enablement to address the debt — a guardrail breach of 8 percentage points below the floor.
The Value Stream Owner has not got autonomous authority to make this shift; it requires an exception decision from the Portfolio Leadership Group. The criterion is strategic case versus mandate integrity.
The strategic case is concrete: incident risk, recurring incidents predicted, and a multi-quarter cost trajectory if not addressed. The mandate integrity cost is that this exception, if frequent, signals the guardrail boundary may itself need adjustment.
Decision: Exception granted for one quarter, with a commitment to revisit the guardrail at the next allocation cycle. Recorded as an exception, with the rationale.
Example 3 — A ratification decision
The Initiative Owner for “Real-time fraud detection upgrade” brings a pivot recommendation forward at the Portfolio Sync. During Implementing, evidence has accumulated that the original architecture choice (in-house rules engine) will not scale to the required throughput. The recommendation is to pivot the Lean Business Case to a third-party engine with integration work, increasing cost by 20% but reducing delivery risk substantially.
The Portfolio Leadership Group reviews the recommendation. The criterion is whether the revised hypothesis is supported by the evidence and reflects the system’s forward-looking interest.
The evidence is solid: load testing data, vendor evaluation, and a revised cost-benefit case. The forward-looking interest favors the pivot — delivery risk reduction is material.
Decision: Pivot ratified. The Lean Business Case is updated with the revised hypothesis, MVP, and cost. Continuous Initiative Validation continues against the updated baseline.
Related
- Portfolio Governance and Decision-Making — the capability that owns the decision discipline
- Portfolio Ways of Working — the forums and cadences in which these decisions are taken
- Portfolio Roles — the roles through which decision authority is exercised
- Portfolio Kanban Flow — the flow mechanic decisions execute through