What category does Small Batches belong to?

Small Batches belongs to the "Principles" category in personal knowledge management and productivity.

What are the key topics related to Small Batches?

Key topics related to Small Batches include: lean, agile, flow, productivity, software-development.

Small Batches

Q: What are alternative names for Small Batches?

Small Batches is also known as: Small Batch Size, Small Batch Principle, Reduce Batch Size, Single-Piece Flow, One-Piece Flow.

Doing and delivering work in small increments to shorten cycle times, reduce risk, and get feedback sooner.

Also known as: Small Batch Size, Small Batch Principle, Reduce Batch Size, Single-Piece Flow, One-Piece Flow

Category: Principles

Tags: lean, agile, flow, productivity, software-development

Explanation

Working in small batches means splitting work into small pieces and moving each piece through the whole process (build, review, release, feedback) before starting a lot more. It is a central principle of lean manufacturing, Donald Reinertsen's product development flow, and continuous delivery.

## Why Small Batches Win

- **Shorter cycle time**: By Little's Law, less work in progress per item means it gets through the system faster.
- **Shorter queues**: Smaller and more uniform items reduce variability, which, per Kingman's Formula, reduces waiting time.
- **Faster feedback**: You learn whether something works after days rather than months.
- **Lower risk**: When a small change fails, it is easy to identify and roll back. A large release fails in more ways at once.
- **Less waste**: If priorities change, less work in progress is thrown away.
- **More motivation**: Finishing things often provides a steady stream of small wins.

## The Trade-off

Each batch has a transaction cost: setup, review, deployment, coordination. Large batches are tempting when those costs are high. The lean answer is to reduce the transaction cost (automation, simpler processes) so that smaller batches become economical, rather than accepting large batches.

## Examples

- Small pull requests instead of giant ones
- Publishing short articles regularly instead of one perfect long piece a year
- Releasing features incrementally behind flags
- Processing your inbox daily instead of weekly
- Writing a book chapter by chapter with feedback along the way

## Related Practice

Note that this differs from task batching, which groups similar tasks to reduce context switching. Small batches are about the size of the units of work that flow through a process.

Related Concepts

← Back to all concepts