Accelerate and the Power of Small Batches
As we enter the third section of The Lean Startup (Accelerate), Eric Ries introduces us to one of the most counterintuitive yet miraculous laws of productivity in the business world. The human brain instinctively loves “mass production.” We assume that doing tasks in bulk or large batches saves us time and energy. However, this chapter completely shatters that mental paradigm, proving that the secret to genuine speed lies in working with Small Batches.
To illustrate this concept, Ries provides a brilliant and simple example that is globally recognized as the classic illustration of Lean Management: The Envelope Stuffing Game.
The Envelope Story: Why Our Instincts Are Wrong
Imagine you have 100 paper letters that need to be folded, stuffed into envelopes, sealed, and stamped. If you had to do this, what method would you choose?
Most people (and traditional managers) would choose the “Large Batch” method: fold all 100 letters first, then stuff all 100 envelopes, then seal them all at once. Our minds tell us this is faster because we are hyper-focused on one specific task at a time. However, scientific experiments and time-tracking have repeatedly proven that the “Small Batch” method (completing one single envelope from start to finish before moving to the next) is significantly faster!
“Large batches create a dangerous illusion of productivity. They keep errors hidden until the very last moment. In small batches, you catch and correct the failure immediately.”
Why is the one-piece flow faster? Partly because of the hidden time spent sorting and moving large piles around the desk. But more importantly, it is an issue of Error Detection. Imagine that in the large batch method, you have folded all 100 letters, and you are finally ready to stuff them. Suddenly, you realize the letters are folded slightly too wide and do not fit into the envelopes! A disaster has occurred; you have just wasted the effort of 100 letters. In the small batch (one-by-one) method, you would have discovered this exact error on the first envelope, instantly saving the other 99.
From Toyota to Tech Giants: Defeating Mass Production
This is the exact philosophy that built the foundation of the Toyota Production System (TPS) after World War II. While American automakers in Detroit were manufacturing parts in massive batches of thousands to maintain “economies of scale,” Toyota focused on small batch sizes and continuous flow. As a result, Toyota minimized warehousing costs, discovered defective parts instantly, and conquered the global market at a breathtaking speed.
In the software world, companies like Amazon do not release new code in massive six-month batches. They utilize “Continuous Deployment.” Every line of code written is pushed to the live server in an exceptionally small batch within minutes, allowing the team to measure real user reaction instantly.
📌 Technical Agility: Implementing Small Batches in the Digital World
The biggest mistake in digital product development is the waterfall, bulk-release approach. Having a team code in silence for six months to unveil a massive platform on a single day is a “Large Batch Strategy” that almost always leads to catastrophic failure. Web design, mobile app development, or even the execution of SEO and social media campaigns must be agile, released in small batches, and constantly shaped by market feedback. The Stinoment engineering and digital team manages all its international projects based on agile architecture and micro-releases, reducing your capital risk to zero. If you need a technical team perfectly aligned with Lean Startup standards to develop your platforms or strategically elevate your SEO, you can connect with the Stinoment Client Support Team (led by Hamed Asghari) for expert consultation.
Ultimately, the law of small batches teaches us that the speed of a startup is not defined by how fast you can type code; it is defined by how fast you can complete the entire “Build-Measure-Learn” loop for one tiny feature.
💡 Note from Hamed Asghari (CEO of Stinoment)
One of the most lethal diseases among leadership teams is what I call “Rocket Launch Syndrome.” Executives mistakenly believe that releasing a product should resemble the Apollo 11 launch: years of secretive engineering, monumental budgets, and finally, a historic day to press the red button with media in attendance. This mindset, rooted deeply in the industrial era of mass production, is commercial suicide in today’s tech landscape.
As the leader of a technology agency dealing with dozens of international projects daily, I have clearly observed how working in “Large Batches” drastically inflates organizational anxiety. When you launch a massive feature set after months of labor, and the product fails, pinpointing the fatal bug among thousands of lines of code or hundreds of intertwined strategies is practically impossible. You won’t even know which specific part of that giant package the customer hated!
Conversely, when you break your strategy down into Small Batches, you are essentially building an “immune system” for your business. At Stinoment, we constantly remind our teams that an engineer’s efficiency is not measured by being 100% busy writing code without interruption; true efficiency is measured by the speed at which a tiny idea is delivered into the hands of the end-user and the subsequent learning derived from it. Small batches crush engineering ego, but in return, they absolutely guarantee your business’s survival in a ruthless global market.