The Principles of Product Development Flow

If you only quantify one thing, quantify the cost of delay.

If you only quantify one thing, quantify the cost of delay. Quantify economics. Product development's primary goal is to make good economic choices. Many organizations focus on proxy variables like cycle time or efficiency without understanding their true economic impact. This leads to suboptimal decisions and missed opportunities. Cost of delay (COD) is crucial. Understanding the economic cost of delaying a project is fundamental. It allows teams to evaluate trade-offs between time, resources, and features. COD helps prioritize work, justify investments in process improvements, and make informed decisions about resource allocation. Use economic decision rules. By establishing clear economic decision rules, organizations can empower teams to make fast, decentralized decisions that align with overall business objectives. For example, on the Boeing 777 project, engineers were authorized to increase unit cost by up to $300 to save a pound of weight, enabling thousands of system-level optimum trade-offs without constant managerial oversight.

Queues are the root cause of the majority of economic waste in product development. Queues are invisible but costly. Unlike in manufacturing, product development queues are often invisible, consisting of information rather than physical objects. This makes them easy to overlook, but their impact is significant, increasing cycle time, risk, variability, and cost while reducing quality and motivation. Understand queueing theory. Key principles include: Capacity utilization increases queues exponentially Variability increases queues linearly Most damage is done by high-queue states Manage queues actively. Strategies include: Control queue size rather than capacity utilization Use WIP constraints to limit maximum queue size Implement fast feedback loops to quickly address emerging queues Apply queueing discipline to prioritize high-value work

We cannot add value without adding variability, but we can add variability without adding value. Embrace beneficial variability. Unlike in manufacturing, some variability in product development can create economic value. This occurs when the positive outcomes of variability (e.g., breakthrough innovations) outweigh the negative outcomes. Understand economic payoff functions. The impact of variability depends on how it's transformed by economic payoff functions. Asymmetric payoff functions can make increased variability beneficial. Manage variability strategically. Approaches include: Variability pooling: Combine uncorrelated random tasks to reduce overall variation Short-term forecasting: Reduce uncertainty by shortening planning horizons Small experiments: Break large risks into series of smaller risks Consequence reduction: Focus on reducing the cost of variability rather than just its amount

Don't test the water with both feet. Small batches yield fast feedback. Reducing batch size accelerates feedback, enabling quicker learning and adaptation. This is particularly crucial in product development, where fast feedback can truncate unproductive paths quickly and reduce the cost of failure. Benefits of small batches: Reduced cycle time Decreased variability in flow Accelerated feedback…