The Mumbai Dabbawalas: Six Sigma by Hand
Every morning, about 5,000 dabbawalas in Mumbai collect home-cooked lunches from households, move them across a sprawling city by train and bicycle, deliver them to the right offices by midday, and return the empty tins that afternoon, roughly 200,000 lunches a day. They do it with no computers, no GPS, no logistics platform: just a color-coded marking system on the lids and a workforce that has it memorized. The error rate business schools cite sits near Six Sigma, matching or beating technology-heavy logistics networks.
For founders and operators, this case sharpens the instinct that pulls you toward software every time you scale, and questions whether that instinct is right. It asks where you have added technology and complexity that made a process slower and more fragile rather than better. What actually produces the dabbawalas' extraordinary reliability, and how to apply it to your own operations, is the takeaway the app makes concrete.
Frequently asked questions
What is the Mumbai dabbawalas case about?
It is about roughly 5,000 dabbawalas in Mumbai who collect home-cooked lunches, move them across the city by train and bicycle, deliver them to the right offices by midday, and return the empty tins, about 200,000 lunches a day. They do it with no computers, no GPS, and no logistics platform, just a color-coded marking system memorized by the workforce. The case questions the instinct that scaling always requires software.
How accurate is the dabbawala delivery system?
Business schools cite an error rate near Six Sigma, matching or beating technology-heavy logistics networks. The dabbawalas achieve this handling roughly 200,000 lunches a day with about 5,000 workers. Their only tool is a color-coded marking system on the lids.
Why is the low-tech dabbawala system so reliable?
Because the simple color-coded system and a workforce that has it memorized produce extraordinary reliability without the fragility that software and complexity can add. The case argues that more technology does not automatically mean a better process. Sometimes added complexity makes a process slower and more fragile rather than better.
What can founders learn from the Mumbai dabbawalas?
The lesson is to question the instinct that pulls you toward software every time you scale and to find where added technology made a process slower or more fragile. Simple, well-designed systems can outperform high-tech ones. CaseBook turns this into a move you apply to your own company, with an AI coach that reads your answer.