Map the Contributor Network Before Mapping Its Problems
Create a working hypothesis of every internal and external unit that contributes to the selected value stream. Capture enough structure, scale, roles, and decision interfaces to support the next four diagnostic stages.
- Fast exercise
- 5 minutes
- Full exercise
- 10–15 minutes
- Input
- Value-stream boundary
- Output
- Contributor inventory + validation gaps
- Next stage
- Business Objectives
Understanding the Landscape
Begin with who contributes—not with an idealized process diagram
The first map is a contributor landscape: the people, teams, trains, functions, suppliers, platforms, and operational actors that jointly turn a trigger into value. It is deliberately incomplete and provisional. Its purpose is to make the coordination system discussable.
Contributor Network
Who belongs in the value stream? What scale, roles, interfaces, and confidence do we know?
Useful before conference designDetailed Process Map
How does a specific work item move step by step, and where do time and information accumulate?
Useful for deeper Flow validationUnknown contributors, counts, and decision interfaces remain on the map as explicit validation gaps. A visible question mark is more useful than an invisible assumption.
Running the Exercise
Four moves to a usable Value Stream Landscape
Use the presentation controls on each card to move through the exercise without manual scrolling.
-
1
Approximately 1–2 minutes
Set a Workable Boundary
Name the product, service, customer journey, or operational outcome whose Flow you want to improve. Identify the trigger and the value delivered without attempting a complete process decomposition.
TriggerWhat starts demand? Customer need, regulation, incident, order, strategic intent, or operational signal.
ScopeWhich value stream are we diagnosing? Name the product or service boundary and relevant planning horizon.
ValueWhat becomes usable? Customer, user, operational, regulatory, or business outcome.
Our map is good enough when everyone can tell which contributors belong in this value stream—and which belong outside today’s boundary.
Speaker Notes
Facilitator intentCreate a workable diagnostic boundary before the contributor inventory starts. The goal is not to map the whole enterprise, but to name the trigger, value, and scope that determine who belongs on this first Value Stream Landscape.
How to facilitate
- Start with the concrete value stream the conference preparation is meant to improve: a product, service, customer journey, regulatory flow, operational outcome, or integrated solution path.
- Ask for the trigger and the usable value first. This keeps the group from beginning with departments, reporting lines, or the latest transformation structure.
- Make the boundary provisional and visible. Use an adjacent parking area for nearby value streams or supporting systems that matter, but should not define today's diagnostic unit.
Listen and watch for
- A scope that is too broad, such as the whole company, the whole portfolio, or all software delivery. That usually prevents a usable contributor map.
- A scope that is too narrow, such as one ART or one team, when suppliers, central functions, platforms, or operations materially affect the value delivered.
- Participants switching immediately into process steps. A process map can come later; this slide is about agreeing which value stream and contribution system are being diagnosed.
Avoid
- Trying to settle every boundary debate before starting. Record unresolved boundary questions as validation gaps and continue.
- Letting the most senior organizational view define the value stream automatically. The boundary should follow value, trigger, and outcome, not only hierarchy.
- Confusing the map with a commitment to reorganize. This is a working hypothesis for conference preparation, not an operating-model decision.
-
2
Approximately 2–4 minutes
Capture Every Contributor Type
Use the eight prompts to prevent the map from ending at the Agile organization chart. Add named units only where they affect the selected value stream.
01ARTs Teams, capacity, and ART-level decision roles.
02Solution Trains Several ARTs or large-solution structures sharing direction.
03Solution Areas / Domains Closer collaboration areas, components, or capabilities.
04Central Functions Finance, HR, Legal, Procurement, Compliance, Security, Architecture.
05Suppliers / Partners External teams, test labs, certification, cloud, or platform partners.
06Traditional Departments Line units, projects, programs, PMO, or governance boards.
07Shared Platforms Infrastructure, toolchain, DevOps, data, AI, and shared services.
08Customers / Operations Service, support, users, customers, and readiness functions.
Facilitator prompt: “Who can delay, enable, approve, operate, validate, or learn from the value—even if they do not sit inside an ART?”
Speaker Notes
Facilitator intentExpand the map beyond the agile delivery structure so the group sees every contributor, constraint owner, and feedback actor that may affect value-stream Flow and conference decision readiness.
How to facilitate
- Walk through the eight contributor prompts from the reference deck: ARTs, Solution Trains, Solution Areas or domains, central functions, suppliers, traditional departments, shared platforms, and customers or operations.
- For each contributor, ask why it belongs: it delivers, enables, approves, validates, operates, funds, constrains, supplies, or provides feedback for the selected value stream.
- Use local names first and add the contributor type second. The room needs shared recognition more than perfect framework terminology.
Listen and watch for
- A map that stops at ARTs and teams. That usually hides the central functions, platforms, suppliers, evidence chains, and operational feedback loops that later create conference decisions.
- A generic stakeholder list. The deck asks for contributors, constraints, and decision interfaces—not everyone who has an opinion about the topic.
- External partners or operations being mentioned late with phrases like they just need to approve it, they only provide the environment, or we tell them afterwards.
Avoid
- Adding contributors just because they are politically important. If their connection to the selected value stream is unclear, mark the reason-to-coordinate as unknown.
- Debating whether something is a domain, Solution Area, department, platform, or function for too long. Use the label participants understand and move on.
- Treating absent contributors as known. If supplier, customer, operations, legal, or compliance reality is missing, write a validation gap instead of inventing it.
-
3
Approximately 2–5 minutes
Build the Fast Inventory
Mark what exists. Add counts and names only where participants can estimate them quickly. Keep “unknown” available so the group does not manufacture certainty.
Value Stream Inventory Structure element Select Count Names People Agile Release Trains □ yes □ no □ ? Solution Trains □ yes □ no □ ? Teams outside ARTs □ yes □ no □ ? Domains / Solution Areas □ yes □ no □ ? Central functions □ yes □ no □ ? Suppliers / partners □ yes □ no □ ? Traditional departments □ yes □ no □ ? Shared platforms / services □ yes □ no □ ? Fast-mode rule: if the answer is unknown, keep it on the map as a validation gap instead of stopping the exercise.
Speaker Notes
Facilitator intentConvert the contributor conversation into a fast inventory that is complete enough for conference preparation while keeping uncertainty visible instead of manufacturing precision.
How to facilitate
- Use the inventory as a speed device: yes, no, or unknown first; count, names, and people only where the group can estimate quickly.
- Preserve unknowns. A question mark is not a failure of the exercise; it is a preparation item for interviews, data checks, or invite validation.
- Separate existence from confidence. The group may know that a supplier or platform is involved but not know its people count, decision owner, lead time, or readiness impact.
Listen and watch for
- False certainty in counts and people numbers. Ranges and confidence levels are more useful than precise but unsupported figures.
- Participants stopping the exercise because one row is unknown. Use the deck's fast-mode rule: keep the unknown on the map and continue.
- Duplicated units under different names, especially where line organization, ART structure, platform ownership, and supplier structure overlap.
Avoid
- Turning the five-minute fast inventory into an enterprise architecture repository or HR data cleanup effort.
- Deleting unknown rows to make the map look complete. The next stages need to know where confidence is low.
- Asking for exact capacity allocation too early. This stage only captures rough contributor scale; Value Stream Capacity comes later.
-
4
Approximately 2–4 minutes
Mark Confidence, Gaps, and Decision Interfaces
Enrich each mapped unit with the minimum information needed for later diagnosis. Do not add detail merely because it is available.
01Name + Type Use the language participants recognize.
02Rough People / Teams Enough to understand social scale and capacity.
03Key Roles Who owns work, knowledge, artifacts, and decisions?
04Reason to Coordinate Which objective, initiative, interface, or constraint connects the unit?
05Confidence / Gaps High, medium, low, or unknown—with a validation owner.
H · corroborated M · credible estimate L · weak evidence ? · validateOwn idea: Add one thin “decision-interface” line only where a unit can create material waiting through approval, prioritization, compliance, funding, or scarce expertise. This prepares the later Ability to Decide analysis without turning the map into spaghetti.
Speaker Notes
Facilitator intentAdd only the minimum decision-useful information to each mapped unit: name and type, rough scale, key roles, reason to coordinate, and confidence or gaps, including the interfaces that may later become Flow problems or Ability-to-Decide issues.
How to facilitate
- For every material unit, ask for the five fields from the source deck: name and type, rough people or teams, key roles, reason to coordinate, and confidence or gaps.
- Mark decision interfaces only where they can create material waiting: approval, prioritization, funding, compliance, architecture, supplier commitment, operations readiness, or scarce expertise.
- Assign a validation owner to important low-confidence items. This turns a rough map into a preparation backlog for the later conference design.
Listen and watch for
- Interface lines multiplying until the map becomes spaghetti. Keep only links that matter for Flow, capacity, risk, evidence, or decisions in the selected scope.
- Roles being named as generic titles without decision or artifact ownership. Ask what the role can decide, update, validate, block, or escalate.
- Gaps that belong to later exercises, such as detailed objective priority, full capacity split, or exact problem ranking. Capture the pointer, then move on.
Avoid
- Treating confidence as an afterthought. Confidence is part of the output because it tells the facilitator what must be validated before the conference.
- Adding every meeting, sync, and governance touchpoint as an interface. The page is preparing diagnosis, not documenting the full meeting system.
- Closing the landscape as done without naming the next validation path. Important gaps need an owner, a source, or a decision about whether they matter.
Facilitation
Protect speed without hiding uncertainty
Return to the trigger and value. Ask what each unit contributes, enables, approves, validates, operates, or learns.
Use their local name and add a type in smaller text. Shared understanding matters more than framework vocabulary.
Record a range and confidence. Name a data owner. Continue the exercise.
Show only coordination that can materially change Flow, capacity, risk, or decisions in the selected scope.
Do not invent their reality. Mark the interface and invite a representative into validation or the conference-design team.
Use a parking area for adjacent value streams. Keep today’s diagnostic unit coherent enough to act on.
Ready to Move On?
The landscape is useful when it supports the next question
It does not need to be complete. It needs to be explicit enough to connect objectives to real contributors.
- The value-stream trigger, value, and working boundary are named.
- ARTs, Solution Trains, Solution Areas, and teams in scope are visible.
- Central functions, suppliers, platforms, traditional units, and operations were considered.
- Rough scale and key roles are recorded where useful.
- Every material contributor has a reason to coordinate.
- Known decision interfaces are visible without mapping every meeting.
- Uncertainty is marked with confidence or a question mark.
- Each important gap has a validation owner or follow-up path.
Source Foundation
This page distills Exercise 1A, slides 8–9 of 05 Value_Stream_Conference.pptx, and preserves the existing contributor-network distinction. Current-state and whole-system guidance is supported by the Lean Enterprise Institute.