• 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 eLearning
  • Services
    • Kanban Software Solutions
    • Consulting & Coaching
    • Training and Seminars
  • Posts
  • Events
    • Events – Agenda View
    • Events – Calendar View
    • International Service Management Calendar
  • Publications
    • Our Publications
    • Notable Publications
    • Quotes
  • About us

10 Kanban Misconceptions

14 May 2017 by Robert Falkowitz 3 Comments

kanban misconceptionWhen I ask people what they think about kanban, why they do not use it or why they show little interest in learning about it, I sometimes receive surprising answers. Clearly, there are many misunderstandings about kanban, many misconceptions about what it is, how it works, who can use it and what its benefits are. Let me debunk the 10 most common kanban misconceptions I have encountered.

Kanban Misconception #1: Lean and Kanban are two different methods

Sometimes, you will see such strange remarks as, “There are three agile methods: scrum, lean and kanban.” But lean and kanban are not two separate methods. Kanban is a part of lean.

Kanban is the way in which lean organizations operate. This goes straight to the source of lean and kanban, namely, Taiichi Ohno at Toyota. Why does this misconception exist? Probably because some organizations apply certain lean concepts or tools, such as the SIPOC diagram or the identification of forms of waste, but they do not use kanban to manage the flow of their work.

Kanban Misconception #2: Kanban is only for manufacturing

Although the original, systematic development of kanban as a method for managing the flow of work started in manufacturing, with its roots going back much further, kanban has been successfully applied for many types of work, including such types of knowledge work as information technology, product development, marketing and sales, human resource management, finance, customer support, back office operations and so forth. For more information on this question, see my discussion here.

Kanban Misconception #3: Kanban is only for software development

In the area of information technology, kanban has become increasingly popular over the past ten years due to much pioneering work in the area of software development. But the application of kanban to software development owes much to its use in the more general domain of product development. And kanban has been shown to work well in most IT activities. See also Misconception #2.

Kanban Misconception #4: If you are using a card board, you are doing kanban

That’s like saying, “if you are using a pencil, you are writing novels.” While it is true that people using kanban are almost certainly visualizing their work on a card board, the inverse is not necessarily true.

You can use a card board to visualize a push method of managing flow, just as well as a pull method of managing flow. Many software tools have gotten on the kanban bandwagon and have provided a kanban board-style view of the tickets they manage. But these tools often oblige you to work in a push manner, which is antithetical to kanban.

Kanban Misconception #5: Kanban can be used only by small teams

It is true that many people are first exposed to kanban via its use in a small team in a start-up organization. But the benefits increase exponentially when it is applied at a portfolio or an enterprise level. And at the other end of the spectrum, many individuals use kanban to help manage their personal tasks. For more information, see our article here.

Kanban Misconception #6: Kanban is just another hype

Kanban has been in use for more than 60 years and its roots go back much further. It is older than most of the companies in existence today. I daresay that most of today’s companies will go out of business long before kanban disappears as a management method.

Kanban Misconception #7: Kanban is incompatible with regulatory requirements

The most stringent regulatory requirements oblige an organization to have a quality management system in place. This means that the organization must have a defined, documented and well understood way of working; it must track and document the work it does; it must have a method for detecting and correcting defects; and it must have a method for keeping under control any changes to the way it works.

Kanban is not only compatible with all these requirements; the core practices of kanban answer directly to each of those requirements. There is no incompatibility with regulatory requirements. In fact, using kanban is likely to make compliance with regulations a much more natural way of working, better understood by all personnel.

Kanban Misconception #8: Kanban requires that all work items be of the same size

Simply false. Kanban helps us to recognize the advantages of small work items and work items of similar size. But it also recognizes that this is often not the reality. Kanban embraces this form of variation in work and provides techniques for keeping work flowing and making it predictable, in spite of variation in work item size.

Kanban Misconception #9: Kanban is a form of project management

Kanban has been very successful as a method to organize the flow of work in a project. But this does not mean that it is synonymous with project management—it is not. Kanban has also been very successful as a method for managing the flow of a vast array of types of work, ranging from manufacturing, through customer support, through back office operations, and so forth. It is better to think of kanban as a means for managing the flow of work required to deliver one or more services. That service could be the manufacture of an automobile, the creation of a software application, the execution of a marketing campaign, the identification and capture of a criminal, and so on and so forth.

Kanban Misconception #10: Kanban results in fewer employees

Suppose an organization can render 200’000 services per year without using kanban, and can render 1’000’000 services per year with kanban. If management is only concerned with reducing costs, then it might believe that it should reduce the number of resources. But if management is concerned with growing the organization and making more satisfied customers, then it will be happy to use kanban to this end and not to fire its employees. It is not kanban that is the cause of these changes. Rather, it is the vision, or lack thereof, of management that causes organizational changes. Blaming kanban for lost jobs is like blaming a pen for what you write.

Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License The article 10 Kanban Misconceptions by Robert S. Falkowitz, including all its contents, is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.

Summary
10 Kanban Misconceptions
Article Name
10 Kanban Misconceptions
Description
Get the full benefit of kanban thanks to debunking of 10 kanban misconceptions about its applicability, use, scope, purpose and meaning
Author
Robert S. Falkowitz
Publisher Name
Concentric Circle Consulting
Publisher Logo
Concentric Circle Consulting

Filed Under: Kanban Tagged With: agile, kanban, manufacturing, misconceptions, organizational change, project management, scrum

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

Reader Interactions

Comments

  1. AnshumanAnshuman says

    12 August 2017 at 06:55

    SIPOC is it lean concept or six sigma?

    Reply
    • Robert FalkowitzRobert Falkowitz says

      12 August 2017 at 09:54

      I don’t know. When I was first introduced to this tool, it was in the guise of a Lean Six Sigma approach. But the concept is so fundamental that I would not be surprised if it had a completely different origin. After all, Six Sigma was fundamentally a synthesis of existing practices. According to this person, http://www.answers.com/Q/Who_developed_the_SIPOC_model , it was first developed by Peter R. Scholtes.

      Reply
  2. Katya PsalKatya Psal says

    24 November 2019 at 18:37

    Love your “if you are using a pencil, you are writing novels.” statement 🙂 I met with many situations that Kanban was misunderstood, was used in a wrong way and, consequently, was regarded as a very weak tool to organize, plan and monitor your work. Fortunately, there are many materials about these misunderstandings now, like the one above or my favourite https://kanbantool.com/kanban-library/kanban-results/why-does-90-percent-get-kanban-wrong – this knowledge about using Kanban in line with its actual aims is more widespread. Thank you for sharing this knowledge too!

    Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Primary Sidebar

Kanban eLearning

Kanban training online

Recent Posts

  • The role of the problem manager
  • The Three Indicators
  • Visualization of Configurations

Tag Cloud

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

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

This site uses cookies . You accept those cookies when you continue to use this site. Cookie policyAllow cookiesNo 3rd party non-functional cookiesCookie policy
You can revoke your consent any time using the Revoke consent button.Change cookie settings