• 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

Is Kanban a Visual Management Method?

12 February 2019 by Robert Falkowitz Leave a Comment

Many people, especially those working in tech­nical areas, have at least heard of kanban. Ask them what kanban is and you are likely to get an answer of the sort, “Isn’t it a visual method for managing projects?”1 Well, that’s like saying that Michelangelo’s Sistine Chapel ceiling is a decoration. It’s true, but it is very far from capturing its essence.

If you are an experienced kanban coach or professional, you will probably find the following re­marks to be trivial. But suppose you have simply heard of kanban, without having gained practical ex­peri­ence. Or suppose you do use kanban and you are happy with its definition as a visual ma­nage­ment method. I would suggest that the principle benefits of kanban come from something other than visu­alizing your work on a card board.

Visualization of work is a good start

Kanban steps
Fig. 1: An example of a card board used to support the kanban method

For some people, the maturity level of their organization’s use of kanban gives the impression that kanban is just a visual ma­nage­ment method. For, in fact, most people first perceive kanban as the card board used to visualize their work.

True, this visualization greatly benefits most organizations. You frequently hear remarks such as, “We have never really seen all the different types of work we do before using this card board!”  Visualization assembles for us the data set corresponding to the work in the offing, in progress and completed. The more that data set is but a small selection of your tasks or subject to selection bias, the more your decisions based on that data will be ill advised. The poorer will your system be for managing the flow of work. In fact, the visu­a­li­zation of your work in the form of a card board confirms in a very intuitive way that you are truly attempting to manage the flow of all your work.

Think of what happens in many traditionally managed projects. The project manager attempts to create a detailed plan of all the tasks required to complete the project. But, when the project falls behind and the project manager attempts to understand the causes of delay and blockage, he or she often discovers that people perform many tasks for the project that were not planned at all. Or, it turns out that resources perform more work on non-project ac­ti­vi­ties than initially planned.

So, it is important to be aware of all the work being done by a team. Visualization on a board is one method to help achieve this goal.

A question of maturity

So, you are doing a good job of visualizing your work. Great! But how are you using that visualization to improve the flow of your work? In many org­aniza­tions, you do little or nothing in that regard.

In some cases, your team recognizes that the kanban method comprises much more than visualization. But you are limited to the visu­a­li­zation practice simply because you are only on your first steps of the kanban journey. Good management of the flow of work requires that people become accustomed to creating cards for their tasks and moving those cards from value stream phase to value stream phase (see Fig. 1). Without this basic tracking of work, all the rest of workflow management is extremely dif­ficult to implement ef­fec­tively.

In other words, the team is on the path to improving its work flow using kanban, but is at a low level of maturity. That’s fine, so long as the team does not stagnate at that level.

A question of misconception

On the other hand, many teams or individuals stop at visualization due to various misconceptions about kan­ban. Here are three common misconcep­tions that I will examine in more detail:

  • Kanban boards are necessary to work ac­cord­ing to the kanban method
  • Kanban is a project ma­nage­­ment method
  • Kanban is a view on your tic­ket­ing tool queues

Misconception #1 - Kanban boards are necessary

As useful as they are for knowledge work, card boards are not essential to the use of kanban. Unfortunately, many organi­za­tions believe that kanban is nothing more more than the visualization of work on a board. In fact, using a card board to facilitate the management of flow is an invention that expanded the use of kanban from managing manufacturing to managing the flow of knowledge work, too. In the Toyota Production System, where kanban was invented, kanban cards are not displayed on a board at all!2 Kanban cards exist, but they are used with the batches of materials used to build auto­mo­biles.

Cards are not on boards for sales and manufacturing

kanban card used to manage re-supply of retail stock
Fig. 2: Kanban card in a retail store

If you use kanban to manage your stock in a retail store, you are likely to put kanban cards on the shelves with the mer­chan­dise. They signal to stock managers that it is time to fetch more goods from the stock room. You are likely to see a part number, a quantity to resupply and the location from which the parts should be fetched.

