Workflow optimization is the practical end of operational efficiency. Where efficiency is the principle, workflow is where the principle meets specific work. The techniques below produce concrete improvements in days to weeks - and the improvements compound when documented and shared.

Five techniques that work

1. Map the actual workflow

Most workflow improvements start with mapping how work actually moves through the business. Not the idealized version - the real one.

  • Pick a specific piece of work (an order, an invoice, a customer onboarding)
  • Follow it through the system, step by step
  • Note every wait, handoff, and decision point
  • Time each step honestly

The map almost always reveals waste invisible from inside any single step.

2. Find the bottleneck step

The step where work piles up. Look for queues, backlogs, or steps where multiple people are waiting on one. That's where throughput is constrained.

Improving non-bottleneck steps doesn't increase throughput - the bottleneck still limits total output. Focus there first.

3. Batch similar work

Context-switching is expensive. Each switch from one type of work to another costs 5-15 minutes of re-orientation. Batching reduces the switches.

Common batching opportunities:

  • Process invoices on Friday, not daily
  • Hold customer calls in 90-minute blocks
  • Block calendar time for deep work
  • Group similar projects under one focus period

4. Parallelize where possible

Steps that don't depend on each other can run at the same time. Linear workflows that have parallelizable sections are usually wasting time.

Common parallelization:

  • Sales proposals: legal review can happen alongside technical scoping, not after
  • Customer onboarding: training can happen alongside setup, not after
  • Hiring: reference checks can happen alongside final interviews

5. Remove waiting

Most workflow time is waiting - for approvals, for responses, for the next person's availability. Removing or reducing waits often produces the biggest wins.

Tactics:

  • Eliminate approvals that always approve
  • Set response-time expectations explicitly
  • Use async communication for status, sync for blockers
  • Identify and remove dependencies that aren't real

Document and share improvements

One person's workflow improvement is valuable. The same improvement adopted across the team is multiplicatively more valuable. Document changes; share them; update process documentation. See Business Processes Explained.

Common mistakes

1. Optimizing non-bottlenecks

Improving steps that aren't the constraint doesn't increase throughput.

2. Removing slack that's actually load-bearing

Some "waste" is buffer that prevents larger problems. Remove with care.

3. Optimizing for speed at the cost of quality

Faster but worse isn't an improvement. Watch quality metrics during workflow changes.

4. Solo optimization

Workflow improvements that one person discovers but doesn't share, end with that person. Document.

Related concepts