Value Streams
End-to-end delivery of an outcome, and where the waiting happens.
5 to work through
-
intermediate
A commerce platform's engineering throughput is high but features take months to reach merchants. Where does value-stream mapping look, and what does it typically find?
2 min answer -
intermediate
A quick-commerce business running dark stores maps the value stream for "launch a new product category". The map has five boxes - groomed, built, reviewed, tested, deployed - totalling 11 working days with flow efficiency of 46%. On the strength of it, leadership funds a £600k pipeline programme to cut the 11 days. Review the map and the decision.
3 min answer -
intermediate
A quick-commerce business wants to improve its ten-minute promise. The engineering team optimises the checkout API. Why is that likely the wrong target?
2 min answer -
intermediate
Delivery feels slow and leadership wants a productivity initiative. You propose mapping the value stream first. What will you map and what do you expect to find?
1 min answer -
advanced
Delivering one customer outcome requires six teams. What is that telling you architecturally and what would you change?
2 min answer
2 terms in this topic
Flow Efficiency
The proportion of elapsed lead time in which work is actively being done - typically very low, which is why optimising engineering throughput address…
conceptValue Streams
The end-to-end sequence from a customer's trigger to their outcome — the frame that shows whether teams are aligned to flow or to function.
Neighbouring topics
Business Architecture
General material on the business side of architecture.
Business Capabilities
What a business does, stated stably and independent of implementation.
Capability Mapping
Overlaying systems onto capabilities to expose duplication and gaps.
Business Processes
How work actually flows, including the handoffs nobody documented.
Domain Boundaries
Where the language of the business changes, and services should too.
Stakeholder Analysis
Who is affected, what they need, and who can block you late.
Product Thinking
Treating platforms and services as products with users and a lifecycle.
Business KPIs
The numbers a design is ultimately judged against.
Regulatory Constraints
Non-negotiable requirements that remove design options entirely.
Organisational Constraints
Team structure, skills and budget cycles as architectural inputs.
Time to Market
The constraint that dominates most products, and how to trade against it.
Build vs Buy
Differentiation versus table stakes, priced over five years.
Business Cases
Expressing an architecture proposal in the currency that gets funded.
Operating Models
How delivery, platform and governance functions fit together.
Team Topologies
Stream-aligned, platform, enabling and complicated-subsystem teams.
Platform as a Product
Adoption earned rather than mandated, with an owner and a roadmap.
Outcome Measurement
Knowing whether the thing you built achieved what it promised.
Portfolio Prioritisation
Choosing between investments with incomparable benefits.
Business Continuity
What the business does while the system is unavailable.