If you use kanban to manage the manufacture of physical goods, you probably keep those cards in the batches of materials used as input to each processing station in the manufacturing process. They signal the frequency of the resupply of input materials at each station in the manu­fac­turing process.

kanban card and bolts
Fig. 3: Kanban card used in manufacturing

Card boards are used for knowledge work

However, knowledge work, unlike retail sales and manu­fac­turing, manipulates data, ideas and know­ledge, rather than tangible mate­ri­als. You cannot attach a phy­sical kanban card to an intangible concept. Data and in­for­ma­tion are hidden from sight. They reside in our brains or in the memory of computers. There is no easy way to position kanban cards in either place (given existing tech­no­logy).

The kanban board allows us to virtualize the value stream we use, displaying it as columns and rows in a table. The kanban cards symbolize batches of work (work items). They are positioned in the appropriate cells of that table, thereby sym­bo­liz­ing, the status of each work item in the value stream.

Are kanban card boards necessary for using kanban for knowledge work? In principle, they are not. How­ever, whether that board is a physical board or a virtual board displayed using soft­ware, most organizations find them to be the easiest, most intuitive way to visualize their work. But the essence of kanban is not in the board itself. It is in the techniques used to manage the flow of work—that work made visible via the card board.

Think of a kanban board as a form of virtual tele­metry used to manage the flow of work. It is like a thermometer used to display the current tem­perature. Measuring the tem­pe­ra­ture is great, but com­pletely valueless unless you make decisions based on those readings. Visualizing work is fine, but only insofar as it gives you the data you need to make decisions about managing the flow of your work.

Is a card board the best way to visualize work? Many org­a­ni­zations find this to be true. Is a card board the only way to visualize work? That is surely not the case. But what else is there? I have elsewhere discussed the use of Marey charts and Sankey diagrams. In the spirit of kanban, teams should experiment col­la­bo­ra­tively to find visual­iza­tion techniques that best meet their own needs, culture and experience.

Misconception #2 - Kanban is a project management method

False! This misconception is a case of putting the cart before the horse. Kanban is a flow ma­nage­ment method for any form of work. Since some work is organized in projects, the flow of work in a project can be managed using kanban. However, the over­whelming amount of work managed using kanban is not project work (unless, of course, you were led to believe that kanban is only for managing projects).

In fact, org­aniza­tional units should use kanban to manage all their work, whether in a project or not. If you try to use kanban to manage only the work done in a project, ignoring what the project team members do out of that project, kanban is likely to be a relatively ineffective me­thod. You might get some benefit from it, but nothing like its true potential.

Misconception #3 - Kanban is a view on your ticketing tool queues

Today, many ticketing tool products are jumping on the kanban bandwagon. They add views of ticket queues arranged in a matrix, just as in a kanban board. And so, they proudly declare that they support kanban, or even that they allow you to implement kanban in your organization.

 

As we know since the work of Marshall McLuhan, we in the electronic age tend to view the world via our tools. So we can understand why you might believe that you are using kanban if your ticketing tool tells you so. I hope you will excuse my extreme skepticism of such claims.

Marshall McLuhan (with Woodie Allen)
Fig. 4: Marshall McLuhan (with Woodie Allen)

There is a fundamental difference between the ma­nage­ment of flow that most ticketing tools support and the kanban method. Tic­ket­ing tools generally are based on a push method of managing the flow of work. Kanban, on the other hand, implements a pull method of managing flow. The easiest way to illustrate the dif­fe­rence is to contrast the older business model for American automobile manu­fac­turers with the business model of Toyota, when using the Toyota Production System.

In the older American model, the basic concept was to first build the cars and then figure out how to sell them. Since predicting how many cars will be sold is  a very tricky business, there was often a big mismatch, resulting in lost opportunities, capital tied up in inventory and huge a­mounts of waste. This is a push model. Work is triggered by the plans of the managers.

Fig. 5: In the push model, the direction of control and the direction of flow are both upstream to downstream

