Category Archives: Data

Don’t Expect Short Quotes to Tell the Whole Story

When people try to use a short quote as an accurate encapsulation of a management concept they will often be disappointed.

It is obvious that Dr. Deming believed that organizations failed to use data effectively to improve needed to change and use data effectively in order to thrive over the long term. He believed that greatly increasing the use of data in decision making would be useful. He also believe there were specific problems with how data was used, when it is was used. Failing to understand variation leads to misinterpreting what conclusions can appropriately be drawn from data.

Using data is extremely useful in improving performance. But as Deming quoted Lloyd Nelson as saying “the most important figures that one needs for management are unknown or unknowable.”

I believe Dr. Deming would have said something like “In God we trust, all others bring data” (I haven’t been able to find a source verifying he did say it). Others don’t believe he would referencing the Lloyd Nelson quote and all Deming’s other work showing that Dr. Deming’s opinion that data isn’t all that matters. I believe they are correct that Dr. Deming wouldn’t mean for the quote to be taken literally as a summation of everything he ever said. That doesn’t mean he wouldn’t use a funny line that emphasized an important message – we need to stop relying so much on unsubstantiated opinion and instead back up opinion with data (including experiments).

Quotes can help crystallize a concept and drive home a point. They are very rarely a decent way to pass on the whole of what the author meant, this is why context is so important. But, most often quotes are shared without context and that of course, leads to misunderstandings.

image of quote - "It is wrong to suppose that if you can’t measure it, you can’t manage it – a costly myth."

A funny example of this is the Deming quote that you often see: “if you can’t measure it, you can’t manage it.” Deming did actually say that. But without the context you get 100% the wrong understanding of what he said. Deming’s full statement is “It is wrong to suppose that if you can’t measure it, you can’t manage it – a costly myth.” Now normally the much more context is required to truly understand the author’s point. But this is a funny example of how a quote can be even be accurate when passed on to you and yet completely misleading because it is taken out of context.

Continue reading

The Importance of Critical Thinking and Challenging Assumptions

There are many factors that are important to effectively practice the management improvement ideas I have discussed in this blog for over a decade. One of the most important is a culture that encourages critical thinking as well as challenging claims, decisions and assumptions.

I discussed this idea some in: Customers Are Often Irrational. There is a difference between saying people wish to have their desires met and people act in the manner to maximize the benefits they wish to receive.

It is important to study customer’s choice and learn from them. But being deceived by what their choice mean is easier than is usually appreciated. Often the decision made is contrary to the ideal choice based on their beliefs. It is often poor decision making not an indication that really they want a different result than they express (as revealed versus stated preference can show). People that ignore the evidence behind climate change and condemn coastal areas to severe consequences don’t necessarily prefer the consequences that their decision leads to. It may well be that decision to ignore the evidence is not based on a desire to suffer long term consequences in order to get short term benefits. It may well be just an inability to evaluate evidence in an effective way (fear of challenging ourselves to learn about matters we find difficult often provides a strong incentive to avoid doing so).

Knowing the difference between choosing short term benefits over long term consequences and a failure to comprehend the long term consequences is important. Just as in this example, many business decisions have at the root a desire to pretend we can ignore the consequences of our decisions and a desire to accept falsehoods that let us avoid trying to cope with the difficult problems.

photo of me with a blackboard in my father's office

Photo of me and my artwork in my father’s office by Bill Hunter

It is important to clearly articulate the details of the decision making process. We need to note the actual criticism (faulty logic, incorrect beliefs/assumptions…) that results in what some feel is a poor conclusion. But we seem to find shy away from questioning faulty claims (beliefs that are factually incorrect – that vaccines don’t save people from harm, for example) or lack of evidence (no data) or poor reasoning (drawing unsupported conclusions from a well defined set of facts).

Critical thinking is important to applying management improvement methods effectively. It is important to know when decisions are based on evidence and when decisions are not based on evidence. It can be fine to base some decisions on principles that are not subject to rational criticism. But it is important to understand the thought process that is taken to make each decision. If we are not clear on the basis (evidence or opinion regardless of evidence) we cannot be as effective in targeting our efforts to evaluate the results and continually improve the processes in our organizations.

Describing the decision as “irrational” is so imprecise that it isn’t easy to evaluate how much merit the criticism has. If specific facts are called into question or logical fallacies within the decision making process are explained it is much more effective at providing specific items to explore to evaluate whether the criticism has merit.

When specific criticisms are made clear then those supporting such a decision can respond to the specific issues raised. And in cases where the merits of one course of action cannot be agreed to then such critical thought can often be used to create measures to be used to evaluate the effectiveness of the decision based on the results. Far too often the results are not examined to determine if they actually achieved what was intended. And even less often is care taken to examine the unintended consequences of the actions that were taken.

Continue reading

Technological Innovation and Management

Technological innovation brings great opportunity for improving results and our quality of life. But transforming potential benefits into real results comes with many challenges.

