Waiting waste is time lost when work cannot proceed because feedback, input, a decision, or another process step has not arrived. In software, it often hides behind activity: people switch tasks while pull requests, tests, or environments remain queued. Lead time still grows, and delayed feedback makes it harder to respond while the work is fresh. section 2.4.4
Waiting is a diagnostic lens, not a judgment about individual effort or a rigid classification. It can combine with other wastes: slow validation creates queues, while late feedback can lead to parallel work and rework. The useful question is where the system delays information or decisions that could arrive sooner. section 2.4.4 section 2.4
Look for waiting in familiar engineering workflows:
- Pull requests sit for days awaiting review, or test environments are unavailable. section 2.4.4
- A small change queues behind slow validation, long test suites, or sequential security scans. section 6.5.2
- Feedback depends on full integration with infrastructure or external services, making a simple behavior expensive to check. section 2.4.4
Listing 2.4 Waiting waste
@Test
void createsUser_integration() {
UserService service = new UserService(
new RealDatabase(),
new RealEmailClient()
);
service.createUser("user@example.com");
}
This test constructs a service with a real database and email client, illustrating how simple validation can depend on slow, environment-sensitive integration. section 2.4.4
When validation becomes the queue
A team expands integration coverage and adds scanning stages; build time rises from 12 to 42 minutes, and three commits queue behind one another. Coding faster does not remove this constraint. Parallelization, layered testing, and post-deploy validation can protect flow while retaining deep validation. section 6.5.2
Ask where information could arrive earlier, which feedback comes too late to change behavior, and how much waiting has become normal. Testing can add value; waiting for tests does not. Find the delay in the whole flow, not just the time spent coding. section 2.4.4 section 6.5.2
