Bring Strategic Intent and Real Decision Authority into the Room
Use the Flow-problem backlog to identify the portfolio choices the conference must make. Prepare the people, guardrails, objectives, epics, investment boundaries, and roadmaps needed to make those choices explicit and usable.
- Fast exercise
- 5 minutes
- Full exercise
- 15–25 minutes
- Input
- Top Flow problems + objectives
- Output
- Portfolio roles + artifact stack
- Next module
- Shared Initiatives & Communities
Understanding Portfolio Contribution
Portfolio participation should resolve intent and boundaries
Portfolio leaders do not join to restate a slide deck. They make strategic intent, investment boundaries, non-delegable constraints, and unresolved trade-offs clear enough for the value stream to build a credible draft roadmap.
Decision Depth
Match the preparation effort to reversibility and impact
Use light evidence, one clear decider, a short review horizon, and fast artifact update.
Include affected units and shared foundations, but preserve the option to adjust after evidence.
Test technical, legal, safety, operational, or commercial consequences before commitment.
Bring explicit options, consequences, dissent, investment impact, and a documented review or supersession path.
Running the Exercise
Five moves from Flow problem to portfolio-ready contribution
-
1
Approximately 2–4 minutes
Translate Problems into Portfolio Decisions
Start with the highest-ranked Flow problems. Ask what cannot be resolved by one ART, Solution Train, shared initiative owner, or local function—and what portfolio choice would remove the wider constraint.
PriorityWhat comes first? Resolve competing objectives, epics, or shared initiatives.
InvestmentWhere does capacity or funding move? Change budget, capacity allocation, or enablement investment.
BoundaryWhat remains fixed? Clarify policy, risk tolerance, strategic constraint, or delegation limit.
SequenceWhich order protects value? Choose milestones, market windows, dependency order, or learning steps.
Stop / startWhat leaves or enters WIP? Pause, split, continue, or start an initiative based on capacity and evidence.
EscalationWho must decide elsewhere? Name the higher authority, deadline, and fallback when the conference lacks the mandate.
Decision statement By [date], [decider] must choose [decision] so that [objective / Flow effect], within [guardrails], updating [artifact].Example: “By the conference close, the portfolio sponsor must choose whether to sequence the compliance launch before the data-platform rollout, within the Q3 regulatory date and current investment envelope, updating the portfolio and Value Stream roadmaps.”
Speaker Notes
Facilitator intentConvert the highest Flow problems into bounded portfolio decisions, so the room can distinguish what needs strategic authority from what can be solved by delivery, shared initiatives, central functions, or suppliers.
How to facilitate
- Start with the top Flow-problem backlog items and ask which choice cannot be made credibly by one ART, Solution Train, function, or initiative owner alone.
- Use the decision statement on the slide: decider, decision, date, guardrails, intended Flow effect, and artifact to update.
- Separate decision types explicitly: priority, investment, boundary, sequence, stop/start, or escalation. A vague need for alignment is not yet a decision.
Listen and watch for
- A problem being lifted to portfolio level only because it is painful, not because portfolio authority can change the constraint.
- Portfolio decisions hiding inside delivery language, such as more capacity, more focus, or better sequencing without a named trade-off.
- A decision statement with no update artifact; if the portfolio roadmap, epic, guardrail, or value-stream roadmap will not change, the decision may be informational.
Avoid
- Reprioritizing the entire portfolio inside this exercise. Prepare the decision the conference needs, do not recreate portfolio governance.
- Treating every Flow problem as a portfolio problem. Route local, functional, supplier, or shared-foundation problems to the right contribution module.
- Leaving the decision phrased as a question no one in the future could validate as decided or not decided.
-
2
Approximately 3–5 minutes
Separate Guardrails from Choice
Do not let every historical commitment arrive as a hard constraint. Classify each boundary and require enough evidence to understand what happens if it is challenged.
Hard constraintExternally or mathematically fixed Law, safety threshold, signed contract, physical limit, or truly immovable date.
GuardrailPolicy that enables delegated choice Budget band, risk tolerance, architecture principle, or strategic boundary.
CommitmentImportant promise with an owner Market, customer, executive, or partner commitment that may have a renegotiation path.
AssumptionBelief awaiting validation Forecast, dependency belief, capacity estimate, business-case premise, or inherited plan.
Portfolio Guardrail Canvas Boundary Type Source / owner Evidence Consequence if changed Decision space Q3 regulatory readiness Hard constraint Compliance sponsor Regulatory date Launch blocked scope and sequence Platform investment band Guardrail LPM Lean budget portfolio trade-off allocation within band Customer demo in June Commitment Business Owner customer plan trust / renegotiation demo scope Speaker Notes
Facilitator intentProtect real constraints while reopening untested commitments and assumptions. Portfolio contribution becomes useful when leaders know which boundaries are hard, which are delegated guardrails, and where trade-space remains.
How to facilitate
- Put each boundary on its own card and classify it as hard constraint, guardrail, commitment, or assumption before negotiating it.
- Ask for source, owner, evidence, consequence if changed, and remaining decision space. This mirrors the Iron Triangle discipline from the Executive Workshop.
- Translate guardrails into usable decision language: what is fixed, what can move, who can approve an exception, and by when.
Listen and watch for
- Historic promises being treated as law, budget, contract, or regulation without evidence or owner.
- Guardrails that are so vague they cannot help delegated decision-making, or so rigid they become unacknowledged hard constraints.
- Executives calling something non-negotiable while still expecting the conference to create a realistic roadmap inside impossible boundaries.
Avoid
- Challenging every constraint as political theatre. Some constraints are real and should be respected.
- Accepting a boundary without naming the consequence. If nobody can say what happens when it is crossed, it is not yet operationally useful.
- Pushing ambiguity downstream to ARTs and teams; the point is to remove ambiguity before detailed planning.
-
3
Approximately 3–6 minutes
Assign Decision Roles
Use the organization’s own language. The role pattern below combines useful distinctions from RAPID and DACI without requiring either framework as a new governance layer.
Drive / RecommendPrepare the choice Frames the question, gathers input, compares options, and brings a recommendation.
Decide / ApproveMake the call Owns the final choice and commits the organization within known authority.
AgreeProtect a mandatory boundary Required sign-off only where law, safety, policy, contract, or delegated governance demands it.
InputImprove the decision Provides facts, experience, options, dissent, and consequences without silently gaining veto power.
PerformMake it real Owns execution and must understand feasibility, capacity, and follow-through.
InformReceive the outcome Needs the decision and consequence but not a seat in the decision conversation.
One-D rule: Use one final decider for each bounded decision whenever governance permits. If several people jointly decide, state the joint rule and deadlock path explicitly.
Speaker Notes
Facilitator intentMake decision ownership explicit enough that the conference can close choices rather than collect opinions. Use role distinctions pragmatically without adding a new governance framework for its own sake.
How to facilitate
- Assign one final decider wherever governance permits; where joint decision-making is required, name the rule and deadlock path.
- Distinguish Drive/Recommend, Decide/Approve, Agree, Input, Perform, and Inform so input does not silently become veto power.
- For each required agreement role, ask what mandatory boundary it protects: law, safety, contract, budget, formal policy, or delegated governance.
Listen and watch for
- Many senior people listed as deciders for the same bounded choice, which usually means no one is accountable for closure.
- Agreement roles assigned because someone is important, rather than because a mandatory boundary requires sign-off.
- Performers missing from the role map; decisions that cannot be executed are not conference-ready.
Avoid
- Importing RAPID, DACI, or any other model as ceremony. Use only the distinctions that improve this decision.
- Letting the decision driver become the final decider by default. Preparation ownership and decision authority are different things.
- Creating an invite list before the decision role map is clear.
-
4
Approximately 3–6 minutes
Build the Portfolio Input Stack
Bring only the portfolio artifacts that frame a real conference decision. Every artifact needs a named owner, relevant horizon, confidence level, and update responsibility.
ObjectivesOutcomes and thresholds OKRs, business objectives, customer or regulatory outcomes, and success measures.
EpicsValue and learning hypotheses Epic hypotheses, MVP logic, expected outcomes, assumptions, and current decision state.
RoadmapStrategic sequence Portfolio horizon, major milestones, initiative relationships, and known decision windows.
InvestmentFunding and capacity guardrails Budget bands, allocation policies, cost limits, and material investment choices.
External datesWindows and obligations Regulatory dates, launches, contracts, fairs, customer events, and renewal points.
RisksAssumptions and exposure Strategic risks, dependencies, mitigation options, and risk-acceptance authority.
Portfolio Contribution Board Decision Decider Driver Artifact Guardrail Confidence Update owner Sequence compliance vs platform rollout Portfolio sponsor Epic Owner portfolio roadmap Q3 deadline M Portfolio Mgmt Fund shared test capacity LPM Business Owner investment view budget band L Finance partner Speaker Notes
Facilitator intentAssemble only the portfolio artifacts that make selected decisions possible: objectives, epics, roadmaps, investment boundaries, external dates, and risks with owners, confidence, and update responsibility.
How to facilitate
- For every artifact, ask which decision it supports and which option, constraint, consequence, or confidence level it changes.
- Require an owner, horizon, version or source, confidence, and update path. A deck without an owner is not a decision input.
- Connect the portfolio stack to the value-stream draft: when the decision is made, which roadmap, epic, investment view, or guardrail changes?
Listen and watch for
- Large context decks arriving as a substitute for a decision-ready option comparison.
- Objectives and epics without success thresholds, time horizon, or current decision status.
- Investment information that names budget but not capacity, boundary, trade-space, or who can change it.
Avoid
- Dragging every portfolio artifact into the conference package. More material can reduce decision quality when it hides the actual choice.
- Using stale roadmaps without marking version date and confidence.
- Treating portfolio intent as already understood because it was presented somewhere before.
-
5
Approximately 2–5 minutes
Select Participation and Test Portfolio Readiness
Choose Core, Decision Window, Standby, Preparation-only, or Inform-after for each person. Then test whether the decision could still fail because authority, evidence, or trade-space is missing.
Portfolio Invite and Participation Checklist Candidate Decision role Artifact owner Mandatory signal Mode Selected? Business Owner Decide / input objective value threshold Core □ Epic Owner Drive epic hypothesis options Core □ LPM / Portfolio Mgmt Decide / agree portfolio roadmap investment guardrail Window □ Portfolio Architect Input / agree target-state guardrail architecture consequence Standby □ □ Portfolio readiness gate GREENquestion, authority, trade-space, evidence, options, artifact, and update owner are ready
YELLOWa named gap has an owner, due date, and safe fallback
REDthe conference would discuss but cannot decide—escalate or reschedule the decision window
Speaker Notes
Facilitator intentChoose participation modes and test whether the portfolio decision could still fail because authority, evidence, trade-space, artifact ownership, or response time is missing.
How to facilitate
- Assign Core, Decision Window, Standby, Preparation-only, or Inform-after based on the decision role and expected artifact update.
- Run the readiness gate: question, authority, trade-space, evidence, options, artifact, and fallback.
- If the decision is not ready, create a preparation item with owner, due date, risk if missing, and fallback path.
Listen and watch for
- People invited as a courtesy because they are important, without a decision role, artifact role, or mandatory signal.
- Standby roles without a real response-time agreement; that creates a slow callback chain during the conference.
- Red readiness hidden behind executive confidence. If evidence or authority is missing, the room should know before the decision window.
Avoid
- Optimizing for a small meeting by removing the only person who can approve the trade-off.
- Optimizing for inclusion by inviting everyone full-time, which turns the conference into an audience event.
- Moving to agenda design before the portfolio contribution can actually close or route its decisions.
Facilitation
Protect strategic clarity without turning the conference into portfolio theatre
Ask for an outcome, threshold, horizon, owner, and the choice the conference must make.
Classify each claim as hard constraint, guardrail, commitment, or assumption and request its source.
Confirm whether authority is also delegated. Representation without authority cannot close the decision.
Bound the decision more tightly or define the joint-decision and deadlock rule explicitly.
Name the editable source of truth and its update owner before the conference.
Move supporting analysis to preparation. Keep the decision window focused on options, consequences, and authority.
Ready to Move On?
The portfolio contribution is ready when intent and authority can meet delivery reality
- Top Flow problems have been translated into explicit portfolio decisions.
- Each decision has a deadline, purpose, and bounded scope.
- Hard constraints, guardrails, commitments, and assumptions are separated.
- Reversibility and impact determine the depth of preparation.
- One final decider or an explicit joint-decision rule is named.
- Driver, agreement, input, performance, and information roles are clear where needed.
- Objectives, epics, roadmaps, investment guardrails, dates, and risks have owners.
- Participation modes reduce attendance without lengthening the decision loop.
- Every decision names the artifact that will be updated.
- Readiness gaps have owners, due dates, and fallbacks.
Source Foundation
This page distills slides 29–31 of 2026-07-13_Value_Stream_Conference.pptx. Decision-role distinctions, reversibility, and explicit artifact ownership extend the slide sequence as facilitator support.