The Lake‑Water and Rock Effect: A Metaphor for Managing Work‑in‑Progress and Defect Reduction in Lean Product Development

Lake‑Water and Rock Effect is a metaphor from the book Lean Product Development that compares the amount of work‑in‑progress (WIP) to the water level of a lake and organizational problems to rocks hidden beneath the surface.

当一个湖中有很多水时，水面很高，湖中的石块都被水所覆盖。

When the water level is high, many rocks (issues) are submerged and invisible; as the level drops, larger rocks become visible, followed by medium and small rocks as the surface continues to fall.

The metaphor is used in Chapter 12 of the book to illustrate controlling WIP: the lake level represents the amount of WIP, and the rocks represent internal problems.

How to Apply the Metaphor

Continuous Delivery 2.0 advocates shortening verification loops as much as possible. Over time, verification activities reach a balance that teams are reluctant to disturb because it reflects a tacit agreement among departments.

These activities consist of value‑adding work and non‑value‑adding work (fixed costs), illustrated in the diagram below.

1. What Happens When Iteration Cycles Are Shortened?

When a fixed iteration length is maintained, teams continuously compress non‑value‑adding activities (fixed costs). Shortening the cycle (e.g., from two weeks to one week) without changing work methods increases the proportion of fixed costs, making the output of two short cycles feel less than that of one longer cycle.

The lake‑water metaphor explains this: the iteration cycle is the lake surface, and fixed costs are the rocks. Lowering the surface (shortening the cycle) makes the rocks appear larger, just as the second small ring of fixed cost in the diagram matches the first large ring.

To improve, teams must continue to reduce the fixed costs of the smaller rings before moving to the next level of balance.

2. "Same‑Day Defect, Same‑Day Completion"

When iteration cycles are long, defects tend to accumulate toward the end of the cycle, raising the lake surface of defects. Some teams adopt a principle that any defect found on a given day must be fixed and verified the same day.

有人说：“当日事，当日毕”是一种追求速度的牵引，本身就不利于研发质量。

The author argues this view is mistaken; the principle is valid when quality standards are met.

当我们说“当日事，当日毕”的时候，应该是在质量达标的前提下做出的承诺。

Any commitment must be based on expected quality. Some teams mistakenly rush deliveries, completing work crudely just to meet dates, which undermines quality.

In practice, reducing the "defect lake" to a one‑day surface is challenging at first. The main obstacles are:

Too many defects to fix in a day, indicating poor upstream quality; more effort is needed early to prevent defects.

Long defect‑location time due to difficult test environments, missing logs, etc.; teams must improve debugging infrastructure.

Long defect‑verification time, often because fixing one defect may introduce others; automation and regression testing help.

By addressing these issues, teams can lower the defect lake, achieve faster feedback, and maintain high quality.

— THE END —