ASQ has asked their Influential Voices to explore the idea of the fourth industrial revolution: “this new era is founded on the practical use of technological innovations like artificial intelligence, big data, robotics, and the Internet of Things (IoT).”

For many years GMs huge investment in robotics in the 1980s ($billions) has been an example of how pinning hopes on technology often doesn’t produce the desired results. I think that a capable management system is needed to make technological innovation as successful as it needs to be.

In this decade we are finally reaching the point where robotics is really making incredible strides. Robotics has provided huge benefits for decades, when used appropriately, but the ease of use and benefits from robotics have greatly increased recently.

I think robotics is going to be an incredibly powerful source of benefits to society in the next 20 years. Amazon is very well placed to profit in this area. Several other companies (Toyota, Boston Dynamics*, Honda, SoftBank…) are likely to join them (though which will be the biggest winners and which will stumble is not obvious)

Cliff Palace historical ruins

Photo by John Hunter of Cliff Palace (built in the 1190s), Mesa Verde National Park.

I am less confident in the Internet of Things. It seems to me that much of the IoT effort currently is flailing around in ways similar to GMs approach to robotics in the 1980s and 1990s. There is huge potential for IoT but the architecture of those solutions and the impact of that architecture on security (and fragile software that creates many more problems than it solves) is not being approached wisely in my opinion. IoT efforts should focus on delivering robust solutions in the areas where there is a clear benefit to adopting IoT solutions. And that needs to be done with an understanding of security and the lifecycle of the devices and businesses.

I think it will be much wiser to have an internet hub in the business or home that has all IoT traffic route through it in a very clear and visible way. Users need clear ways to know what the IoT is trying to do and to have control to determine what is and what is not sent out from their system. Having devices that share information in a non-transparent way is not wise. This is especially when those devices have cameras or microphones.

Continue reading

All Data is Wrong, Some is Useful

From my first blog post on this blog – Dangers of Forgetting the Proxy Nature of Data

we often fail to explore whether changes in the numbers (which we call results) are representative of the “true results” of the system or if the data is misleading.

Data is meant to provide us insight into a more complex reality. We need to understand the limitations when we look at “results” and understand data isn’t really the results but a representation we hope is close to reality so we can successfully use the data to make decisions.

But we need to apply thought to how we use data. Lab results are not the same are what happens in the field. It is cheaper and faster to examine results in a lab. But relying on lab results involves risk. That doesn’t mean relying on lab results is bad, we have to balance the costs and benefits of getting more accurate data.

But relying on lab results and not understanding the risk is dangerous. This is the same idea of going to the gemba to get an accurate understanding instead of relying on your ability to imagine reality based upon some data and ideas of what it is probably like.

photo of a Modified Yellow VW Beetle

VW Beetle (in Bangkok, Thailand) has some sort of modification along the back bumper but I don’t know what it is meant to do. Any ideas? More of my photos from Bangkok.

Volkswagen Drops 23% After Admitting Diesel Emissions Cheat

Volkswagen AG lost almost a quarter of its market value after it admitted to cheating on U.S. air pollution tests for years

During normal driving, the cars with the software — known as a “defeat device” — would pollute 10 times to 40 times the legal limits, the EPA estimated. The discrepancy emerged after the International Council on Clean Transportation commissioned real-world emissions tests of diesel vehicles including a Jetta and Passat, then compared them to lab results.

Obviously VW was managing-to-test-result instead of real world value. It seems they were doing so intentionally to provide misleading data. Obviously one of the risks with lab test results (medical trials etc.) is that those with an interest in showing better results could manipulate the data and lab procedures (or systems) to have the data show their product in the most favorable light.

Continue reading

Transforming a Management System – A Case Study From the Madison Wisconsin Police Department

This post in an excerpt from The Quality Leadership Workbook for Police by Chief David Couper and Captain Sabine Lobitz (buy via Amazon).

cover image of the New Quality Leadership Workbook for Police

The New Quality Leadership Workbook for Police

Transformational Steps
A Case Study Madison, Wisconsin (1981-1993)

Step 1: Educate and inform everyone in the organization about the vision, the goals, and Quality Leadership. This step must be passionately led by the top leader.

  • Begin discussion with top management team and train them.
  • Discuss and ask employees; get feedback from them.
  • Share feedback with the chief and his management team.
  • Get buy-in from top department managers.
  • Survey external customers—citizens; those who live and work in the community.
  • Create an employee’s advisory council; ask, listen, inform, and keep them up to date on what’s going on.
  • The chief keeps on message; tells, sells, and persuades, newsletters, meetings and all available media.

Step 2: Prepare for the transformation. Before police services to the community can be improved, it is essential to prepare the inside first — to cast a bold vision and to have leaders that would “walk the talk.”

  • Appoint a top-level, full-time coordinator to train, coach, and assist in the transformation.
  • Form another employee council to work through problems and barriers encountered during implementation of the transformation and Quality Leadership.
  • Require anyone who seeks to be a leader to have the knowledge and ability to practice Quality Leadership.

