The Principles of Product Development Flow¶
Reinertsen, D. G. (2009). The Principles of Product Development Flow: Second Generation Lean Product Development. Celeritas Publishing.
Cited by¶
10 citations across 10 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Batch Size
- And the feedback-lag dimension means that when the operation itself is being improved, small batches accelerate the learning signal and compound over time, so they can dominate at long horizons even where they lose on any single trade-off snapshot.
This sourceArgues that reducing batch size shrinks feedback lag and risk in product development (the Batch Size Feedback and Risk Principles), with batch size as a central control knob.
- And the feedback-lag dimension means that when the operation itself is being improved, small batches accelerate the learning signal and compound over time, so they can dominate at long horizons even where they lose on any single trade-off snapshot.
- Diminishing Incremental Gains
- Reinertsen (2009) builds his entire Principles of Product Development Flow program on this premise: queue-length, cycle-time, and cost-of-delay metrics surface the marginal economics that intuition silently mis-prices.
This sourceBuilds an economic framework around queue size, cycle time, and cost of delay so the marginal economics of work-in-progress — normally hidden by aggregate metrics — become continuously visible.
- Reinertsen (2009) builds his entire Principles of Product Development Flow program on this premise: queue-length, cycle-time, and cost-of-delay metrics surface the marginal economics that intuition silently mis-prices.
- Optionality
- Distinguishing rational optionality from indecisive option-hoarding requires discipline and clear triggering conditions for exercise, a discipline Reinertsen (2009) operationalizes as work-in-progress limits and cost-of-delay accounting in product-development flow.
This sourceBuilds an explicit economic framework around queue size, cycle time, and cost of delay so that the marginal economics of work-in-progress and batch sizes—normally hidden by aggregate metrics—become continuously visible to product-development decision-makers.
- Distinguishing rational optionality from indecisive option-hoarding requires discipline and clear triggering conditions for exercise, a discipline Reinertsen (2009) operationalizes as work-in-progress limits and cost-of-delay accounting in product-development flow.
- Prioritization
- Many failing initiatives persist because the true opportunity cost remains hidden; prioritization exposes it, as Reinertsen (2009) argues in his economic framing of cost-of-delay-driven sequencing.
This sourceBuilds an explicit economic framework around queue size, cycle time, and cost of delay so that the marginal economics of work-in-progress and batch sizes—normally hidden by aggregate metrics—become continuously visible to product-development decision-makers.
- Many failing initiatives persist because the true opportunity cost remains hidden; prioritization exposes it, as Reinertsen (2009) argues in his economic framing of cost-of-delay-driven sequencing.
- Resource Management
- Static Quotas Waste Capacity; Dynamic Allocation Causes Unpredictability** (a tension Reinertsen (2009) treats as central to product-development flow, where over-reservation of capacity compounds queue costs while excessive variability destabilizes throughput):
This sourceBuilds an explicit economic framework around queue size, cycle time, and cost of delay so that the marginal economics of work-in-progress and batch sizes—normally hidden by aggregate metrics—become continuously visible to product-development decision-makers.
- Static Quotas Waste Capacity; Dynamic Allocation Causes Unpredictability** (a tension Reinertsen (2009) treats as central to product-development flow, where over-reservation of capacity compounds queue costs while excessive variability destabilizes throughput):
Domain-specific¶
- Cumulative flow diagram
- Overburden Waste (Muri)
- . Lean construction — crews scheduled at unsustainable pace under fixed-deadline pressure (Lean Construction Institute), so defects, rework, and injuries rise and schedules paradoxically slip. Lean software engineering — teams loaded beyond sustainable velocity (Reinertsen's Product Development Flow), eroding quality, growing technical debt, and burning out on-call rotations
This sourceReinertsen's principle that capacity utilization increases queues exponentially and that the resulting queues degrade quality, efficiency and cycle time.
Supported in partVerified against a saved copy of the source
“The Principle of Queueing Capacity Utilization: Capacity utilization increases queues exponentially.”
- . Lean construction — crews scheduled at unsustainable pace under fixed-deadline pressure (Lean Construction Institute), so defects, rework, and injuries rise and schedules paradoxically slip. Lean software engineering — teams loaded beyond sustainable velocity (Reinertsen's Product Development Flow), eroding quality, growing technical debt, and burning out on-call rotations
- Requirements Churn
- The measurement move is direct: track the rate of specification amendment against the rate of work completion; when the former exceeds the latter, the team is not the constraint
This sourceReinertsen's queue-and-flow account of product development, in which the arrival rate of work and the bottleneck's capacity govern system throughput.
Supported in partVerified against a saved copy of the source
“In particular, the variability in the arrival rate of work is determined”
- The measurement move is direct: track the rate of specification amendment against the rate of work completion; when the former exceeds the latter, the team is not the constraint
Mechanisms¶
- Decision Clock
- Its strength is that it makes the cost of delay legible — the quantity a group feels but rarely names — so that analysis paralysis has to argue against a visible number rather than hide behind "let's be thorough."
This sourceMakes cost of delay explicit as an economic quantity for comparing time-sensitive decisions.
- Its strength is that it makes the cost of delay legible — the quantity a group feels but rarely names — so that analysis paralysis has to argue against a visible number rather than hide behind "let's be thorough."
- Portfolio Tradeoff Review
- Loading a portfolio past its capacity does not politely queue the extra work — it degrades throughput for everything, because high utilization multiplies delay across the whole system
This sourceShows that rising capacity utilization drives nonlinear queue growth and therefore longer waiting time.
- Loading a portfolio past its capacity does not politely queue the extra work — it degrades throughput for everything, because high utilization multiplies delay across the whole system
Verification¶
Does it exist? Confirmed. This work's ISBN resolves to a registered record, which fixes its identity. That is all it fixes.
Does it back the claim? Read against the text for 2 of 10 citations: 2 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Links previously used in the corpus¶
Before the registry existed this work was also linked 2 other ways.
- https://search.worldcat.org/title/The-principles-of-product-development-flow-%3A-second-generation-lean-product-development/oclc/768093403 ×1
- https://www.google.com/books/edition/The_Principles_of_Product_Development_Fl/1IjPQwAACAAJ ×1
Registry ID ref:afbb9fc2b0cd · see in the full table