Landscape
Which units jointly create value?
Exercise 1E
Prioritize Value Stream Flow Problems
Turn symptoms into a prioritized backlog of flow problems the Value Stream Conference must be able to discuss, decide on and remove.
Context
Exercises 1A–1D describe the system. 1E asks what prevents it from flowing.
By now the group has a first picture of the Value Stream landscape, business objectives, shared initiatives and capacity reality. Flow problems are the practical obstacles that slow, block, distort or rework value creation across that system.
Objectives
Which outcomes are on the table?
Initiatives
Which shared foundations matter?
Capacity
Where does capacity actually go?
Flow Problems
What prevents better flow?
Exercise output
A prioritized flow-problem backlog.
The goal is not to solve the whole list. The goal is to create a decision-focused backlog: which problems must the first conference be able to address?
Unsorted problem list
A checklist-supported list of symptoms, blockers and repeated friction points.
Evidence and scope
Which units, objectives and Value Stream parts are affected? What evidence exists?
Flow category
Classify problems by WIP, bottleneck, handoff, feedback, batch, queue, policy or domain constraint.
Priority backlog
Rank the problems that most need cross-unit coordination or conference-level decisions.
Definition
What counts as a Value Stream flow problem?
A flow problem is anything that repeatedly slows down, blocks, distorts or reworks value creation across the Value Stream. Local problems can be captured, but high priority belongs to problems that require shared decision power or shared preparation.
Delay
Work waits for decisions, handoffs, reviews, environments, suppliers or capacity.
Rework
Work returns because quality, architecture, compliance or requirements were unclear.
Overload
Too much WIP, too many parallel initiatives or overloaded specialists create queues.
Fragmentation
Different tools, standards, boards, roadmaps or definitions create friction.
Late learning
Feedback from users, system demos, telemetry, tests or compliance comes too late.
Policy constraint
Funding, contracts, governance, approvals or org boundaries prevent fast collaboration.
Value Stream-level test
If one team or one ART can solve the issue alone, capture it, but do not over-prioritize it for the Value Stream Conference. If several units must decide together, it belongs high on the backlog.
Research lens
Eight flow-problem lenses.
Use these lenses to avoid a blank-canvas brainstorm. They help the group search for recurring interruptions, not one-off irritations.
WIP / Flow load
Too many active initiatives, features, defects or dependencies.
Bottlenecks
Specialists, environments, approvals or suppliers constrain the whole system.
Handoffs
Work crosses boundaries with waiting, information loss or unclear ownership.
Feedback
Customer, system, telemetry, test or compliance feedback arrives too late.
Batch size
Requirements, releases, integrations or decisions are too large to move fast.
Queues
Decision, review, test, legal or procurement queues grow faster than they clear.
Realignment
The system cannot respond quickly enough to change, learning or disruption.
Legacy policies
Funding, contracts, governance or process rules prevent flow-oriented decisions.
Evidence
Make problems credible enough to drive preparation.
The first backlog should be defensible, not perfect. A strong problem statement has at least one symptom, one affected scope and one reason why the conference should care.
Flow metrics
Flow time, flow load, flow efficiency, predictability, WIP, throughput or cycle time.
Delivery metrics
Lead time, deployment frequency, recovery time, change fail rate or deployment rework.
Lean waste signals
Waiting, rework, over-processing, inventory/WIP, handoffs or unused knowledge.
Roadmap signals
Repeated re-planning, unstable assumptions, unresolved dependencies or missed handoffs.
Workshop evidence
Repeated examples from several units, dot votes or “this happens every PI”.
Business impact
Objective delayed, capacity consumed, customer promise at risk or compliance gate missed.
Canvas 1
Flow Problem Discovery Board.
Capture candidate problems before ranking them. Keep wording short. Symptoms first, evidence second, solution ideas later.
Discovery Board
Symptom → Evidence → Scope
Problem / symptom
What is repeatedly slowing, blocking or distorting flow?
Evidence
What examples, metrics or repeated observations make it credible?
Affected units
Which ARTs, suppliers, functions or roadmap layers are touched?
Objective impacted
Which business objective, compliance window or customer promise is affected?
Category
WIP, queue, bottleneck, handoff, feedback, batch, policy or domain constraint.
Owner / follow-up
Who can clarify evidence or prepare the next conversation?
Problem statements
Turn symptoms into decision-ready statements.
A precise problem statement makes the priority discussion much faster. It also prevents the conference from becoming a complaint forum.
Because
Recurring symptom or constraint.
Affected scope
Units, suppliers, functions or roadmap layer.
Cannot
Flow effect: wait, rework, overload, miss feedback or delay.
Impact
Objective, customer, compliance, cost or predictability effect.
Decision need
What must be decided, prepared or owned?
Canvas 2
Flow Problem Prioritization Canvas.
Score the strongest problems to build the first decision backlog. Use the numbers to structure conversation, not to create fake precision.
Impact
How strongly does the problem delay, block or rework value?
Scope
How many units, ARTs, suppliers or functions are affected?
Urgency
How soon will the problem hurt objectives or delivery windows?
Coordination need
How much cross-unit decision-making is required?
Conference leverage
Can a conference meaningfully reduce the problem?
Quick formula
Priority Score = Impact + Scope + Urgency + Coordination Need + Conference Leverage. In very short workshops, skip numeric scoring and dot-vote on: “Which problems most need Value Stream-level coordination?”
Snippet prompts
Flow Problem Snippet Cards.
Use the cards as prompts, then translate them into local language and concrete examples. Labels without evidence do not make a backlog.
Too Much WIP
Everything starts; little finishes.
Decision Queue
Work waits for portfolio, architecture, legal, procurement or leadership decisions.
Specialist Bottleneck
A few people are required everywhere.
Late Architecture
Architecture decisions or interface contracts arrive after teams commit work.
Integration Cliff
Integration, validation or release problems appear too late to fix cheaply.
Supplier Waterfall
Supplier contracts, milestones or cadence force sequential handoffs.
Capacity Surprise
KTLO, maintenance, incidents or compliance consume capacity not visible in planning.
Evidence Gap
Safety, audit, compliance or cyber evidence is created after implementation decisions.
Release Window Mismatch
Hardware, software, cloud, supplier or compliance release windows do not line up.
No Shared Roadmap
Objectives, architecture, suppliers, capacity and risks are not visible in one roadmap.
Decision Without Owner
Problems are discussed repeatedly but no one can decide or update the artifact.
Realignment Too Slow
Change is detected, but the Value Stream cannot gather the right people fast enough.
Fast mode
15-minute version for a 90-minute workshop.
Use this when Exercise 1E must be done under severe time pressure. It creates a usable priority list without deep analysis.
Checklist scan
Mark only obvious Yes items. Skip Maybe debates.
Add own problems
One card per participant or group. Symptoms first.
Cluster and name
Group similar problems into 5–8 clusters.
Dot vote
Vote: which problems most need Value Stream coordination?
Top backlog
Write top 5 with owner or evidence follow-up.
Debrief
Turn the backlog into conference preparation.
Close Exercise 1E by making the top problems visible enough to drive Exercise 2: decision capability, invitees and preparation inputs.
Top problems
Which 5–10 problems most constrain Value Stream flow?
Decision needs
Which problems require real decision power in the conference?
People needed
Who must be in the room or on standby to address them?
Artifacts needed
Which roadmaps, evidence, capacity views or risk data must be prepared?
Preparation owner
Who clarifies evidence, scope, decision rights or follow-up before the conference?
Output statement
“Our first Value Stream Conference must be able to address these top flow problems: [list]. For each problem we know the affected units, evidence, expected decision need and preparation owner.”
Handoff to Exercise 2
The top flow problems define decision capability.
The next step is to design who must participate, which inputs must be prepared and what the conference must be able to decide.