Step 3: Teach Quality Leadership. This begins at the top with the chief and the chief’s management team.

  • Train all organizational leaders in Quality Leadership.
  • Train all employees as to what Quality Leadership is, why the transformation is necessary, and what it means for them.

Step 4: Start practicing Quality Leadership. If top managers within the organization are not authentically practicing Quality Leadership neither will anyone else.

Continue reading

Out of Touch Executives Damage Companies: Go to the Gemba

When your customer service organization is universally recognized as horrible adding sales requirements to customer service representatives jobs is a really bad practice. Sadly it isn’t at all surprising to learn of management doing just that at our largest companies. Within a system where cash and corruption buys freedom from market forces (see below for more details) such practices can continue.

Such customer hostile practices shouldn’t continue. They shouldn’t be allowed to continue. And even though the company’s cash has bought politically corrupt parties to allow such a system to survive it isn’t even in the selfish interest of the business. They could use the cover provided by bought-and-paid-for-politicians-and-parties to maintain monopolistic pricing (which is wrong ethically and economically but could be seen as in the self interest of a business). But still provide good service (even while you take monopolistic profits allowed with corrupt, though legal, cash payments).

Of course, Adam Smith knew the likely path to corruption of markets made up of people; and he specifically cautioned that a capitalist economic system has to prevent powerful entities efforts to distort markets for individual gain (perfect competition = capitalism, non-competitive markets = what business want, as Adam Smith well knew, but this is precisely not capitalism). Sadly few people taking about the free-market or capitalism understand that their support of cronyist policies are not capitalist (I suppose some people mouthing those words are just preaching false ideas to people known to be idiots, but really most don’t seem to understand capitalism).

Anyway, this class of protected businesses supported by a corrupt political and government (regulators in government) sector is a significant part of the system that allows the customer hostility of those politically connected large businesses to get away with a business model based on customer hostility, but wasn’t really what I meant to write about here.

Comcast executives have to know they are running a company either rated the worst company in the country or close to it year after year. They, along with several others in their industry, as well as the cell phone service providers and too-big-to-fail-banks routinely are the leaders of companies most reviled by customers. Airlines are also up their for treating customer horribly but they are a bit different than the others (political corruption is much less of the reason for their ability to abuse customers for decades than is for the others listed above).

Leaked Comcast employee metrics show what we figured: Sell or perish [Updated]
Training materials explicitly require a “sell” phase, even in support calls.

The company’s choice to transform what is traditionally a non-revenue-generating area—customer service—into a revenue-generating one is playing out with almost hilariously Kafkaesque consequences. It is the nature of large corporations like Comcast to have dozens of layers of management through which leadership instructions and directives are filtered. The bigger the company, the more likely that members of senior leadership (like Tom Karinshak) typically make broad policy and leave specific implementations to lower levels.

Here, what was likely praised in the boardroom as an “innovative” strategy to raise revenue is instead doing much to alienate customers and employees alike. Karinshak’s assurances that he doesn’t want employees to feel pressured to sell in spite of hard evidence that Comcast demands just that are hard to square with the content of the document.

So what is going on here? Most people can easily see this is likely a horrible practice. It is a practice that a well run company theoretically could pull off without harming customers too much. But for a company like Comcast to do this it is obviously going to be horrible for customers (same for all those too-big to fail banks, cell phone service providers and other ISPs and cable TV providers).

Lets just pretend Comcast’s current leadership executives were all replaced with readers of the Curious Cat Management Improvement blog. And lets say that for now you are suppose to focus on improving the policies in place (while thinking about policy changes for later but not making them yet).

Continue reading

George Box Webcast on Statistical Design in Quality Improvement

George Box lecture on Statistical Design in Quality Improvement at the Second International Tampere Conference in Statistics, University of Tampere, Finland (1987).

Early on he shows a graph showing the problems with American cars steady over a 10 years period. Then he overlays the results for Japanese cars which show a steady and significant decline of the same period.

Those who didn’t get to see presentations before power point also get a chance to see old school, hand drawn, overhead slides.

He discusses how to improve the pace of improvement. To start with informative events (events we can learn from) have to be brought to the attention of informed observers. Otherwise only when those events happen to catch the attention of the right observer will we capture knowledge we can use to improve. This results in slow improvement.

A control chart is an example of highlighting that something worth studying happened. The chart will indicate when to pay attention. And we can then improve the pace of improvement.

Next we want to encourage directed experimentation. We intentionally induce informative events and pay close attention while doing so in order to learn.

Every process generates information that can be used to improve it.

He emphasis the point that this isn’t about only manufacturing but it true of any process (drafting, invoicing, computer service, checking into a hospital, booking an airline ticket etc.).

