• Skip to main content
  • Skip to primary sidebar

This view of service management...

On the origin and the descent of managing services. We put meat on the bones.

  • Kanban Software
  • Services
    • Kanban Software Solutions
    • Consulting & Coaching
    • Training and Seminars
  • Posts
  • Events
    • Events – Agenda View
    • Events – Calendar View
  • Publications
    • Our Publications
    • Notable Publications
    • Quotes
  • About us

Gandhi and continual improvement

2 July 2016 by Robert Falkowitz

Last week I saw a film about the group Ekta Parishad.1 This group applies methods derived from Mohandas Gandhi to help dispossessed Indians to regain their land and livelihood. The film centered on one of the main activities of the group, which is the training of the dispossessed people from a certain region on how to exercise their rights and protect themselves in a non-violent way.

During that training, the film shows a discussion of the results of what was evidently a brainstorming session about the issues facing the community. These issues included such problems as insufficient funds, lack of food, no teachers, low salaries, loss of local traditions, no hospitals or medicines and so forth. When I saw this list, I immediately thought of the results of such sessions when a group of IT people describe the problems they are facing. Until they receive further training, such lists are almost always the same: lack of resources (that eternal complaint!); lack of skills; poor documentation; inadequate tools; etcetera, etcetera and so forth, as the king said.

The leader of the Ekta Parishad meeting then swept aside that list, saying that it is very superficial. He then started a list of problems that he, himself, saw while touring the village concerned. “Why is the village so dirty?” “Why has the canal bringing water to the village pump been blocked for days?” “Why do children defecate in the streets?” The list could have grown very long.

Those of us accustomed to a lean approach to improvement will immediately recognize that the group leader has done a gemba walk. He is espousing the principle of genchi genbutsu, “go and see”. In short, rather than generating a theoretical list of issues, inevitably pre-digested, often conventional, biased and poorly actionable, problems should be described in terms of what you can detect at the place where the work is being done.

What I found worthy of note is the fact that this approach to improvement, if really based on the teachings of Gandhi, predates the lean methods developed at Toyota by several decades. My knowledge of what Gandhi really said and did is largely anecdotal, based more on films rather than gone and seen for myself what he wrote. But he is now on my reading list. Perhaps he provides many other insights that we can use today to improve how we work.

Horizontal bar

1Karl Saurer, Ahimsa. Die Stärke von Gewaltfreiheit, 2012.

Summary
Gandhi and continual improvement
Article Name
Gandhi and continual improvement
Description
Are the methods of non-violence espoused by Mohandas Gandhi a potential source for the continual improvement of work?
Author
Robert S. Falkowitz
Publisher Name
Concentric Circle Consulting
Publisher Logo
Concentric Circle Consulting

Filed Under: Continual improvement Tagged With: ahimsa, continual improvement, Gandhi, gemba walk, genchi genbutsu, non-violence

Subscribe to our mailing list

Click here to be the first to learn of our events and publications
  • Email
  • Facebook
  • LinkedIn
  • Phone
  • Twitter
  • xing
  • YouTube

Primary Sidebar

Kanban eLearning

Kanban training online

Recent Posts

  • Verbs, nouns and kanban board structure
  • The role of the problem manager
  • The Three Indicators

Tag Cloud

kanban training cause agile ITIL process metrics waste impact incident management tools priority change management ITSM kanban board service request process lead time risk resource liquidity flow incident kanban flow efficiency manifesto service manager value stream histogram automation process definition rigidity statistical control chart context switching Cost of Delay Incident Management lean management lean knowledge management bias problem knowledge work manifesto for software development service management tools
  • Kanban Software
  • Services
  • Posts
  • Events
  • Publications
  • Subscribe
  • Rights & Duties
  • Personal Data

© 2014–2023 Concentric Circle Consulting · All Rights Reserved.
Concentric Circle Consulting Address
Log in

Manage Cookie Consent
We use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
Manage options Manage services Manage vendors Read more about these purposes
View preferences
{title} {title} {title}