Design a Conference That Can Actually Decide
Start with the highest-priority Flow problems. For every decision they require, bring together the authority, delivery reality, expertise, prepared roadmaps, and artifact ownership needed to make a usable choice—not another stakeholder update.
- Fast path
- 6 × 5 minutes
- Full path
- 90–150 minutes
- Contribution modules
- Six connected views
- Primary output
- Decision-capable conference package
- Next step
- Conference Agenda
Understanding the Decision System
Invite for decisions, not for completeness
A conference becomes decision-capable when every material choice has a clear purpose, authority, evidence base, delivery reality, and place where the result will live.
Decision System, Not Stakeholder Meeting
Five capabilities must meet around the decision
Can approve, reject, sequence, fund, or change a material trade-off.
Knows what ARTs, suppliers, platforms, and shared functions can realistically absorb.
Understands architecture, operations, compliance, security, quality, or supplier constraints.
Can speak credibly for affected value, delivery units, customers, operations, or partners.
Can update the roadmap, backlog, capacity view, decision log, or interface agreement.
Three Preparation Questions
Begin with the decision and work outward
- 1Which decisions must the conference be able to make?
Turn the top Flow problems into explicit trade-offs, approvals, sequencing choices, policy changes, or escalations.
- 2Who is required to make those decisions usable?
Name the decider, driver or recommender, required agreement, contributors, performers, and people to inform.
- 3What must be prepared before the decision window?
Bring options, evidence, roadmaps, capacity, constraints, consequences, and the artifact that will be updated.
Three Roadmap Inputs
The conference integrates prepared perspectives
It does not replace the preparation that makes trade-offs visible. Each input type protects the draft roadmap from a different failure mode.
Business objectives, epics, strategic themes, investment guardrails, value hypotheses, and hard external dates.
Prevents a roadmap without intent.Architecture, platform, DevOps, cybersecurity, compliance, toolchain, AI/data, quality, and transformation work.
Prevents local plans from contradicting one another.ART and unit capacity, committed work, KTLO, enabler demand, constraints, dependencies, risks, and credible flex.
Prevents aspiration from being mistaken for a plan.Business objectives, problem-removal work, shared foundations, capacity envelope, decisions, owners, and readiness gaps.
One shared hypothesis ready for refinement.Participation Architecture
Get the right contribution without filling every chair for two days
Attendance is only one way to contribute. Design the shortest reliable path from expertise or authority to the decision window.
Owns several decisions, roadmaps, or integrations and must remain in the shared context.
Needed for a known topic, trade-off, approval, or roadmap update at a scheduled time.
Pulled in when a bounded question arises; the escalation route and fallback are known.
Provides evidence or expertise but does not need to join the decision conversation.
Affected by the result but neither contributes material input nor holds decision authority.
Decision Contract
Give every important decision a minimum preparation standard
What exact choice must be made, by when, and why now?
Who has the final authority, and who drives the preparation?
Which guardrails are hard, which are negotiable, and which are assumptions?
What credible choices and consequences must be compared?
Which facts, roadmaps, capacity views, risks, and confidence levels matter?
Who must agree, contribute, perform, stand by, or be informed?
Which roadmap, backlog, agreement, or decision log becomes the new source of truth?
When is the decision checked, and what evidence could cause it to change?
Six Contribution Modules
Build the conference package one contribution system at a time
-
2.1
Module 1
Portfolio Contributions
Bring strategic intent, decision authority, investment guardrails, and portfolio roadmaps into the conference.
Open module → -
2.2
Module 2
Shared Initiatives & Communities
Prepare the owners and roadmaps for architecture, platform, DevOps, security, compliance, data, and other shared foundations.
Open module → -
2.3
Module 3
Tactical Contributions
Bring delivery reality, capacity boundaries, contribution forecasts, dependencies, and risks from ARTs and other executing units.
Open module → -
2.4
Module 4
Central Functions
Make funding, people, legal, procurement, operations, quality, release, and governance constraints decision-ready.
Open module → -
2.5
Module 5
Suppliers & Partners
Expose external decision rights, lead times, interfaces, commitments, evidence gates, and escalation paths.
Open module → -
2.6
Module 6
Facilitation & Preparation
Turn the decision backlog, invite map, roadmap inputs, and readiness gaps into a runnable conference system.
Open module →
Ready to Begin?
Start with three decisions, not the full invitation list
The first pass should expose missing authority and preparation. It does not need to solve the entire conference design at once.
Bring from Flow Problems
- The top three to ten Flow problems
- Affected objectives, units, and partners
- Evidence, confidence, and validation gaps
- Initial decision and artifact implications
Build in this step
- Decision Contracts and authority map
- Core, window, standby, and preparation paths
- Portfolio, shared-foundation, and tactical input stack
- Readiness gaps with owner and due date
The conference package
- Decision backlog
- Invite and standby map
- Input roadmap stack
- Artifact update responsibilities
- Readiness backlog
Clarify strategic intent, decision authority, and the guardrails that cannot be delegated.
Source Foundation
Deck-led, strengthened by decision and Flow guidance
This overview distills slides 22–28 and 47 of 2026-07-13_Value_Stream_Conference.pptx; the six contribution modules cover slides 29–46. Participation modes, Decision Contracts, reversibility, and decision-Flow measures extend the deck as optional facilitator support.