2A · Portfolio
Strategic intent, funding, guardrails and epics.
Exercise 2D
Central Function Contributions
Identify central functions that must be represented, prepared or available so the Value Stream Conference can make real decisions — without late surprises from finance, HR, legal, procurement, quality, operations or risk.
Chapter 2 · Getting able to decide
Where Exercise 2D fits.
Exercise 2 turns the discovery outputs from Exercise 1 into a contribution-based invitation and preparation package. Exercise 2D checks which central functions can enable, constrain or invalidate the decisions the Value Stream Conference wants to make.
2B · Value Stream Initiatives
Architecture, DevOps, platform, AI/data and compliance.
2C · Executing Units
ARTs, Solution Areas, teams, departments and capacity realism.
2D · Central Functions
Finance, HR, legal, procurement and support constraints.
2E · External Suppliers
Lead times, interfaces, contracts and partner commitments.
Exercise output
A central-function contribution map: which functions are needed, who represents them, what artifacts they bring, and whether they attend, prepare input or remain on standby.
Explain
What is a central function?
A central function is any non-executing function whose constraints, expertise, approvals, capacity or support can change the Value Stream Roadmap.
Not necessarily outside
Central functions may be outside the agile structure, partially embedded in ARTs, or represented through shared services and enterprise roles.
Not automatically invited
They should be represented only when they own a constraint, capability, decision right, critical knowledge or readiness signal.
Not only governance
Some are gates; others are enablers: funding, hiring, customer rollout, procurement, support readiness and risk treatment.
Not status
Their contribution should change a decision, a roadmap, a capacity assumption or a follow-up action.
Why this matters
Central functions prevent late surprises.
Many flow problems do not come from ARTs or teams. They come from constraints that are discovered too late: legal review, budget gates, compliance obligations, procurement lead times, support readiness or quality evidence.
Decision rights
Someone can approve, reject, adjust or escalate a functional constraint.
Functional truth
The room sees real capacity, lead times, restrictions and support limits.
Artifact owners
The responsible person updates the relevant roadmap, policy, gate or capacity plan.
Fast path
Standby access exists when the issue is rare but critical.
Roadmap realism
The draft no longer assumes money, staffing, approval or readiness that cannot be supported.
Decision-first logic
Start from the top flow problems.
Exercise 1E produced the problem backlog. Exercise 2D asks which central functions can unblock those problems or make decisions about them.
Flow problem
What blocks value flow most strongly?
Decision needed
What trade-off or artifact update would remove friction?
Function needed
Which central function owns part of the decision?
Contribution
Who attends, who is standby, what must be prepared?
Mode
Core, block, standby, artifact-only or out of scope?
Filter
Use the flow-problem backlog as the filter. If a function does not help solve a top problem, it may be standby, artifact-only or out of scope.
Contribution model
People and artifacts must travel together.
For each relevant function, capture people and artifacts together. The conference needs usable decision inputs, not generic updates.
People
Decision maker, domain expert, artifact owner, functional representative or standby path.
Artifacts
Roadmap, capacity plan, policy, guardrail, risk register, release calendar or contract map.
Decision rights
Approve, reject, adapt, escalate, update, commit to support or trigger follow-up.
Constraints
Lead time, budget limit, evidence gate, staffing limit, launch window or support load.
Readiness
What must be true before the conference so this function can contribute usefully?
Right mode
In-room, part-time, standby, pre-brief or artifact-only.
Checklist 1
Do we need central functions at all?
Before listing functions, decide whether Exercise 2D is a core activity, a quick sanity check, or a standby map.
| Question | No | Maybe | Yes | Implication |
|---|---|---|---|---|
| Do top flow problems involve budget, staffing, contract, legal, compliance or support constraints? | □ | □ | □ | If yes, central functions likely need direct representation. |
| Can the Value Stream Conference change or clarify these constraints? | □ | □ | □ | If no, use artifact-only input or escalation after the conference. |
| Are functional artifacts current enough to support roadmap decisions? | □ | □ | □ | If no, define pre-work owners and due dates. |
| Can the right people attend without breaking the room-size limit? | □ | □ | □ | If no, use standby windows or part-time attendance. |
| Would missing central functions create late surprises after the conference? | □ | □ | □ | If yes, include at least decision maker or artifact owner. |
| Do central functions have capacity limits that affect delivery feasibility? | □ | □ | □ | If yes, request a function capacity plan or support forecast. |
Checklist 2
Which central functions are in scope?
Use this as a fast selection list. Add your own functions where your organization has different names or constraints. Do not optimize for completeness; select functions that change roadmap realism, decision speed or risk exposure.
| Central function | Yes | Maybe | No | Decision / constraint pattern | Artifact expected |
|---|---|---|---|---|---|
| Finance / Controlling | □ | □ | □ | funding, cost, ROI, budget move | budget envelope / business case |
| HR / People & Skills | □ | □ | □ | hiring, skills, training, org-change capacity | skill roadmap / staffing plan |
| Legal | □ | □ | □ | liability, terms, legal review, IP | legal constraint list / review lead times |
| Procurement | □ | □ | □ | sourcing, supplier timing, contract gates | supplier / contract timeline |
| Marketing / Sales / PR | □ | □ | □ | launch promise, market window, communication | launch calendar / customer commitments |
| Customer Support / Operations | □ | □ | □ | readiness, service continuity, incidents | support readiness / ops capacity |
| Risk Management | □ | □ | □ | enterprise risk posture, controls, escalation | risk register / mitigation plan |
| Quality / V&V | □ | □ | □ | quality gates, validation evidence, test capacity | V&V plan / evidence gates |
Checklist 3
Choose the lightest representation mode that is still safe.
Not every function needs a full-time seat. Use the weakest mode that still keeps the conference decision-capable.
Core room
Decision is likely, frequent or cross-cutting. The function owns a key constraint or artifact update.
Part-time block
Needed only for a defined agenda block, review or trade-off conversation.
Standby window
Rare but critical decision. Person is reachable and can join immediately.
Pre-brief + artifact
Function input matters, but decisions are unlikely in the conference.
Delegate / representative
Decision-maker cannot attend, but empowered delegate has clear boundaries.
Out of scope
No relevant decision, constraint or artifact for this first conference.
Snippet cards
Pick functions, artifacts and decision patterns.
Use the cards to discover why a central function may be needed in the conference and what it must bring.
Business & people
- Finance / Controlling
- Business Case Owner
- HR / People & Skills
- People Development
- Marketing / Sales
- Public Relations / Communications
- Customer Support
- Operations / Service
Governance & readiness
- Legal
- Procurement
- Risk Management
- Compliance / Safety
- Quality / V&V
- Release Management
- Enterprise Architecture
- Data Protection / Privacy
Artifacts
- Budget envelope
- Functional roadmap
- Function capacity plan
- Lead-time map
- Risk register
- Compliance evidence plan
- Contract / supplier map
- Release / launch calendar
Decision patterns
- Funding trade-off
- Skill bottleneck
- Contract sequencing
- Regulatory gate
- Support readiness
- Launch promise
- Quality / evidence gap
- Risk escalation
Checklist 4
What must each central function bring?
For every function in scope, capture the minimum input needed for decision readiness. Minimum quality beats completeness.
| Input type | Needed? | Owner known? | Good enough when… | Example |
|---|---|---|---|---|
| Functional roadmap | □ | □ | milestones and planned changes are visible | HR skill roadmap / release calendar |
| Capacity plan | □ | □ | support capacity and bottlenecks are explicit | Procurement review capacity |
| Constraints / guardrails | □ | □ | hard vs soft constraints are separated | budget envelope / legal constraints |
| Lead-time assumptions | □ | □ | waiting times and queues are visible | audit window / hiring lead time |
| Decision rights | □ | □ | delegate knows what they can approve | funding change up to threshold |
| Escalation path | □ | □ | who decides next is clear | legal escalation / risk committee |
| Artifact update path | □ | □ | roadmap or register can be changed | risk log / contract map / support plan |
| Standby availability | □ | □ | contact is reachable during decision window | 20-minute join path |
Checklist 5
Prepare the central-function representative.
A representative is useful only if the room understands what they can decide, what they know and what they cannot decide.
Mandate
Can the person make or confirm decisions? What is outside their mandate?
Context
Does the person understand the top flow problems and business objectives?
Artifacts
Which function artifacts must they bring and update during or after the conference?
Capacity
Can they state available support capacity and bottlenecks for the planning horizon?
Boundaries
Which constraints are hard, negotiable, uncertain or only policy interpretations?
Escalation
Who can decide if the representative reaches a boundary?
Standby network
Which SMEs can be pulled in without flooding the conference room?
Follow-up
Which sync or owner will close unresolved functional decisions?
Canvas
Central Function Contribution Board.
Map every relevant central function to the decision, person, artifact and representation mode required for the conference. Use the board as the single preparation backlog for central functions.
| Central function | Person / role | Decision enabled | Artifact brought | Capacity / constraint | Mode | Status |
|---|---|---|---|---|---|---|
| Finance | Missing · Draft · Ready · Standby · Out of scope | |||||
| HR / Skills | Missing · Draft · Ready · Standby · Out of scope | |||||
| Legal | Missing · Draft · Ready · Standby · Out of scope | |||||
| Procurement | Missing · Draft · Ready · Standby · Out of scope | |||||
| Marketing / PR | Missing · Draft · Ready · Standby · Out of scope | |||||
| Customer Support / Operations | Missing · Draft · Ready · Standby · Out of scope | |||||
| Risk / Compliance | Missing · Draft · Ready · Standby · Out of scope | |||||
| Quality / V&V | Missing · Draft · Ready · Standby · Out of scope | |||||
| Own function | Missing · Draft · Ready · Standby · Out of scope |
Canvas
Function artifact and capacity readiness board.
Use this when a central function must prepare a roadmap, capacity plan or constraint view before the conference.
| Function | Artifact / roadmap | Owner | Time horizon | Capacity / lead time | Decision supported | Readiness |
|---|---|---|---|---|---|---|
| Finance | Budget envelope | □ Missing · □ Draft · □ Ready | ||||
| HR / Skills | Skill roadmap | □ Missing · □ Draft · □ Ready | ||||
| Legal | Legal constraints | □ Missing · □ Draft · □ Ready | ||||
| Procurement | Contract / supplier map | □ Missing · □ Draft · □ Ready | ||||
| Support / Ops | Support readiness | □ Missing · □ Draft · □ Ready | ||||
| Risk / Compliance | Risk + evidence plan | □ Missing · □ Draft · □ Ready | ||||
| Quality / V&V | V&V capacity / gates | □ Missing · □ Draft · □ Ready | ||||
| Own function | □ Missing · □ Draft · □ Ready |
Canvas
Decision-to-function matrix.
Start with the top flow problems. Then mark which central functions are needed to make or validate the decision.
| Flow problem / decision | Fin | HR | Legal | Proc | Mkt/Sales | Support/Ops | Risk/Comp | Q/V&V | Other | Invite mode |
|---|---|---|---|---|---|---|---|---|---|---|
| Problem 1 / decision | □ | □ | □ | □ | □ | □ | □ | □ | □ | Core · Block · Standby · Artifact-only |
| Problem 2 / decision | □ | □ | □ | □ | □ | □ | □ | □ | □ | Core · Block · Standby · Artifact-only |
| Problem 3 / decision | □ | □ | □ | □ | □ | □ | □ | □ | □ | Core · Block · Standby · Artifact-only |
| Business objective risk | □ | □ | □ | □ | □ | □ | □ | □ | □ | Core · Block · Standby · Artifact-only |
| Roadmap trade-off | □ | □ | □ | □ | □ | □ | □ | □ | □ | Core · Block · Standby · Artifact-only |
| Capacity / lead-time issue | □ | □ | □ | □ | □ | □ | □ | □ | □ | Core · Block · Standby · Artifact-only |
| Release / launch issue | □ | □ | □ | □ | □ | □ | □ | □ | □ | Core · Block · Standby · Artifact-only |
| Open decision | □ | □ | □ | □ | □ | □ | □ | □ | □ | Core · Block · Standby · Artifact-only |
Canvas
Invite / standby map for central functions.
Decide who needs a seat, who needs a defined timebox, and who only needs to be reachable.
| Function | Core room | Block only | Standby | Artifact only | Named contact / role | Time window / trigger | Escalation |
|---|---|---|---|---|---|---|---|
| Finance | □ | □ | □ | □ | |||
| HR / Skills | □ | □ | □ | □ | |||
| Legal | □ | □ | □ | □ | |||
| Procurement | □ | □ | □ | □ | |||
| Marketing / PR | □ | □ | □ | □ | |||
| Support / Ops | □ | □ | □ | □ | |||
| Risk / Compliance | □ | □ | □ | □ | |||
| Quality / V&V | □ | □ | □ | □ | |||
| Own function | □ | □ | □ | □ |
Standby rule
No other meeting during the standby window, reachable channel defined, and the decision trigger is visible to facilitators.
Facilitation
Run Exercise 2D in four passes.
A compact sequence keeps the conversation focused on decisions rather than stakeholder completeness.
Select functions
Use the function checklist to mark Yes / Maybe / No. Do not discuss names yet.
Connect decisions
Map top flow problems to central-function decisions and constraints.
Choose representation
Decide core room, part-time block, standby, artifact-only or out of scope.
Define preparation
Name the artifact, owner, capacity view, decision right and readiness status.
Known gaps
Stop when every top decision has either a prepared contribution or an explicit gap owner.
Facilitator prompt
“Which central function can actually change the outcome of this flow problem — and what artifact would make the decision responsible?”
Fast mode
10-minute version for a 90-minute workshop.
Use this version when Exercise 2D is one micro-step inside a larger Value Stream Conference preparation workshop.
Frame
Only map functions that affect top flow problems.
Checklist
Mark central functions: Yes / Maybe / No.
Decisions
For each top problem, mark the needed function.
Mode
Core room, block only, standby or artifact-only.
Output
Capture top 3 gaps and owners.
Debrief
Are central functions conference-ready?
Use these questions to decide whether Exercise 2D produced enough preparation input.
Decision relevance
Can we explain why each selected function is needed for a top flow problem or roadmap decision?
Representation
Do we know who represents the function and what mandate they have?
Artifact readiness
Are required roadmaps, capacity plans, constraints and risk views named and owned?
Room-size discipline
Did we keep observers out and use standby where possible?
Update path
Do we know which artifact changes during or after the conference?
Gaps
Are missing inputs captured as preparation work with owners and dates?
Exercise 2D output
Central-function contribution package.
When Exercise 2D is done, the preparation team knows which central functions must shape the Value Stream Conference: function map, decision matrix, artifact stack and readiness gaps.