Make the Draft Roadmap Respect Real Capacity and Local Constraints
Bring the people and artifacts that expose what ARTs, Solution Trains, Solution Areas, platforms, suppliers, and other executing units can credibly contribute. Tactical roadmaps are realism filters—not detailed plans written on behalf of teams.
- Fast exercise
- 5 minutes
- Full exercise
- 15–25 minutes
- Input
- Capacity + Flow-problem backlog
- Output
- Contribution and capacity board
- Next module
- Central Functions
Understanding Tactical Contribution
The conference needs a credible boundary, not a promise of perfect delivery
Tactical units contribute the information needed to test feasibility: committed work, capacity allocation, enabler demand, dependencies, risks, options, and what they cannot absorb without a trade-off.
The conference does not decompose every feature or predetermine implementation for the people doing it.
Show what the unit can contribute, under which assumptions, with which dependencies and confidence.
Show the consequence of adding demand: delay, displacement, capacity change, risk, or reduced scope.
Capacity as a Realism Filter
Bring the full demand on the unit into view
Running the Exercise
Four moves from executing units to a capacity-realistic contribution system
-
1
Approximately 2–4 minutes
Map Executing Units to the Decisions
For each Decision Contract, identify which tactical units contribute capacity, absorb consequences, own dependencies, or possess delivery knowledge. Reuse the Value Stream Landscape rather than drawing a second organization map.
TeamImplementation reality Feasibility, learning, quality, skill, and local dependency signals.
Solution AreaCloser collaboration scope Local objectives, cross-team options, interfaces, and contribution choices.
ARTTrain roadmap and capacity Objectives, feature and enabler horizon, dependencies, risks, and Flow constraints.
Solution TrainCross-ART integration Solution intent, milestones, system integration, shared risks, and capability sequencing.
Platform / serviceShared enabling capacity Service demand, adoption, roadmap, operating constraints, and bottlenecks.
Supplier unitExternal contribution Commitments, lead time, interfaces, test capacity, and contract boundary.
Mapping prompt Which unit must change its roadmap, capacity, interface, or commitment if this decision is made?Speaker Notes
Facilitator intentConnect Decision Contracts to the executing units that contribute capacity, absorb consequences, own dependencies, or hold delivery knowledge, without turning the conference into detailed team planning.
How to facilitate
- Reuse the Value Stream Landscape and map each decision to Teams, Solution Areas, ARTs, Solution Trains, platforms, suppliers, or other executing units.
- Ask which unit must change its roadmap, capacity, interface, or commitment if the decision is made.
- Mark both contributors and consequence carriers. Sometimes the unit that suffers the impact is not the unit that performs the visible work.
Listen and watch for
- Only ARTs being mapped while platforms, suppliers, shared services, test labs, or Solution Areas carry the real constraint.
- A unit listed because it is organizationally nearby, not because it changes capacity, dependency, risk, or evidence for the decision.
- Detailed implementation debates starting before contribution boundaries are visible.
Avoid
- Drawing a second org chart. This is a decision-to-contribution map, not a reporting-line model.
- Equating named involvement with reliable capacity. Capacity, confidence, and constraints come next.
- Assuming teams can absorb every higher-level decision without displacement or trade-off.
-
2
Approximately 3–5 minutes
Select the Reality Holders
Choose people for the information and authority a decision needs. One representative may cover several roles; a job title alone does not guarantee capacity insight or implementation credibility.
RTE / train FlowSystem impediments Dependencies, planning constraints, escalation needs, and train-level Flow.
Product ManagementRoadmap and scope trade-offs Features, objectives, sequencing, customer need, and product decisions.
System ArchitectTechnical feasibility Runway, interfaces, enablers, integration risk, and option consequences.
Business OwnersValue and acceptance Outcome expectations, local business trade-offs, and governance signals.
Solution Area / team repsLocal options and constraints Skill, work detail, feedback, quality, and practical contribution choices.
Test / integration / supplier repsSpecialized bottlenecks Environment, evidence, acceptance, lead-time, and external interface reality.
Representation rule Choose the smallest set that can explain the boundary, offer alternatives, and commit the affected artifact to refinement.Speaker Notes
Facilitator intentSelect the smallest set of people who can explain delivery reality, offer alternatives, and commit the relevant artifact to refinement without pretending to plan work on behalf of teams.
How to facilitate
- Choose roles for the information and authority they bring: train Flow, Product Management, architecture, Business Owners, Solution Area or team reps, test, integration, and supplier reality.
- Separate forecast authority from execution commitment. Representatives can bring a boundary; teams still refine and commit later.
- Use participation modes: core for recurring decision material, window for known topics, standby for bounded questions, preparation-only for evidence.
Listen and watch for
- Representatives who can report status but cannot explain what capacity, quality, dependency, or roadmap change would be required.
- Teams missing from validation when the decision meaningfully changes their local work system.
- A job title used as proof of reality. Ask what the person can explain, update, validate, or escalate.
Avoid
- Crowding the room with every possible expert. Choose by decision need and response-time risk.
- Delegating feasibility judgment to people too far from the work when uncertainty is high.
- Letting a representative commit teams to implementation details the teams have not yet refined.
-
3
Approximately 4–7 minutes
Prepare Tactical Contribution Roadmaps
Use the same horizon and confidence language across units where possible. Show only enough detail to test the Value Stream draft and locate the decisions that teams must refine later.
Committed horizon Current objectives, major features, enablers, milestones, and obligations.
Capacity distribution Rough buckets, source, confidence, persistent demand, and credible flex.
Contribution forecast What the unit can plausibly contribute to each shared objective or initiative.
Dependencies Cross-ART, shared-service, supplier, environment, and decision dependencies.
Constraints Skills, architecture, quality, evidence, operations, lead time, and availability.
Risks and unknowns Assumptions, blockers, validation needs, probability, impact, and owner.
Options Sequence, scope, split, swap, enable, stop, or learn-before-commit choices.
Cannot absorb The demand or date that becomes implausible without an explicit trade-off.
Confidence rule: A rough estimate with a source and confidence is more useful than a precise number whose assumptions are invisible.
Speaker Notes
Facilitator intentPrepare tactical contribution roadmaps that make committed demand, capacity distribution, dependencies, risks, options, confidence, and cannot-absorb boundaries visible enough for value-stream trade-offs.
How to facilitate
- Ask each unit for the same minimum horizon and confidence language so the value-stream draft can compare units without erasing local detail.
- Include committed horizon, capacity distribution, contribution forecast, dependencies, constraints, risks, options, and cannot-absorb statements.
- Tie each roadmap item to a decision or objective; remove detail that does not affect a conference choice or refinement handoff.
Listen and watch for
- Roadmaps that show desired new work but hide KTLO, maintenance, compliance, incidents, quality work, or support load.
- Different units using incompatible bucket language, creating false capacity comparisons.
- A precise number with no source, confidence, assumption, or owner.
Avoid
- Turning the roadmap into a full feature breakdown. That belongs in ART and team refinement.
- Averaging capacity across units too early. The constraints usually sit in the differences.
- Asking for commitment before the conference has resolved the higher-level trade-space.
-
4
Approximately 4–7 minutes
Expose Capacity Boundaries and Decision Consequences
Complete the board per tactical unit. The final column should name the choice the conference can make—not merely repeat that the unit is busy.
Contribution and Capacity Board Tactical unit People to involve Committed horizon Capacity buckets Credible flex Dependencies / risks Decision enabled Confidence ART A RTE, PM, Architect Compliance + maintenance 35 / 15 / 15 / 20 / 5 / 5 / 5 5–10% shared test lab sequence enabler M Platform PM, service owner Telemetry rollout 32 / 12 / 18 / 20 / 8 / 4 / 6 6% cloud lead time phase adoption M Supplier X Supplier PM, tech lead Interface V2 22 / 20 / 10 / 18 / 20 / 4 / 6 0–6% contract window fund change L Capacity boundary statement If [new demand] enters by [horizon], [unit] must displace, delay, split, or enable [existing demand], because [constraint], with [confidence].H · current data + owner validated M · credible estimate + known assumptions L · directional estimate ? · validation owner requiredSpeaker Notes
Facilitator intentTranslate tactical contribution data into decision consequences: what must be displaced, delayed, split, enabled, or accepted as risk when new value-stream demand enters the system.
How to facilitate
- Complete the contribution board and ensure the final column names the decision enabled, not merely that the unit is busy.
- Use the boundary statement format: new demand, horizon, unit, displaced or enabled work, constraint, and confidence.
- Look for credible flex rather than imaginary spare people: timing, sequence, scope, automation, sourcing, investment, or learning-before-commit.
Listen and watch for
- No-capacity statements that end the conversation without naming options, displacement, or escalation paths.
- Flex capacity that has the wrong skill, timing, location, contract, or dependency context to help the decision.
- Low-confidence tactical forecasts being treated as commitments because the conference needs an answer.
Avoid
- Solving capacity by casually moving people between stable teams. First examine demand, priorities, skills, and Flow through constraints.
- Using the board to blame delivery units for systemic overcommitment.
- Closing the module without naming what the conference must decide to make the roadmap realistic.
Facilitation
Protect team planning while making system-level trade-offs unavoidable
Return to objectives, milestones, contribution, capacity, dependencies, and decisions. Teams refine detailed work later.
Include collaboration, learning, variability, support, quality, and buffer. A fully loaded system cannot absorb change.
Clarify what they can forecast, what needs team refinement, and which authority must join the decision window.
Align only the distinctions needed for the trade-off. Preserve local detail outside the conference view.
Ask what would need to stop, move, split, automate, enable, or be accepted as risk.
Choose a reversible decision, a learning milestone, or a named validation before treating the forecast as a commitment.
Ready to Move On?
Tactical contributions are ready when the roadmap can be tested against a credible delivery boundary
- Every material decision is mapped to the affected executing units.
- Representatives bring capacity insight, product context, technical feasibility, and local reality where needed.
- Tactical roadmaps remain forecasts and inputs rather than imposed detailed plans.
- Committed work, shared work, KTLO, maintenance, compliance, learning, and buffer are visible enough.
- Contribution forecasts state assumptions and confidence.
- Cross-unit, supplier, platform, environment, and decision dependencies are visible.
- Each unit names credible flex and what it cannot absorb.
- Adding demand exposes the displaced work or enabling investment.
- Unknowns have validation owners and dates.
- The board names the conference decisions that tactical evidence enables.
Source Foundation
This page distills slides 35–37 of 2026-07-13_Value_Stream_Conference.pptx. Confidence, displacement, and “cannot absorb” statements strengthen capacity as a decision input without converting the conference into detailed planning.