He then discussed an example from a class my father taught and where the students all when to a TV plant outside Chicago to visit. The plant had been run by Motorola. It was sold to a Japanese company that found there was a 146% defect rate (which meant most TVs were taken off the line to be fixed at least once and many twice) – this is just the defect rate before then even get off the line. After 5 years the same plant, with the same American workers but a Japanese management system had reduced the defect rate to 2%. Everyone, including managers, were from the USA they were just using quality improvement methods. We may forget now, but one of the many objections managers gave for why quality improvement wouldn’t work in their company was due to their bad workers (it might work in Japan but not here).

He references how Deming’s 14 points will get management to allow quality improvement to be done by the workforce. Because without management support quality improvement processes can’t be used.

With experimentation we are looking to find clues for what to experiment with next. Experimentation is an iterative process. This is very much the mindset of fast iteration and minimal viable product (say minimal viable experimentation as voiced in 1987).

There is great value in creating iterative processes with fast feedback to those attempting to design and improve. Box and Deming (with rapid turns of the PDSA cycle) and others promoted this 20, 30 and 40 years ago and now we get the same ideas tweaked for startups. The lean startup stuff is as closely related to Box’s ideas of experimentation as an iterative process as it is to anything else.

Related: Ishikawa’s seven quality control tools

He also provided a bit of history that I was not aware of saying the first application of orthogonal arrays (fractional factorial designs) in industry was by Tippett in 1933. And he then mentioned work by Finney in 1945, Plackett and Burman in 1946 and Rao in 1947.

Taking Risks Based on Evidence

My opinion has long been that football teams are too scared to take an action that is smart but opens the coach to criticism. So instead of attempting to make it on 4th down (if you don’t understand American football, just skip this post) they punt because that is the decision that is accepted as reasonable.

So instead of doing what is wise they do what avoids criticism. Fear drives them to take the less advantageous action. Now I have never looked hard at the numbers, but my impression is that it is well worth the risk to go for it on 4th down often. In a quick search I don’t see a paper by a Harvard professor (this article refers to it also – Fourth down: To punt or to go?) on going for it on 4th down but I found on by a University of California, Berkeley economist (David Romer wrote called “Do Firms Maximize? Evidence from Professional Football.”).

On the 1,604 fourth downs in the sample for which the analysis implies that teams are on average better off kicking, they went for it only nine times. But on the 1,068 fourth downs for which the analysis implies that teams are on average better off going for it, they kicked 959 times.

My guess is that the advantages to going for it on 4th down are greater for high school than college which is greater than the advantage for the pros (but I may be wrong). My guess is this difference is greater the more yardage is needed. Basically my feeling is the variation in high school is very high in high school and decreases with greater skill, experience and preparation. Also the kicking ability (punting and field goals) impacts the choices of going for it on 4th down and that dramatically increases in college. So if I am correct, I think pro coaches should be more aggressive on 4th down, but likely less aggressive than high school coaches should be.

But in any event the data should be explored and strategies should be tested.

Continue reading

Stu Hunter Discussing Bill Hunter, Statistics for Experimenters and EVOP

In this clip, Stu Hunter talks about Bill Hunter (my father, and no relation to Stu Hunter), Statistics for Experimenters and EVolutionary OPerations (EVOP).

Stu mentions Bill Hunter’s work with the City of Madison, which started with the First Street Garage (Out of the Crisis included a short write up on this effort by Dad, which, I believe, was the first application of Deming’s ideas in the public sector).

There was also a great deal of work done with the Police department, as the police chief, David Couper, saw great value in Deming’s ideas. The Police department did some great work and David’s blog shares wonderful ideas on improving policing. I don’t think Dad was that directly involved in what happened there, but it is one of the nice benefits of seeding new ideas: as they take root and grow wonderful things happen without any effort on your part.

As to why Dad got involved with the city, he returned from a summer teaching design of experiments and quality improvement methods in China (this is just before China was really open, a few outsiders were let in to teach). We had also lived overseas several other times, always returning to Madison. He decided he wanted to contribute to the city he loved, Madison, and so he talked to the Mayor about helping improve performance of the city.

The mayor listened and they started with a pilot project which Dad work on with Peter Scholtes. Dad talked to Peter, who he had know for years, and who worked for the city, before talking to the mayor. Read more about the efforts in Madison via the links at the end of this post.

Continue reading

The Art of Discovery

Quality and The Art of Discovery by Professor George Box (1990):

Quotes by George Box in the video:

“I think of statistical methods as the use of science to make sense of numbers”

“The scientific method is how we increase the rate at which we find things out.”

“I think the quality revolution is nothing more, or less, than the dramatic expansion of the of scientific problem solving using informed observation and directed experimentation to find out more about the process, the product and the customer.”

“It really amounts to this, if you know more about what it is you are doing then you can do it better and you can do it cheaper.”

“We are talking about involving the whole workforce in the use of the scientific method and retraining our engineers and scientists in a more efficient way to run experiments.”

“Tapping into resources:

  1. Every operating system generates information that can be used to improve it.
  2. Everyone has creativity.
  3. Designed experiments can greatly increase the efficiency of experimentation.

