Developing and managing capabilities and value streams
What the syllabus expects
You must be able to explain what a capability is, how capabilities combine into value streams, and how both are assessed and improved. A capability is an organisation's ability to do something, formed from people and skills, processes and practices, technology, information and partners. Practices are sets of organisational resources designed for performing work; the service value chain describes generic activities, and value streams are the specific sequences of activities and practices used to deliver a product or service.
Managing them: identify value streams and their demand types; map current state, find constraints and waste, design a future state, then implement incrementally; assess capability gaps against required outcomes; use the continual improvement model and PDCA or DMAIC cycles; measure outcomes rather than activity; govern through portfolios, workforce and skills planning, and supplier and partner capability.
Traps in questions
- Confusing capability (can we do it?), process (a defined sequence of activities) and value stream (the end-to-end route to value).
- Treating a maturity level as the goal: improvement must trace to value and outcomes, not to a score.
- Assuming improvement must be a large programme; small, frequent, measured improvements are preferred.
- Mapping only the technology steps and omitting information flow, approvals and wait states.
- Measuring activity volume where outcome and experience measures are needed.
Worked example
Onboarding a new employee is a value stream: engage, design and transition, deliver and support. It depends on capabilities such as identity and access management and knowledge management. Map the stream, note that most elapsed time is waiting for approvals, then reduce handoffs. Rule of thumb: a value stream starts and ends with the customer; a capability answers "can we reliably do this?".