The six forms of waste in knowledge work:

1. Multitasking

• Context switching destroys throughput. Research shows switching between two projects costs 20% productivity; three projects costs 40%.
• A person "working on" three projects simultaneously is less productive than working on one and finishing it first.
• The illusion: multitasking feels productive. The reality: nothing finishes.

2. Half-Done Work

• Unfinished features, open PRs sitting in review, code waiting for QA, designs waiting for approval.
• This is inventory — it consumes effort to create, delivers zero value until complete, and decays over time as the codebase changes around it.
• Every half-done item is a hidden cost: context to maintain, merge conflicts to resolve, decisions to remember.

3. Extra Features (Gold-Plating)

• Building things nobody asked for or will use.
• The Standish Group found that 64% of software features are rarely or never used.
• Every extra feature is code to maintain, test, and document — forever.

4. Handoffs

• Every time work passes from one person or team to another, context is lost.
• Developer to QA, designer to developer, product to engineering — each handoff drops information.
• Cross-functional teams eliminate handoffs by putting all necessary skills on one team.

5. Waiting

• Waiting for approvals, waiting for environments, waiting for decisions, waiting for other teams.
• In most organizations, work items spend more time waiting than being worked on.
• The fix: empower teams to make decisions, automate environment provisioning, remove approval bottlenecks.

6. Heroics

• Working 80-hour weeks to hit a deadline, then burning out.
• Heroics mask systemic problems. If you need heroes, your process is broken.
• Sustainable pace is not soft — it is the only way to maintain quality and throughput over time.