In the pull model, work is triggered by the needs of the customers. A customer places an order; the order is fulfilled from stock. The size of the stock is strictly limited so as not to tie up capital in a risky way. But, since a slot is opened for more stock, another automobile is ma­nu­fac­­tured and sent to stock. And this triggers, in turn, the resupply of the raw materials needed to build a new automobile. In other words, each step in the production process is triggered by downstream events. In the push model each step is trig­gered by upstream events.

direction of control pull
Fig. 6: In the pull model, the direction of flow control is from downstream to upstream
fish on a bicycle
Fig. 7: Fish on a bicycle
The pull model is truly at the heart of kanban as a flow ma­nage­ment method. Using a tool based on a push model, but with a matrix view of the state of work, has as little to do with kanban as a fish has to do with a bicycle.

So, is Kanban a visual management method?

Kanban is a method for managing the flow of any work. At the heart of the method is the pull model, whereby the flow of work is controlled in a downstream to up­stream direction. This results in a just-in-time ap­proach to making the inputs available to each phase of a value stream. The word “kanban” in Japanese (看板) does indeed mean something like “sign post”. The kanban method does indeed use visual signals to trigger the resupply of input materials and the execution of tasks, at least in certain cases. But the visual form of that signaling will vary tremendously, according to the nature of the work. In highly automated ma­nu­fac­turing, the signs controlling flow, being data in computer networks, are not visible at all to humans. In processes operated by humans, kanban may make use of physical cards as visual control signals. In knowledge work, the value stream is abstracted as a kanban board and the kanban cards are manipulated on that board, rather than with the materials being managed.  That board and its cards may be abstracted once again, be­com­ing data managed by software and displayed on video screens. Thus, while visualization may play an important role in many cases for apprehending the state of work, vi­su­a­li­zation is, at best, a practice that enables the core of flow management. It is not the core itself.

Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International LicenseThe article Is Kanban a Visual Management Method? by Robert S. Falkowitz, including all its contents, is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.

Bibliography

[a]  Ohno, Taichi, Toyota Production System: Beyond Large-Scale Production, Productivity Press 1988.

[b]   Anderson, David J., KANBAN. Successful Evolutionary Change for Your Technology Business. Blue Hole Press. 2010.

Notes
1 “Kanban is a visual system for managing work“; “Kanban is a visual system for managing work as it moves through a process“; “Personal Kanban is a visual project management system“; etc. etc.
2 I don’t mean to say that card boards do not exist anywhere at Toyota. I mean that when the shop floor was operated manually, the workers manipulated kanban cards without the use of card boards.
Credits

Unless otherwise indicated here, the diagrams are the work of the author.

Fig. 3: By Karen Abeyasekere, U.S. Air Force – This Image was released by the United States Air Force with the ID 080527-F-0000A-001[1], Public Domain, https://commons.wikimedia.org/w/index.php?curid=74965372

Fig. 4: From the film Annie Hall.

Fig. 7: The “fish on a bicycle” image is downloaded from https://www.fishonabike.com/ © Adam Sobot

Summary
Is Kanban really a Visual Management Method?
Article Name
Is Kanban really a Visual Management Method?
Description
Kanban is very frequently described as "a visual management method for projects". But is this really true? I believe it misses the core of understanding kanban and creates many misconceptions.
Author
Robert S. Falkowitz
Publisher Name
Concentric Circle Consulting
Publisher Logo
Concentric Circle Consulting

Filed Under: Kanban Tagged With: just in time, kanban board, kanban card, kanban maturity, knowledge work, marey chart, Marshall McLuhan, project management method, pull method, push method, ticketing tools, Toyota Production System, visualization, work flow

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

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

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

Tag Cloud

incident management tools change management statistical control chart kanban training waste Incident Management kanban board automation agile urgency cause knowledge work process definition context switching risk histogram manifesto for software development priority process metrics value change control lean flow efficiency value stream leadership bias incident resource liquidity adaptive case management rigidity kanban ITIL service management tools impact knowledge management flow manifesto problem lead time service manager
  • 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}