A Community Model for Service Excellence


Sitting out in the open in my home office are piles of magazines, consisting mainly of Harvard Business Review, FastCompany, Wired, and various technology variants, almost all of them with dog-earned pages and handwritten notes, waiting to be transcribed and transformed into blog fodder. In fact, I was just chatting with my good friend and fellow blogger Jeff Shuey (@jshuey) about a personal goal to move through some of this backlog, publishing 14 articles in 4 days (just over 2 days to go, with 9 left!).

One of the articles in my backlog is from the November 2012 edition of HBR, entitled  Mumbai’s Models of Service Excellence in which author Stefan Thomke describes the entrepreneurial spirit and legendary reliability of the city’s 5,000+ dabbawalas who each and every day deliver more than 130,000 meals prepared by their customers, in their own homes, out to the customer’s office and then return the empty lunchboxes back to each customer’s home. Thomke shares that the dabbawalas are semiliterate workers who largely manage themselves, and yet have achieved a high level of performance with almost no overhead, not complex IT systems, and most without cell phones. Thomke writes:

“The dabbawalas service is legendary for its reliability. Since it was founded in 1890, it has endured famines, wars, monsoons, Hindu-Muslim riots, and a series of terrorist attacks. It has attracted worldwide attention and visits by Prince Charles, Richard Branson, and employees of Federal Express, a company renowned for its own mastery of logistics.”

After hearing about the success of this poorly educated, decentralized workforce performing with such reliability and predictability in an environment which can easily be labeled chaotic, Thomke traveled to Mumbai to conduct some research o the topic with the help of Harvard Business School’s India Research Center (IRC), where he learned all about the culture and history of the dabbawalas, interviewed workers and supervisors, and observed them in action. What he observed was that the dabbawalas have an overall system consisting of 4 pillars, all of which are, as he puts it, “perfectly aligned and mutually reinforcing.”

What stood out to me about this story was how much the dabbawala pillars matched what experts have found to be true in the successful creation, and sustained health, of communities – and specifically, communities built around social collaboration infrastructures.

  • Organization. Over the course of the day,  a dabbas (a customer’s lunch box) will change hands many times before it reaches its destination, and then is returned back to where it started. There are clearly defined roles and responsibilities, with everyone knowing their part, and what is expected of them. Communities perform best when people know the organizational structure (which doesn’t mean hierarchy, necessarily) and the roles they play within, which allow them to participate more fully. (I often use the phrase “If you don’t know the boundaries of what is expected, how do you know when you’ve exceeded expectations?”)
  • Management. The dabbawalas essentially manage themselves, but they operate with a high level of trust and respect the customer boundaries (no stealing customers) of their fellow dabbawalas. The community policies and enforces rules and guidelines within the organization, which makes solving disputes and reviewing exceptions quick and equitable. Similarly, most communities work best when the organizational layout is clear, and the members self-regulate, adapting and extending roles and rules, as needed.
  • Process. One of the more interesting aspects of the dabbawalas system has been their unique short-hand method for tracking origination and destination locations, using numbers, colors, shapes, and simple alphabetic codes to keep track of their clients. Thy adhere rigorously to their processes and standards, because they rely so much on each other and the organization, and will fine or fire members for repeated mistakes. But their process also empowers every worker to take action to improve customer relations or to deal with issues at any part of the supply chain. Similarly, communities thrive when processes are kept relatively flat and transparent, allowing people to resolve their own issues rather than hand over the wall to a separate IT organization to resolve, empowering people to do the right thing, and to keep the community healthy.
  • Culture. Clearly, being part of the dabbawalas community is a lifestyle , with workers sharing emotional bonds and connections, and many of them spending their entire working lives within the dabbawalas ranks. New workers generally come from friends or family members of the community, and share the same cultural values, language, religious beliefs, and work ethics of the people they work directly with – which is an important aspect of their continued success. As with communities, the ability to identify and collaborate with people who share beliefs and perspectives is an important ingredient to the success of a community. Not that a community can’t be a melting pot of backgrounds and beliefs – this has more to do with being able to surface a shared sense of purpose.

Now, one important aspect of the dabbawalas success has been their need to make this successful. Personally, I think this is above and beyond what the author described as the group’s culture, because it has to do with people’s livelihoods — they push to succeed because they must succeed to survive. Aspects of that are part of the organizational culture, for sure, but I believe it has more to do with the individual drive of its members – akin to those power users or connector personalities who drive our collaborative structures and who hold our communities together. Without that drive, the pillars will fall away.

As Thomke points out, there are some valuable lessons to be learned here. One comment that stood out – and I completely agree with the author – is that a healthy community is constantly reviewing each of these pillars and making adjustments. He shares “When confronted with disappointing results, far too many companies mistakenly think that the remedy is to conduct a purge of employees and recruit some stars.”  But the dubbawalas have shown that by allowing the community to adjust the organization, management, organization, and culture of their community based on the changes and economic realities of their surroundings, they can make the right decisions to keep things moving forward. And since they’ve been around since 1890, they’re obviously doing something right.

Christian Buckley

Christian is a Microsoft Regional Director and M365 Apps & Services MVP, and an award-winning product marketer and technology evangelist, based in Silicon Slopes (Lehi), Utah. He is the Director of North American Partner Management for leading ISV Rencore (https://rencore.com/), leads content strategy for TekkiGurus, and is an advisor for both revealit.TV and WellnessWits. He hosts the monthly #CollabTalk TweetJam, the weekly #CollabTalk Podcast, and the Microsoft 365 Ask-Me-Anything (#M365AMA) series.