Build the capability to design and run Value Stream Conferences.
Explore the complete two-day Value Stream Conference Training online before you book or attend it. Modules 1–6 form Day 1; Modules 7–12 form Day 2.
Two-day training curriculum
Twelve connected modules
The existing training material defines all twelve modules in the learning sequence.
Training Modules Day 1
Training Modules Day 2
-
07
Training module
Dynamic ARTs and Dynamic PI Planning
-
08
Training module
Designing Solution Areas with Collaboration Maps
-
09
Training module
Synchronizing Roles and Events
-
10
Training module
Synchronizing Artifacts and Collaborations
-
11
Training module
Dynamic ART Synchronization
-
12
Training module
The learning architecture behind all twelve modules
Training from the Back of the Room
The content changes from module to module. The learning flow stays recognizable: Connect, Concept, Concrete Practice, and Conclusion.
-
1
The common learning pattern
Every Module Uses the 4Cs
Each module starts with participants' current reality, introduces only the concepts needed for the next step, protects time for practice, and closes by transferring the result forward.
C1 Connection · Usually 5 minutes Enter through current work
Participants connect the module topic to a real situation, open question, visible delay, decision, or experience.
C2 Concept · About 20 minutes Add only useful theory
The trainer introduces the models and distinctions that make the upcoming practice sharper.
C3 Concrete Practice · 15 + 5 minutes Create a visible output
Participants build, compare, prioritize, map, or decide—then debrief what the result reveals.
C4 Conclusion · Usually 5 minutes Close with transfer
The group names the learning, preserves the output, and makes the handoff into the next module explicit.
The architecture is consistent enough to create confidence—and flexible enough to serve the purpose of each module.
Speaker Notes
Facilitator intentIntroduce the common Training from the Back of the Room architecture that applies to all twelve modules—not only to Follow the Flow.
How to facilitate
- Present the 4Cs as the repeating learning path participants will experience in every module.
- Connect each C to a practical purpose: enter through current work, add useful concepts, build something visible, and close with transfer.
- Explain that the pattern creates familiarity while the questions, practices, and outputs change from module to module.
Listen and watch for
- Participants may assume the course is a sequence of presentations. Emphasize that every module contains protected participant work.
- Some people may hear 4Cs as instructional-design jargon. Translate immediately into what they will actually do.
- Watch for the belief that every module must use exactly the same minutes. The architecture is stable; the timing remains adaptable.
Avoid
- Do not introduce the model as a rigid compliance checklist.
- Do not use Follow the Flow examples as though they define every module.
- Do not separate Conclusion from the module handoff; transfer is part of the learning design.
-
2
The default 60-minute rhythm
Protect Practice, Not Slide Time
The exact timing can flex. What remains protected is the progression from relevance to understanding, from understanding to application, and from application to transfer.
-
01
Connect Activate experience and make the module personally relevant.5 min
-
02
Concept Teach the minimum concepts required for a strong practice.≈ 20 min
-
03
Practice Give participants protected time to create a usable output.15 min
-
04
Debrief Challenge assumptions, evidence, quality, and transfer.5 min
-
05
Conclusion Name the result and prepare the next learning step.5 min
Intentional flex bufferUp to ten minutes remain available for transitions, examples, group movement, questions, and module-specific emphasis. This buffer protects the learning flow; it is not an invitation to crowd out the practice.
Speaker Notes
Facilitator intentMake the default 60-minute module rhythm visible while protecting flexibility for transitions, examples, group movement, and module-specific emphasis.
How to facilitate
- Walk through the protected core: five minutes Connect, about twenty minutes Concept, fifteen minutes practice, five minutes debrief, and five minutes Conclusion.
- Name the remaining time as an intentional flex buffer rather than unplanned slack.
- Use the flex buffer for transitions, questions, examples, table movement, or a slightly deeper module-specific concept—not to consume practice by default.
Listen and watch for
- Concept sections tend to expand because trainers have more material than the module needs.
- Groups may require more debrief time when the output exposes disagreement or uncertainty.
- Participants should always know whether they are connecting, learning, practicing, reflecting, or transferring.
Avoid
- Do not present the timing as a stopwatch promise.
- Do not treat the debrief as optional overflow.
- Do not use the flex buffer to add another mini-lecture while the exercise is shortened.
-
01
-
3
One coherent learning journey
The Pattern Stays Stable; the Content Changes
Twelve modules become one course when participants can see what each hour produces and how that output becomes the starting point for the next conversation.
01 Protect practice
When time slips, reduce explanation before reducing participant work.
02 Make outputs explicit
Every module should leave behind an artifact, decision input, shared model, or clearer question.
03 Use debriefs as quality gates
The debrief turns activity into learning and makes the output challengeable.
04 Keep handoffs visible
Each module should make the next module easier to enter and more meaningful to complete.
A module is complete when its learning is visible, its output is usable, and its handoff is clear.
Speaker Notes
Facilitator intentShow how one repeating architecture turns twelve modules into a connected learning journey rather than twelve isolated lessons.
How to facilitate
- Make the intended output explicit before each practice begins.
- Close each module by naming what participants created and how it becomes input for the next module.
- Shorten examples before shortening participant practice; the artifact is where shared capability develops.
Listen and watch for
- A module ending with interesting discussion but no usable output.
- Participants treating an exercise as activity without understanding its connection to conference design.
- Handoffs that remain implicit, forcing the next module to restart the conversation.
Avoid
- Do not invent a different facilitation grammar for every module.
- Do not confuse consistency with repetition; prompts and outputs must remain specific to the module.
- Do not hide unresolved questions. Carry them forward as explicit validation or preparation work.
The learning architecture is visible across the whole training.
The detailed learning content can now be developed module by module while every module keeps the same recognizable 4C learning flow.