An informed observer and directed experimentation are necessary for the scientific method to be applied. He notes that the control chart is used to notify an informed observer to explain what is special about the conditions when a result falls outside the control limits. When the chart indicates a special cause is likely present (something not part of the normal system) an informed observer should think about what special cause could lead to the result that was measured. And it is important this is done quickly as the ability of the knowledgable observer to determine what is special is much greater the closer in time to the result was created.

The video was posted by Wiley (with the permission of George’s family), Wiley is the publisher of George’s recent autobiography, An Accidental Statistician: The Life and Memories of George E. P. Box, and many of his other books.

Related: Two resources, largely untapped in American organizations, are potential information and employee creativityStatistics for Experimenters (book on directed experimentation by Box, Hunter and Hunter)Highlights from 2009 George Box SpeechIntroductory Videos on Using Design of Experiments to Improve Results (with Stu Hunter)

George Box

I would most likely not exist if it were not for George Box. My father took a course from George while my father was a student at Princeton. George agreed to start the Statistics Department at the University of Wisconsin – Madison, and my father followed him to Madison, to be the first PhD student. Dad graduated, and the next year was a professor there, where he and George remained for the rest of their careers.

George died today, he was born in 1919. He recently completed An Accidental Statistician: The Life and Memories of George E. P. Box which is an excellent book that captures his great ability to tell stories. It is a wonderful read for anyone interested in statistics and management improvement or just great stories of an interesting life.

photo of George EP Box

George Box by Brent Nicastro.

George Box was a fantastic statistician. I am not the person to judge, but from what I have read one of the handful of most important applied statisticians of the last 100 years. His contributions are enormous. Several well know statistical methods are known by his name, including:

George was elected a member of the American Academy of Arts and Sciences in 1974 and a Fellow of the Royal Society in 1979. He also served as president of the American Statistics Association in 1978. George is also an honorary member of ASQ.

George was a very kind, caring and fun person. He was a gifted storyteller and writer. He had the ability to present ideas so they were easy to comprehend and appreciate. While his writing was great, seeing him in person added so much more. Growing up I was able to enjoy his stories often, at our house or his. The last time I was in Madison, my brother and I visited with him and again listened to his marvelous stories about Carl Pearson, Ronald Fisher and so much more. He was one those special people that made you very happy whenever you were near him.

George Box, Stuart Hunter and Bill Hunter (my father) wrote what has become a classic text for experimenters in scientific and business circles, Statistics for Experimenters. I am biased but I think this is acknowledged as one of (if not the) most important books on design of experiments.

George also wrote other classic books: Time series analysis: Forecasting and control (1979, with Gwilym Jenkins) and Bayesian inference in statistical analysis. (1973, with George C. Tiao).

George Box and Bill Hunter co-founded the Center for Quality and Productivity Improvement at the University of Wisconsin-Madison in 1984. The Center develops, advances and communicates quality improvement methods and ideas.

The Box Medal for Outstanding Contributions to Industrial Statistics recognizes development and the application of statistical methods in European business and industry in his honor.

All models are wrong but some are useful” is likely his most famous quote. More quotes By George Box

A few selected articles and reports by George Box

Continue reading

Quality Processes in Unexpected Places

This month Paul Borawski asked ASQ’s Influential Voices to explore the use of quality tools in unexpected places.

The most surprising example of this practice that I recall is the Madison, Wisconsin police department surveying those they arrested to get customer feedback. It is obvious that such “customers” are going to be biased. Still the police department was able to get actionable information by seeking the voice of the customer.

photo of a red berry and leaves

Unrelated photo from Singapore Botanical Garden by John Hunter.

Certain of the police department’s aims are not going to match well with those they arrest (most obviously those arrested wish the police department didn’t arrest them). The police department sought the voice of the customer from all those they interacted with (which included those they arrested, but also included those reporting crimes, victims, relatives of those they arrested etc.).

The aim of the police department is not to arrest people. Doing so is necessary but doing so is most similar in the management context to catching an error to remove that bad result. It is better to improve processes so bad results are avoided. How the police interact with the public can improve the process to help steer people’s actions away from those that will require arrests.

The interaction police officers have with the public is a critical gemba for meeting the police department’s aim. Reducing crime and encouraging a peaceful society is aided by knowing the conditions of that gemba and knowing how attempts to improve are being felt at the gemba.

All customer feedback includes bias and personal preferences and potentially desires that are contrary to the aims for the organization (wanting services for free, for example). Understanding this and how important understanding customer/user feedback on the gemba is, it really shouldn’t be surprising that the police would want that data. But I think it may well be that process thinking, evidence based management and such ideas are still not widely practiced as so the Madison police department’s actions are still surprising to many.

Quality Leadership: The First Step Towards Quality Policing by David Couper and Sabine Lobitz

Our business is policing, our customers are the citizens within our jurisdictions, and our product is police service (everything from crime fighting and conflict management to safety and prevention programs.)

