Wastes 3 & 4: Handoffs and Waiting

Every time work passes from one person or team to another, context is lost.

The product manager writes requirements. They know the user's pain, the business constraints, the priority trade-offs. They hand this to a designer.

The designer reads the requirements, asks clarifying questions (some of which the PM can't answer anymore because context has faded), and creates mockups. They hand this to developers.

The developers read the requirements and mockups, ask clarifying questions (some of which neither PM nor designer can answer anymore), and build something. They hand it to QA.

QA tests against the requirements, finds issues, and hands it back to developers.

At each handoff, information is lost. By the time the feature reaches users, it barely resembles what the PM originally understood about user needs. And each handoff took time—sometimes days waiting in queues.

Handoffs are where context goes to die.

Most of lead time is wait time, not work time. A task that takes 2 hours of active work might have 2 weeks of lead time. Where does the rest go?

• Queue time: Waiting in backlogs for prioritization
• Waiting for review: PRs sitting unreviewed
• Waiting for approval: Decisions stuck in management
• Waiting for dependencies: Blocked on other teams
• Waiting for environments: Can't test because staging is broken
• Waiting for information: Questions unanswered
• Waiting for scheduling: Meetings that can't happen until next week

Each wait introduces delay and often requires re-familiarization when work resumes. You read the code, understand the context, get pulled away, and have to rebuild that context later.

Flow efficiency measures value-add time as a percentage of lead time. In most software organizations, it's 5-15%. That means 85-95% of the time, work is waiting, not being worked.

Cross-functional teams: Bring all skills needed to deliver value onto one team. Product, design, development, testing—all together. Handoffs become conversations.

Generalizing specialists: People who have deep expertise in one area but can contribute in others. When work piles up in review, developers can help review. Fewer queues.

Pair and mob programming: Two or more people working together eliminates handoffs within the work. Review is built in. Knowledge transfer is continuous.

Real-time collaboration: Replace asynchronous handoffs with synchronous collaboration. Instead of writing a spec, have a conversation. Instead of filing a bug, walk over and show the developer.

Eliminate approvals: Most approval steps add no value—they're control mechanisms from low-trust environments. Challenge each approval: What value does this add? Could we get the same benefit another way?

Automate handoffs: If work must transfer, automate the queue. CI/CD pipelines that deploy automatically. PR bots that notify reviewers immediately. Slack integrations that surface blocked work.

The goal isn't to work faster—it's to wait less. Attack the 85%, not the 15%.