High-velocity IT value streams and digital products
What this domain tests
This domain tests whether you can map a value stream, measure its flow, and manage digital products as continuously evolving things rather than one-off projects.
Core concepts
- Value stream: the series of steps an organization uses to create and deliver products and services to consumers. It crosses departments; it is not a process, a team or an org chart.
- Value stream mapping: visualises the flow, separates value-adding from non-value-adding activity (waste), and quantifies it. Key measures: lead time (request to delivery), cycle time (work start to finish), %C&A (percentage of time work arrives complete and accurate), and flow efficiency (work time ÷ lead time).
- Service value chain: the ITIL 4 activities - plan, improve, engage, design and transition, obtain/build, deliver and support - combined into value streams for each product or journey.
- Digital products: software and data-based offerings (apps, APIs, data services) delivered and consumed digitally. They are never "finished"; they evolve, so they need persistent product teams, product owners with outcome accountability, and continuous attention to customer and user experience.
- Product vs project mindset: projects end and disband; products are funded and staffed for the life of the outcome and measured on outcomes, not on delivery of scope.
Worked example
A team maps customer onboarding: lead time 14 days, actual work 2 days, %C&A 40%, with waste in manual credit checks and repeated data re-entry. Flow efficiency is roughly 14%, so most of the delay is waiting and rework. Two changes follow - automate the credit check and remove one handoff - cutting lead time to 4 days. Reasoning: mapping exposes wait time and rework, which is where the leverage is, not faster typing.
Traps that cost marks
- Confusing the value stream with a process or department, then optimising one silo.
- Measuring only activity or utilisation instead of lead time, flow efficiency and outcomes.
- Treating a digital product as a project and dissolving the team at go-live.
- Assuming digital products are static deliverables rather than continuously evolving services.