If we are to cure this we must start to pay attention to the new ideas and trends in the workplace mentioned earlier that are helping America’s businesses; a commitment to people, how people are treated — employees as well as citizens, the development of a people-oriented workplace, and leadership can and does make a difference.

If we change the way in which we lead the men and women in our police organizations, we can achieve quality in policing. However, wanting to change and changing are worlds apart. The road to change is littered by good intentions and short-term efforts.

This article, from 1987, illustrates the respect for people principle was alive and being practiced 25 years ago; most organizations need to do a great deal more work on applying practices that show respect for people.

Related: Quality Improvement and Government: Ten Hard Lessons From the Madison Experience by David C. Couper, Chief of Police, City of Madison, Wisconsin – SWAT Raids, Failure to Apply System Thinking in Law EnforcementMeasuring What Matters: Developing Measures of What the Police DoThe Public Sector and W. Edwards DemingDoing More with Less in the Public Sector – A Progress Report from Madison, Wisconsin

The Market Discounts Proven Company Leadership Far Too Quickly

Developing a strong executive leadership culture is not a short term effort. It isn’t based on one person. It almost never deteriorates quickly. Yet markets continually overact to minor blips on the long term success of companies. I think this is mainly due to a failure to appreciate systems and a failure to appreciate variation along with plenty of other contributing factors.

The market’s weakness does provide investment opportunities. Though taking advantages of them is much more difficult than spotting a general weakness. While excellent management almost never becomes pitiful overnight (regardless of how often talking heads would have you believe) business can change very quickly due to rapidly changing market conditions. Avoiding the purchases when the underlying business has sustained a significant blow that excellent management will deal with but which will reduce the value of the enterprise going forward is key to taking advantage of the market’s silly overreaction to bad news (or even calling things “bad news” that are not actually bad just not as awesome as some were hoping for).

My positive opinion of Toyota’s management has continued for a long time. A few years ago an amazing number of people were all excited about the “decline of Toyota” and wrote about how Toyota’s ways had to change. I wrote at the time was this is needless hysteria and if Toyota just focused a bit more on applying the Toyota’s management methods they would be in great shape. The problems were due to Toyota’s mistakes in practicing the Toyota Production System not in a weakness of those practices.

Looking at a chart of Toyota’s stock price from 2007 to today it peaks at about $137 in January 2007 and bottoms at $58 in early 2009 and now is at $96. Toyota’s stock price has been priced richly due to respect for management and consistently strong cash flow. As it fell below $75 there you no longer had to pay a premium for excellent management, but that management was still there. I like getting bargains when I buy stocks. One of the things I have learned I am too focused on bargains and I should be more willing to accept less of a bargain to get great management systems – so I have adjusted, and have improved my results. When I can get a great bargain and great management it is wonderful, though sadly a rare occurrence. Toyota’s price now seems reasonable, but not a huge bargain.

The market continually gets overly excited by either actual problems or perceived problems. I wrote about this happening with Netflix 2 years ago. Netflix made some mistakes and faced some tough business issues. The evidence of sound, sensible, effective management vastly outweighed the evidence for management failure – yet there were hundreds of articles about the pitiful failure of Netflix management.

Continue reading

Leanpub Podcast on My Book – Management Matters: Building Enterprise Capability

image of the cover of Managmenet Matters by John Hunter

Management Matters by John Hunter

I recently was interviewed for a podcast by Len Epp with Leanpub: Leanpub Podcast Interview #9: John Hunter. I hope you enjoy the podcast (download the mp3 of the podcast).

In the podcast we cover quite a bit of ground quickly, so the details are limited (transcript of the interview). These links provide more details on items I mention in the podcast. They are listed below in the same order as they are raised in the podcast:

The last 15 minutes of the podcast I talk about some details of working with Leanpub; I used Leanpub to publish Management Matters. I recommend Leanpub for other authors. They don’t just have lean in their name, they actual apply lean principles (focusing on the value chain, eliminating complexity, customer focus, etc.) to operating Leanpub. It is extremely easy to get started and publish your book.

Leanpub also offers an excellent royalty plan: authors take home 90% of the revenue minus 50 cents per book. They publish without “digital rights management” crippling purchasers use of the books. Buyers have access to pdf, kindle (mobi) and epub (iPad, nook) format books and get access to all updates to the book. All purchases include a 45 day full money back guaranty.

Related: Business 901 Podcast with John Hunter: Deming’s Management Ideas TodayInterviews for Management Matters: Building Enterprise Capability

Indirect Improvement

Often the improvements that have the largest impact are focused on improving the effectiveness of thought and decision making. Improving the critical thinking in an organization has huge benefits over the long term.

My strategy along the lines of improving critical thinking is not to make that the focus of some new effort. Instead that ability to reason more effectively will be an outcome of things such as: PDSA projects (where people learn that theories must be tested, “solutions” often fail if you bother to look at the results…), understanding variation (using control charts, reading a bit of material on: variation, using data effectively, correlation isn’t causation etc.), using evidenced based management (don’t make decision based on the authority of the person speaking but on the merit that are spoken).

