Find the Shared Work That No Unit Can Sustain Alone
Identify standards, capabilities, and changes that several parts of the value stream must understand, build, follow, or evolve together. Then decide how much shared ownership is actually needed.
- Fast exercise
- 5 minutes
- Full exercise
- 10–15 minutes
- Input
- Landscape + objectives
- Output
- Initiative inventory + ownership gaps
- Next stage
- Value Stream Capacity
Understanding Value Stream Initiatives
A shared initiative is a domain of shared work—not a renamed department
A Value Stream Initiative exists when several units need a common understanding, standard, capability, change, or roadmap. The initiative creates a coordination need because local decisions alone cannot keep the shared concern coherent.
A Community of Practice is one possible pattern. Named representatives, an artifact owner, a temporary problem lab, or an existing forum may be enough.
Running the Exercise
Four moves from shared concern to minimum viable ownership
-
1
Approximately 1–2 minutes
Define the Initiative Candidate
Start with a shared noun phrase and a concrete cross-unit need. Avoid names that merely restate an organization, role, or meeting.
Too broad “Architecture” Names a discipline but does not explain the shared work.
Useful candidate “Cross-ART API and evidence conventions” Names what several units must understand, follow, and evolve together.
Candidate format [Shared concern] + [affected units] + [why coherence matters]Example: “Shared test-environment roadmap across three ARTs and Supplier X so integration evidence arrives before the regulatory gate.”
Speaker Notes
Facilitator intentHelp the group describe a Value Stream Initiative as a shared domain of work rather than as a department, role, or meeting. The output should name what several units must understand, follow, build, or evolve together and why that coherence matters.
How to facilitate
- Start from the Business Objectives and Value Stream Landscape: ask which shared standards, capabilities, or changes are needed across several units to make the objectives realistic.
- Use the candidate format on the slide: shared concern, affected units, and why coherence matters. Push for a concrete noun phrase rather than a discipline label.
- Keep the candidate as a hypothesis. The exercise identifies potential shared work; later preparation decides whether it needs a CoP, roadmap, representative group, or lighter ownership pattern.
Listen and watch for
- Single-word candidates such as architecture, compliance, DevOps, AI, or platform. These may be useful prompts, but they are not yet concrete shared initiatives.
- Department names being used as initiative names, especially when the item says who owns a topic but not what shared work must become coherent.
- A local topic being inflated into a value-stream initiative even though one ART or function can decide and deliver it without cross-unit impact.
Avoid
- Starting with the ownership solution, such as we need a CoP, before naming the shared concern and affected scope.
- Treating every cross-unit dependency as a Value Stream Initiative. A one-time dependency may need a decision or sync, not an ongoing shared initiative.
- Over-refining wording. A rough candidate is good enough when the shared concern, affected units, and coordination reason are visible.
-
2
Approximately 2–3 minutes
Scan Three Initiative Patterns
Use the patterns to widen the search beyond projects. Each pattern can produce standards, communities, ownership, and roadmaps at value-stream level.
Shared standard How we work together Architecture principles, API conventions, Definition of Done, security controls, evidence rules.
Shared capability What many units rely on Platform service, DevOps pipeline, test environment, telemetry, AI or data infrastructure.
Shared change What the value stream must evolve Transformation roadmap, skill shift, operating model, supplier collaboration, toolchain rollout.
ArchitectureCompliance / SafetyDevOps / InfrastructureCybersecurity Toolchain / ALMPlatformAI / DataTransformation / Org Design Quality / V&VSupplier IntegrationRelease / OperationsOwn initiativeSpeaker Notes
Facilitator intentUse the three source-deck patterns—shared standards, shared capabilities, and shared changes—to widen the search beyond projects and departments while keeping every candidate anchored in value-stream-wide coordination need.
How to facilitate
- Walk the group through the three patterns from the deck: shared standard, shared capability, and shared change.
- For each pattern, ask which objectives or Flow issues would become harder if every unit solved the topic locally.
- Use the prompt cloud as a menu, not a checklist. Select only topics that materially affect several parts of the value stream.
Listen and watch for
- The exercise becoming a generic capability catalogue: architecture, cyber, toolchain, platform, AI, quality, supplier integration, and operations should only stay if they create shared work.
- Participants assuming formal Communities of Practice are the default answer for every pattern.
- Important shared changes that do not look technical, such as operating model shifts, supplier collaboration, release readiness, skills, or transformation roadmaps.
Avoid
- Forcing one candidate into only one pattern. A platform initiative may involve a capability, standards, and a change roadmap at the same time.
- Adding all prompt-cloud items because they sound important. The deck explicitly says not every topic needs a Value Stream Initiative.
- Skipping the practical test: several parts of the value stream must follow, build, evolve, or understand the same thing.
-
3
Approximately 2–5 minutes
Triage Every Candidate A, B, C, or ?
Classify quickly. Add notes only where the classification changes preparation work or exposes a risk.
AWe already have it A value-stream-level forum, standard, community, or roadmap exists and is usable.
BWe want / need it It does not exist at value-stream level, but shared work would benefit from it.
CWe do not need it The topic is local, irrelevant for now, or already handled well elsewhere.
?We do not know yet Ownership, effectiveness, scope, or need must be validated.
Simple Initiative Triage Candidate initiative A B C ? Evidence / gap Architecture □ □ □ □ Compliance / Safety □ □ □ □ DevOps / Infrastructure □ □ □ □ Platform / Data / AI □ □ □ □ Supplier Integration □ □ □ □ Own initiative □ □ □ □ Shortcut: when nobody knows, mark “?” and move on. Unknowns become preparation work.
Speaker Notes
Facilitator intentClassify each candidate quickly as already existing, needed, not needed, or unknown so the inventory becomes preparation guidance instead of an endless brainstorm.
How to facilitate
- Apply the A / B / C / ? logic from the reference deck: already have it, want or need it, do not need it, or do not know yet.
- Ask for evidence where it changes the classification: an existing forum, a roadmap, an artifact owner, a decision record, or a known gap.
- When nobody knows, mark '?' and move on. Unknowns become preparation work rather than a reason to stop the exercise.
Listen and watch for
- A claimed 'A' where a forum exists but no one can name the owned artifact, decision right, roadmap, or evidence that it works.
- A claimed 'B' that is really a local improvement wish, not a value-stream-level coordination need.
- Political hesitation around 'C'. It is healthy to keep topics local when the value stream does not gain from broader coordination.
Avoid
- Turning triage into a detailed design workshop. The fast checklist is meant to create a useful inventory quickly.
- Treating '?' as failure. It is a valid outcome and a useful preparation signal.
- Over-trusting the label 'we already have it'. Existing structures still need an effectiveness check before conference preparation relies on them.
-
4
Approximately 2–4 minutes
Name the Minimum Viable Ownership Pattern
For A and B candidates, identify the lightest mechanism that can keep shared understanding, decisions, and artifacts trustworthy. This is a preparation hypothesis—not a permanent organization design.
01Named representatives Each affected unit provides one accountable contact.
02Artifact owner One person keeps a standard, map, backlog, or roadmap coherent.
03Existing forum An established sync absorbs the cross-unit responsibility.
04Temporary decision lab A focused group resolves one bounded shared issue.
05Community of Practice An ongoing community develops shared knowledge and practice.
Capture only five fields CandidateAffected unitsCurrent patternMinimum next patternArtifact / decision ownerOwn idea: Add an explicit expiry or review date to temporary structures. A useful coordination mechanism should not become an immortal meeting by accident.
Speaker Notes
Facilitator intentFor A and B candidates, identify the lightest ownership pattern that can keep shared understanding, artifacts, and decisions trustworthy without turning every initiative into a permanent heavy governance structure.
How to facilitate
- Ask what minimum mechanism would make the initiative decision-capable: named representatives, artifact owner, existing forum, temporary decision lab, or Community of Practice.
- For every selected ownership pattern, name the artifact or decision it protects: roadmap, standard, interface agreement, evidence chain, backlog, dependency map, or operating rule.
- Add a review or expiry point for temporary structures so a useful coordination mechanism does not become an immortal meeting by accident.
Listen and watch for
- Participants solving an organizational design question casually inside a five-minute exercise. Capture the hypothesis; validate it with affected people later.
- Ownership being assigned to a role that lacks decision rights, artifact responsibility, or access to affected units.
- Heavy governance where a named artifact owner or temporary decision lab would be enough.
Avoid
- Equating ownership with meeting attendance. The question is who can keep shared work coherent and update the relevant artifact or decision record.
- Making a CoP the default answer. The deck explicitly leaves the ownership model open until preparation decides what is appropriate.
- Leaving the exercise without a preparation hook: every material A, B, or ? item needs an owner, validation path, or explicit decision to keep it local.
Facilitation
Keep initiatives tied to shared work and observable need
Ask what several units must understand, build, follow, or evolve together. Rename the item around that shared concern.
Offer the lighter ownership patterns. Formality should follow need, not precede it.
Ask which artifact it owns, which decisions it makes, and what evidence shows that it works.
Classify it C without apology. The value stream benefits when coordination is added only where it creates value.
Record the ownership gap as a Flow signal. Do not resolve structural authority casually.
Split it by shared outcome or artifact—for example platform roadmap, evidence standard, and operations readiness.
Ready to Move On?
The inventory is ready when shared work has a visible coordination hypothesis
- Standards, capabilities, and shared changes were all considered.
- Candidates describe shared work rather than departments or meetings.
- Every candidate names the affected units or scope.
- Local work is explicitly kept local.
- A, B, C, and unknown classifications are visible.
- Existing structures have an artifact, decision, or outcome test.
- Needed structures have a minimum viable ownership hypothesis.
- Temporary structures have a review or expiry point.
- Material unknowns have a validation owner.
Source Foundation
This page distills Exercise 1C, slides 12–13 of 05 Value_Stream_Conference.pptx. The ownership extensions remain deliberately pattern-neutral; a Community of Practice is one option rather than the default answer.