Why Small Batches are the Secret to Extreme Productivity

Would you believe that finishing one entire task before starting the next is faster than doing them in groups? Most people don't, yet this is the core paradox behind the small batches lean startup methodology. By focusing on single units of work, businesses can drastically reduce the time it takes to learn what customers actually want.

Traditional wisdom suggests that working in large groups—like folding 100 letters before stuffing any of them—is the most efficient way to manage time. In reality, this "large batch" approach hides errors and creates massive amounts of rework that slow everything down. Moving to a system that prioritizes the flow of individual items creates a much faster and more reliable business engine.

What is Small Batches?

In his book The Lean Startup, Eric Ries explains that small batches refer to a way of working where you move one piece of work through the entire process before starting the next. This concept is borrowed from the world of lean manufacturing business and is often called "single piece flow." Instead of focusing on keeping every person busy, the system focuses on moving the product through the design and production stages as quickly as possible.

This matters because it's the only way to get through the Build-Measure-Learn feedback loop quickly. In a startup, you aren't just trying to make stuff; you're trying to learn how to build a sustainable business. Small batches ensure that if you're making a mistake, you find out almost immediately rather than weeks or months later.

Finding Quality Defects Faster with Small Batches Lean Startup

When you work in large batches, any error committed at the beginning of the process won't be found until the very end. Imagine you're stuffing envelopes and the letters don't actually fit into the envelopes you bought. If you fold all 100 letters first, you won't realize they're too big until you've already wasted all that time folding.

Using single piece flow, you'd realize the mistake on the very first envelope. This immediate feedback prevents "work-in-progress" from turning into a pile of expensive waste. Toyota famously used this to their advantage by allowing any worker to pull the "andon cord" and stop the entire production line if they found a defect, ensuring quality was built in from the start.

Eliminating the Large-Batch Death Spiral

Large batches tend to grow even larger over time because of the overhead required to manage them. If a team only releases a product once every six months, the pressure to get every single feature into that release is immense. This leads to more bugs, more delays, and more fear of shipping, which only pushes the next release even further away.

Working in small batches breaks this cycle by lowering the stakes of any single release. At IMVU, the startup Eric Ries co-founded, the engineering team made an average of 50 product changes every single day. This rapid pace was only possible because they broke every project into the smallest possible units of work.

Reducing Batch Size to Cut Down Wasted Time

In a typical lean manufacturing business, managers focus on "changeover time"—the time it takes to reset a machine to do a new task. Shigeo Shingo, one of the fathers of the Toyota Production System, found ways to reduce changeover times that took hours down to less than ten minutes. This allowed the factory to produce a wide variety of parts in tiny groups without losing efficiency.

Reducing batch size in a startup works the same way. By investing in tools that automate testing and deployment, teams can switch between tasks without the usual friction. This allows for just-in-time scalability, where you only build the infrastructure you need for the current experiment rather than planning for millions of users before you've even found one.

Real-World Success Stories

Alphabet Energy used this approach to build a thermoelectric device that generates electricity from waste heat. Instead of building a massive, expensive factory, they used the existing silicon wafer infrastructure already used by computer chip companies. This allowed them to go from a product concept to a physical version in just six weeks, a timeline unheard of in the energy sector.

SGW Designworks follows a similar path for physical product engineering. When they were hired to build a complex military x-ray system, they didn't spend months on a master plan. They used 3D computer-aided design to build a virtual model in one day and delivered a machined aluminum prototype just three days later. The entire production run was ready in less than a month.

IMVU's "teleporting" avatars are another example of how small batches reveal what customers actually care about. The team originally thought they needed high-quality walking animations, which would have taken months to build. Instead, they shipped a crude version where avatars just disappeared and reappeared in a new spot; customers loved it, and the team saved months of unnecessary work.

Three Steps to Switch to Single Piece Flow

1. Identify Your Largest Bottleneck

Look at your current workflow and find where the most unfinished work is sitting. This usually looks like a pile of half-written code, a stack of designs waiting for approval, or a long list of features waiting for a monthly release. Focus on moving just one of those items to completion today before touching any others.

2. Automate the Changeover

Invest in the tools required to make switching tasks painless. For software teams, this means automated testing; for service teams, it means clear, simple checklists that are updated in real-time. The less time it takes to move from "idea" to "live," the smaller your batches can become.

3. Establish an Immune System

Create a safety net that automatically catches errors so you can work fast without fear. This could be a "product immune system" that alerts the team if customer sign-ups suddenly drop after a change. If a problem is detected, stop all new work until the root cause is fixed so the mistake isn't repeated.

Where the Small Batch Approach Falls Short

Critics often argue that small batches are inefficient in industries with massive physical overhead, like deep-sea oil drilling or airplane manufacturing. In these cases, the cost of a "set-up" is so high that the math seems to favor large batches. While the physics of those industries are real, the trap is assuming that the entire project must be a large batch.

Even in high-overhead industries, the design and planning phases can still be managed with small batches lean startup techniques. Many projects are called "mission critical" as an excuse to avoid early testing, but this often leads to a massive failure years down the road. The risk is that the team builds a perfect product that the market no longer wants by the time it's finished.

Small batches require a radical shift in how we think about productivity. By finishing work in tiny increments, teams catch errors immediately instead of waiting until the end of a massive project. Start measuring your work in units completed rather than hours spent on a single phase.