These things often take time. And they support each other. As people start to understand variation the silly discussion of what special causes created the result that is within the expected outcomes for the existing process are eliminated. As people learn what conclusions can, and can’t, be drawn from data the discussions change. The improvements from the process of making decisions is huge.

As people develop a culture of evidence based management if HiPPOs try to push through decision based on authority (based on Highest Paid Person’s Opinion) without supporting evidence those attempts are seen for what they are. This presents a choice where the organization either discourages those starting to practice evidence based decision making (reverting to old school authority based decision making) or the culture strengthens that practice and HiPPO decision making decreases.

Building the critical thinking practices in the organization creates an environment that supports the principles and practices of management improvement. The way to build those critical thinking skills is through the use of quality tools and practices with reminders on principles as projects are being done (so until understanding variation is universal, continually pointing out that general principle with the specific data in the current project).

The gains made through the direct application of the tools and practices are wonderful. But the indirect benefit of the improvement in critical thinking is larger.

Related: Dan’t Can’t LieGrowing the Application of Management Improvement Ideas in Your OrganizationBuild Systems That Allow Quick Action – Don’t Just Try and Run FasterBad Decisions Flow From Failing to Understand Data and Failing to Measure Results of Changes

Special Cause Signal Isn’t Proof A Special Cause Exists

One of my pet peeves is when people say that a point outside the control limits is a special cause. It is not. It is an indication that it likely a special cause exists, and that special cause thinking is the correct strategy to use to seek improvement. But that doesn’t mean there definitely was a special cause – it could be a false signal.

This post relies on an understand of control charts and common and special causes (review these links if you need some additional context).

Similarly, a result that doesn’t signal a special cause (inside the control limits without raising some other flag, say a run of continually increasing points) does not mean a special cause is not present.

The reason control charts are useful is to help us maximize our effectiveness. We are biased toward using special cause thinking when it is not the most effective approach. So the control chart is a good way to keep us focused on common cause thinking for improvement. It is also very useful in flagging when it is time to immediately start using special cause thinking (since timing is key to effective special cause thinking).

However, if there is result that is close to the control limit (but inside – so no special cause is indicated) and the person that works on the process everyday thinks, I noticed x (some special cause) earlier, they should not just ignore that. It very well could be a special cause that, because of other common cause variation, resulted in a data point that didn’t quite reach the special cause signal. Where the dot happened to land (just above or just below the control limit – does not determine if a special cause existed).

The signal is just to help us systemically make the best choice of common cause or special cause thinking. The signal does not define whether a special cause (an assignable cause) exists of not. The control chart tool helps guide us to use the correct type of improvement strategy (common cause or special cause). But it is just a signaling device, it isn’t some arbiter of whether a special cause actually exists.

Continue reading

Introductory Videos on Using Design of Experiments to Improve Results

The video shows Stu Hunter discussing design of experiments in 1966. It might be a bit slow going at first but the full set of videos really does give you a quick overview of the many important aspects of design of experiments including factorial designed experiments, fractional factorial design, blocking and response surface design. It really is quite good, if you find the start too slow for you skip down to the second video and watch it.

My guess is, for those unfamiliar with even the most cursory understanding of design of experiments, the discussion may start moving faster than you can absorb the information. One of the great things about video is you can just pause and give yourself a chance to catch up or repeat a part that you didn’t quite understand. You can also take a look at articles on design of experiments.

I believe design of experiments is an extremely powerful methodology of improvement that is greatly underutilized. Six sigma is the only management improvement program that emphasizes factorial designed experiments.

Related: One factor at a time (OFAT) Versus Factorial DesignsThe purpose of Factorial Designed Experiments

Continue reading

Keys to the Effective Use of the PDSA Improvement Cycle

The PDSA improvement cycle was created by Walter Shewhart where Dr. Deming learned about it. An improvement process is now part of many management improvement methods (A3 for lean manufacturing, DMAIC for six sigma and many other modifications). They are fairly similar in many ways. The PDSA cycle (Plan, Do, Study, Act) has a few key pieces that are either absent in most others processes of greatly de-emphasized which is why I prefer it (A3 is my second favorite).

The PDSA cycle is a learning cycle based on experiments. When using the PDSA cycle prediction of the results are important. This is important for several reasons but most notably due to an understanding of the theory of knowledge. We will learn much more if we write down our prediction. Otherwise we often just think (after the fact); yeah that is pretty much what I expected (even if it wasn’t). Also we often fail to think specifically enough at the start to even have a prediction. Forcing yourself to make a prediction gets you to think more carefully up front and can help you set better experiments.

An organization using PDSA well will turn the PDSA cycle several times on any topic and do so quickly. In a 3 month period turning it 5 times might be good. Often those organizations that struggle will only turn it once (if they are lucky and even reach the study stage). The biggest reason for effective PDSA cycles taking a bit longer is wanting more data than 2 weeks provides. Still it is better to turn it several times will less data – allowing yourself to learn and adjust than taking one long turn.

The plan stage may well take 80% (or even more) of the effort on the first turn of the PDSA cycle in a new series. The Do stage may well take 80% of of the time – it usually doesn’t take much effort (to just collect a bit of extra data) but it may take time for that data to be ready to collect. In the 2nd, 3rd… turns of the PDSA cycle the Plan stage often takes very little time. Basically you are just adjusting a bit from the first time and then moving forward to gather more data. Occasionally you may learn you missed some very important ideas up front; then the plan stage may again take some time (normally if you radically change your plans).

Remember to think of Do as doing-the-experiment. If you are “doing” a bunch of work (not running an experiment and collecting data) that probably isn’t “do” in the PDSA sense.

Study should not take much time. The plan should have already have laid out what data is important and an expectation of what results will be achieved and provide a good idea on next steps. Only if you are surprised (or in the not very common case that you really have no idea what should come next until you experiment) will the study phase take long.

Continue reading

Agile Story Point Estimation

In agile software development tasks are documented as user stories. Then the level of effort for those stores can be estimated by assigning each story points. The velocity that can be produced in a period (called a sprint, for us 2 weeks) can be estimated. Thus you can predict what can be delivered in the next sprint (which can help business managers make priority decisions).

I have found estimation to be worthwhile. In doing so, we accept there is a great amount of variation but points give a hint to scale. They can help prioritize (if you have 5 things you want but 1 is much harder you may well drop that to the bottom). I have always accepted a great amount of variation in the velocity, worry about the variation I don’t find worthwhile. I do think trying to act as though the velocity is precise can lead to problems. At the same time having a measure of velocity, even accepting understanding variation was present, was useful.

Over time reducing variation (probably largely through better estimation and perhaps a few better tools, reduced technical debt, better documentation, testing…) is helpful and laudable. We made improvement but still lots of variation existed. The biggest help in reducing the measured velocity was breaking down large stories to more manageable sizes. The challenge of estimating user stories, I suspect, has some fairly high variation (even with good system improvements that can help reduce variation).

Large stories just can hide huge variation in what is really required once getting into implementing it.

The way we did estimation (discussing in a sprint planning meeting) did take some time (but not a huge amount). It was agreed by those involved that the time spent was worthwhile. Sometimes we did slip and spend too much time on this, that was an area we had to pay attention to. The discussions were educational and helped provide guidance on how to approach the story. The value of discussions around estimations was probably the biggest surprise I have had in implementing any agile ideas. The value of those discussion was much higher than I imagined (I basically anticipated them just as non-value added time to get the result of an estimate, but they were a source of learning and consensus building).

Related: Assigning Story Points to Bug FixesMistake Proofing the Deployment of Software CodeChecklists in Software Development

These thoughts were prompted by: Story Points Considered Harmful – Or why the future of estimation is really in our past…

Continue reading

Trust But Verify

The following are my comments, which were sparked by question “Trust, but verify. Is this a good example of Profound Knowledge in action?” on the Linked In Deming Institute group.

Trust but verify makes sense to me. I think of verify as process measures to verify the process is producing as it should. By verifying you know when the process is failing and when to look for special causes (when using control chart thinking with an understanding of variation). There are many ways to verify that would be bad. But the idea of trust (respect for people) is not just a feel-good, “be nice to everyone and good things happen”, in Deming’s System of Profound Knowledge.

I see the PDSA improvement cycle as another example of a trust-but-verify idea. You trust the people at the gemba to do the improvement. They predict what will happen. But they verify what does actually happen before they run off standardizing and implementing. I think many of us have seen what happens when the idea of letting those who do the work, improve the process, is adopted without a sensible support system (PDSA, training, systems thinking…). It may actually be better than what was in place, but it isn’t consistent with Deming’s management system to just trust the people without providing methods to improve (and education to help people be most effective). Systems must be in place to provide the best opportunity to succeed. Trusting the people that do the work, is part of it.

I understand there are ways to verify that would be destructive. But I do believe you need process measures to verify systems are working. Just trusting people to do the right thing isn’t wise.

A checklist is another way of “not-trusting.” I think checklists are great. It isn’t that I don’t trust people to try and do the right thing. I just don’t trust people alone, when systems can be designed with verification that improves performance. I hear people complaign that checklists “don’t respect my expertise” or have the attitude that they are “insulting to me as a professional” – you should just trust me.

Sorry, driving out fear (and building trust – one of Deming’s 14 points) is not about catering to every person’s desire. For Deming’s System of Profound Knowledge: respect for people is part of a system that requires understand variation and systems thinking and an understanding of psychology and theory of knowledge. Checklists (and other forms of verification) are not an indication of a lack of trust. They are a a form of process measure (in a way) that has been proven to improve results.

Continue reading