Posts about John Hunter

Why Use Lean if So Many Fail To Do So Effectively

If less than 1% of companies are successful with Lean, why are we doing it?

Lots of us are not. I would say the efforts I see “fail” are because they don’t do it. They have something they call TQM, six sigma, lean management or whatever and try out 10-30% of it in some half-measures, with big doses of Dilbert’s pointy haired boss methods and then don’t get great results. Wow.

The biggest complaint (with some merit) I see is why is lean/Deming/six sigma… so hard to actually do. If companies constantly fail to do it at all (even when they use the name) isn’t that an issue. Isn’t that a weakness of the “solution.” My answer is: yes. The caveat is, until someone comes up with the management system that both gets the results using Deming’s management ideas can, and is super easy for organizations to actually fully adopt (and have the great success that doing so provides) I know of nothing better than trying to do these things.

Certainly I believe you are much better off attempting to use Deming, lean or six sigma than listen to someone that tells you they have management instant pudding that will give you great results with no effort.

My belief is that a partial success rate is much higher than 1%. While many organization never go beyond slapping a few good tools on a outdated management system those few tools actually have good results. Maybe 50% of the implementations are so lame they have almost no positive results (not even getting improvement worth the time and effort). They could be seen as “failures,” to me. Those that actually have a right to say they are practicing “lean” I would say is a pretty small number but still above 1%?

There is also an advantage to this stuff being hard to do. You really don’t have to invent anything new. If you just have persistence and keep continually improving along the path applying ideas proven over decades from Deming, Ohno, McGregor, Christensen, Drucker, Scholtes, Womack, Roger Hoerl (six sigma)… you have a great advantage over all those organizations that ignored the ideas or made a bit of effort and then gave up.

Related: Engage in Improving the Management SystemRethinking or Moving Beyond Deming Often Just Means Applying More of What Dr. Deming Actually SaidManagement Advice FailuresManagement Improvement FlavorsHas Six Sigma Been a Success?

Management Improvement Blog Carnival #157

The Curious Cat management blog carnival is published 3 times a month with hand picked recent management blog posts. I also collect management improvement articles for the Curious Cat Management Articles site; you can subscribe via RSS for new article additions.

Pull Consulting: Immediate Management Consulting As You Need It

I think the potential for consulting as you need it is great. I actually was looking into creating an application to support the ability to provide this service with someone else; but we just had too many other things going on. I have now made myself available for consulting you pull as you need it through MinuteBox. You can get consulting when you need it for as little time as you need.

So if you are trying to apply the ideas I discuss on this blog and run into issues you would like to get some help with connect with me and you can get some immediate coaching on whatever you are struggling with. I am offering a special rate of $1.99 a minute, for now. The graphic on the right of this post (any post on this blog, actually) will show if I am available right now (as does johnhunter.com). If so, you can connect and get started. If not, you can leave a message and we can arrange a time.

I am featured on MinuteBox with this cool graphic, isn’t it nice :-)

home page of MInute Box with John Hunter graphic

John Hunter feature on Minute Box homepage

One advantage of this model is that those of you following this blog have a good idea of what topics you would like to delve into more deeply with me. If you have any questions on a particular topic you would like answered today or arranging coaching on specific topics over a period of time or help planning a project or someone to bounce your ideas off give this consulting as you need it model a try.

For those of you management consultants reading this blog (I know there are many) you can create your own Minute Box account easily and provide this service also. And even if you are not a consultant if you have advice worth sharing (and I know there are many of you also) you can also set up an account.

Related: John Hunter’s professional life timelineJohn Hunter onlineJohn Hunter LinkedIn profileTop Leadership blogsTop Management and Leadership blogs – Top Management blog

ASQ Influential Voices

I am joining the ASQ Influential Voices project for 2012. The effort started last year when ASQ chose a few people to participate in a group effort to share their thoughts on various topics in quality improvement. I have been asked to join for 2012, along with a couple lean bloggers (Mark Graban and Tim McMahon) and others. Each month the ASQ executive director will post on a topic and I, and the other influential voices participants, will share out thoughts on that topic.

My history with ASQ extends back into my childhood. My father, William Hunter, was the founding chair of the ASQ Statistics division. They now administer the Hunter Award, which recognizes substantial contributions to statistical consulting, education for practitioners, and integration of statistics with other disciplines as well as demonstrated excellence in communication and implementing innovative applied statistical methods.

I joined with a group of people to lead the Public Sector Quality Improvement Network shortly after it was formed. The network aimed to help those in the public sector use quality management principles to improve performance. That group of people was one of the most impressive I have worked with; including Tom Mosgaller, Michael Williamson, Barry Crook, Nathan Strong and others. We decided to join with ASQ: that effort has become the ASQ Government Division. Another outgrowth of those efforts was my Public Sector Continuous Improvement Site, which I continue to run.

The Public Sector Network also connects back to my father; Tom Mosgaller and Michael Williamson worked on the quality efforts in the Madison, Wisconsin (at the City of Madison and the University of Wisconsin – Madison). Michael worked in for Joe Sensenbrenner, and then brought the new management ideas to his roles with university. My father approached the mayor, Joe Sensenbrenner, about applying management improvement ideas at the city. The mayor agreed and my father documented that effort in Dr. Deming’s classic, Out of the Crisis as the first government application of Deming’s management principles. See pages 245-247 of Out of the Crisis and also Joe Sensenbrenner’s classic article in the Harvard Business Review: Quality Comes to City Hall. Peter Scholtes was also part of that initial project at the First Street Garage in Madison, Wisconsin.

photo of Terry Holmes, Joe Turner and Bill Hunter

Terry Holmes (president of the local labor union), Joe Turner (division foreman) and Bill Hunter (consultant), working on the First Street Garage project. They went and presented to executives at Ford (where Dr. Deming was working) on the cooperation between union and management in the City of Madison project.

You can read a bit more about the work in Madison in George Box’s (an ASQ fellow) article – William Hunter: An Innovator and Catalyst for Quality Improvement. And also in: Doing More With Less in the Public Sector: A Progress Report from Madison, Wisconsin by William G. Hunter, Jan O’Neill, and Carol Wallen and Quality in the Community: One City’s Experience by George Box, Laurel Joiner, Sue Rohan and Joseph Sensenbrenner (1989). These documents are all made available by the Center for Quality and Productivity Improvement at the University of Wisconsin – Madison that was founded by George Box and my father.

Continue reading

Practical Ways to Respect People

What matters is not your stated respect for people but your revealed respect for people. Here are some ideas I collected after being prompted by a post by Ron Pereira: 7 Practical Ways to Respect People.

  • Don’t waste people’s time: have meetings only when necessary and provide agendas in advance. Use email effectively instead of presenting material in meetings that can better be presented in email. Don’t have complex benefit manuals, aimed at making lawyers happy, that employees are expected to use.
  • Do what you say you will.
  • Provide bad news early (don’t hope it will get fixed somehow so you don’t have to address it, let people know what is going on and let them help).
  • Pay people fairly – I would venture to say most senior executive pay today is inherently disrespectful, If I am wrong about the “most” part, certainly a huge amount executive pay is inherently disrespectful.
  • Put the long term success of all stakeholders as the focus (don’t risk people’s jobs for short term bonuses, don’t use large amounts of leverage risking the future of the company…). Respect all stakeholders and provide them confidence their long term success is important. Companies that find themselves laying off workers due to managements failure to succeed over the long term are not being respectful to those workers. That failure is most obvious today but the important improvement is not in handling the layoff today, it is in the behavior for years before that did not build a system that was successful in the long term.
  • Tell people what they can do to improve. It is respectful to help people improve. It is treating people like a child that needs to be shielding from any hint of weakness in need of improvement.
  • Don’t expect a few people to do far more than their fair share of work because management allows poor performance to continue un-addressed.
  • Continue reading

Rethinking or Moving Beyond Deming Often Just Means Applying More of What Dr. Deming Actually Said

Don Reinertsen – Is It Time to Rethink Deming? from AGILEMinds on Vimeo.

I feel very strongly about the value of Deming’s ideas. I am glad people challenge those ideas and try to push forward management thinking. Helping us manage organizations better (to get better results and allow people to better enjoy their jobs and lives) is why I value Deming’s ideas. To the extent we find better ideas I am very happy. I understand I will disagree with others on the best ways to manage, and believe healthy debate can be productive.

What Don Reinertsen discusses in the video, about special and common cause is not the best way to look at those ideas, in my opinion (though I would imagine it is the most common view). For data points that are common cause (within the control limits and not a special cause pattern) it is most effective to use common cause tools/thinking to improve. For indications of special cause (points outside the control limits or patterns in the data, such as continually increasing results that indicate a special cause) it is most effective to use special cause tools to improve.

This does not mean that a point outside the control limits is caused by a special cause (also know as assignable cause). It is just best to use special cause tools and thinking to address those data points (and the reason this is true is because it is most likely there is an assignable cause). The control limits do not define the nature of the point, they define the type of improvement strategy that should be used.

Don also says repeatedly that you don’t “respond to random variation” in Deming’s view. That is accurate. But then he implies this means you don’t address system performance, which is not. You work on improving systems (that are in control) by improving the system, not by responding to individual common cause data points (random variation) as if it were assignable cause variation.

The purpose of the control chart (that Shewhart developed) was to help you most effectively take action (knowing if special cause thinking, or system improvement, was the best improvement strategy). The control chart shows if the results are in control and tells you that the system is preforming consistently (and identifies a special cause so special cause tools can be used immediately, this is important because special cause improvement strategies are time sensitive). It tells you nothing about if the results are acceptable.

Continual improvement was also central to Deming’s management philosophy (based on the business value of the many improvement options available in every organization). For Deming this meant working on improving the system, if the results are in control, instead of trying to deal with finding a specific assignable cause for one data point and acting on that. If the issue is one of the system performance (no indication it is a special cause) the most effective strategy to get better results is to improve the system, rather than approach it as a special cause issue (examining individual data points, to find special items in that event to be improved). You can use special cause thinking, even where system improvement thinking would be better. It will work. It is just not very effective (improvement will be much slower) compared to focusing on system improvement.

I agree with Don that the United States mentality, not only in nuclear plants but everywhere, is to apply special cause thinking as the strategy for process improvement. This is one the areas Deming was trying to change. Deming, and I, think that setting your improvement strategy based on a common cause (system improvement) or assignable/special cause (learn what is special about that one instance) is the most effective way to achieve the best results. We believe in continual improvement. We believe that the effective way to improve, when a system is in statistical control, is by focusing on the whole systems (all the data) not assignable cause (special cause) thinking where you look at what is special about that bad (or good) individual result.

The economic consideration of whether the costs of improvements are worth the benefit is sensible (and I do not see Dr. Deming arguing against that). That is separate from the best method to improve. For Deming the best method to improve means using special cause thinking for assignable cause issues and common cause thinking for systems issues.

The idea of where to focus improvement efforts is not something Dr. Deming made as clear as he could have, in my opinion. So I see the argument of Deming not prioritizing where improvement should occur voiced occasionally. This is a weakness in Deming’s content, I believe, more than his philosophy (but I can understand it causing some confusion).
Continue reading

The Theory of Knowledge in Deming’s Management System: How Do We Know What We Know?

I contributed an article to the Process Excellence Network’s Deming Files that was published yesterday: How Do We Know What We Know?. I took on the task of explaining the theory of knowledge, as one article in a four part series looking at the four components of Dr. Deming’s System of Profound Knowledge.

The other 3 articles are:

I hope you enjoy all 4 articles. Every two weeks a new article is published by the Deming Files exploring Dr. Deming’s ideas on management. The articles provide a nice dose of views on applying Deming’s ideas today. The network also has series on Drucker ideas and articles on many other management topics (six sigma, lean, etc.).

Related: Deming on Management2009 post: How do we Know What we KnowData Doesn’t Lie, We Can Draw Incorrect Conclusions from DataCorrelation is Not Causation

Touring Factories on Vacation When I Was Young

Growing up, occasionally, a family vacation would include a factory tour related to my Dad’s work. He was providing some management or engineering consulting and took the opportunity to check in on progress and visit the gemba. Here is a photo from one of those tours (in Nigeria, I think). My brother and Mom are visible in the photo.

The tours (which were not a very common occurrence) were quite enjoyable and interesting. Though I really didn’t like how noisy the factories were. Seeing all the machines and vast scale of the systems was quite a change of pace and added some excitement to the vacations (that often were already pretty exciting). I remember we also visited some factories in Kenya (in between seeing the game parks).

photo of factory tour with my family when I was a kid

Factory in Nigeria (I think) that my family toured


On this tour we found a bit of visual management showing which side of a crate should be on the top.
Continue reading

I Will Co-Facilitate a Deming Seminar in Singapore July 25-27

image of the Deming medal

The W. Edwards Deming Institute is working with the NTUC LearningHub to offer management seminars in Singapore. I will be co-facilitating a Deming 2 1/2 day seminar in Singapore with Kelly Allan in July.

The 2 1/2 day Seminar, Deming’s New Philosophy of Management, is open for registration to the public so if you want to join us, sign up for the seminar which will be held July 25 to 27, 2011 in Singapore.

In the seminar you will learn the way of thinking taught by Dr. W. Edwards Deming. Those ideas have been used by leading companies around the world and the value of these management ideas is as high today as it has ever been. Applying these ideas will allow your organization to achieve higher quality, lower costs and increased productivity. As regular readers of this blog know I often write about these ideas here.

Seminar Overview
Application of Dr. Deming’s “New Philosophy of Management” gives you the insight to remove barriers to success, increase efficiencies, reduce waste, boost motivation, stimulate innovation and understand your organization and its real capabilities. Some improvements are as simple as stopping current practices and enjoying productivity increases. Others require learning and understanding the four key components of the “New Philosophy of Management:”
Continue reading

Engage in Improving the Management System

To actually improve management you need to engage in continual improvement of your management systems. This requires doing the hard work of challenging complacency. The job of those improving the practice of management is not to make everyone happy and just ignore that the words about improvement are not actually carrying through to changes in behavior.

Do Executives “Get It?”

So many times executives spout the importance of new initiatives like wellness programs, safety programs, or improvement projects like Lean, Six Sigma, etc. They talk about how great they are and how everyone should embrace them so the company can improve, but when push comes to shove, their actions indicate they really don’t believe in them.

If you are trying to bring about change you need in-process indications of actual success at improving the management system. Instead it seems to me, most of the time, the focus is on spinning what is being done to convince others that what is being done is good. This is not helpful and not useful.

Without in-process indications of how the movement to a better management system is performing the pattern is all too common. People want to show they are doing a good job (which often includes not being too negative – because if they criticize results they can be branded as negative). So instead we end up with actions that would be used if one assumed that while we had problems with the last 4 management fads we implemented, now we have this wonderful new idea it will avoid all the problems.

So we start our new process, and write up reports and presentations for meetings talking about our successes. We are careful to ignore any warning signs. Then, after 1, 2… years (in a good economy this can last quite a bit longer), the boss says the results are not improving, this isn’t working. Everyone quickly agrees and the improvement effort is dropped. Usually there will be a period of time taken until and a new fad is found that everyone agrees is wonderful for 2-5 years until they then all agree was a failure. Repeat for the rest of your career.

To break this cycle and actually continually improve we can’t go along with the in-process indications that the management improvement system is not really working. We need to seek out indications that it is not working and address those issues and build a strong continually improving management system.

Related: Management Advice Failuresflavors of management improvement effortsmanage what you can’t measureFederal Government Chief Performance Officer (a specific example of the repeated failure to improve), just pretending the failures in the past didn’t exist doesn’t help the current effort

Deming Seminar in Singapore: New Philosophy of Management

image of the Deming medal

The W. Edwards Deming Institute is working with the NTUC LearningHub to offer management seminars in Singapore. I will be co-facilitating at several seminars in Singapore with Kelly Allan and Kevin Cahill next month.

The 2 1/2 day Seminar, Deming’s New Philosophy of Management, is open for registration to the public so if you want to join us, sign up for the seminar which will be held January 18 to 20, 2011 in Singapore.

In the seminar you will learn the way of thinking taught by Dr. W. Edwards Deming. Those ideas have been used by leading companies around the world and the value of these management ideas is as high today as it has ever been. Applying these ideas will allow your organization to achieve higher quality, lower costs and increased productivity. As regular readers of this blog know I often write about these ideas here.

Seminar Overview
Application of Dr. Deming’s “New Philosophy of Management” gives you the insight to remove barriers to success, increase efficiencies, reduce waste, boost motivation, stimulate innovation and understand your organization and its real capabilities. Some improvements are as simple as stopping current practices and enjoying productivity increases. Others require learning and understanding the four key components of the “New Philosophy of Management:”

The seminar is conducted with facilitators. It is not lecture style and is interactive and significant time is spent in exercises or discussions and their application. The seminar is based on Dr. Deming’s two books on management – Out of the Crisis and The New Economics. It focuses on a philosophy of four components that lead to understanding of how the organization can work as a system, how an organization can learn as it develops, how to get the best out of people, and interpret data.

After the seminar you will have an understanding of the four critical elements of Deming’s “New Philosophy of Management” and how to apply it within your organization. They are:

Who Should Attend
The seminar material is applicable to senior executives and management in every size of business and service organization, education, retail, health care, government and manufacturing. It will benefit those being introduced to Deming’s thinking for the first time as well as those familiar with his philosophy.

Don’t Treat People Like You Want to be Treated

I have never understood the logic behind the idea that you should treat people like you want to be treated. I know I am different; I don’t want what lots of other people seem to want. If I treat them how I want to be treated, they are not happy.

I understand the sentiment behind the statement. I think it is much more effectively stated as: treat people how they want to be treated. An understanding of psychology will provide you with the understanding that people are different and want to be treated differently, while wanting to feel that they are valued and respected. Some people will like a boisterous extroverted environment and others will want to be able to have some time to concentrate and think by themselves. Some people will want to avoid confrontation at almost any costs others will want to deal openly and directly with issues confronting the organization. And most people will be somewhere in between the alternatives.

I don’t want to be thanked for trivial matters. But I have seen lots of people do like this. I do like to be challenged on what I claim and debate the merits of the idea (if I can learn I am wrong, it is much better to do it early and change – instead of waiting for some problem to develop). I notice a lot of others don’t like this at all. I don’t like to be interrupted when I am trying to concentrate. I know lots of others don’t understand this. And when they are treating others as they want to be treated the thought that others are trying to concentrate doesn’t cross their minds. They are not intentionally trying to be disruptive. They are trying to include others as they would like to be included. I find it annoying when we celebrate some minor success while much more serious problems are left unaddressed. I realize most others don’t have this problem.

I like to see data and evidence to back up claims and to explore what the data strongly shows and what conclusions are more tenuous. I know many just get bored by numbers and don’t want to see endless charts and figures. I like to be challenged and asked difficult questions in meetings. I know lots of people do not like this. I would like to ask other people difficult questions (but don’t – if I went with the treat people like you want to be treated idea I would ask). I like change that is part of a sensible strategy of improvement (that measures results to avoid change for that isn’t improvement, which I don’t like). However, I understand many people are uncomfortable with change. I despise sitting in meetings without agendas or a clear purpose that wander and don’t seem to accomplish anything. Others seem un-bothered by this (though I know in this feeling I am with the majority).

I think a key to managing people is to take time to think about the individuals involved, what your intention is, and then to act in a way that is tailored to how that person wants to be treated. Some people will want to be recognized publicly. Some people may want to discuss in private how they could do even better. Some people may like to be given the opportunity to lead a meeting. Others would rather be given the opportunity to create a new design for the intranet. Others may like the opportunity to train new staff on some aspect of their job. Some people may want opportunities to move up the corporate ladder. Others would rather have some time off to pursue other interests.

You should treat people how they want to be treated, not how you want to be treated.
Continue reading

No True Lean Thinking or Agile Software Development

“There is no true value of any characteristic, state, or condition that is defined in terms of measurement or observation.” – Dr. W. Edwards Deming.

The value depends on your operational definition.

Once you operationalize management ideas in a real organization it necessarily should have differences from how it is operationalized elsewhere. As Deming said there are no effective simple recipes for management. It is one of the frustrations people have with Dr. Deming: that there is no cookbook telling you what you should go do as a manager. You need to understand things like: interactions, variation, psychology, systems thinking, how we know what we know (and what we “know” that isn’t so). And then you need to make decisions about how to apply these concepts in your organization.

There is value in being able to think and discuss ideas in a broader context than your organization. You lose a great deal of learning opportunities if you can’t. And having common idea about what common principles a lean thinking organization or agile software organization should have is helpful I believe. That is aided by abstract ideals of these management practices.

Dilbert comic on the futility of process and arbitrary deadlines

One of agile’s guiding principles is individuals and interactions over processes and tools. I am a Deming follower and that emphasizes the importance of process and system. The words in agile are anti-process. But in my experience it is really a specific type of process – and that is basically idiotic adherence to process that the software developers are sick of. This attitude is best summed up in Dilbert. There are plenty of what I would call process in the practice of agile – sprints, kanban, work in process limits, define what done means, using user stories, retrospectives, build in quality… Basically I think it is important to understand what the principles mean, but don’t get locked into dogmatic ideas.

There are principles that seem to me necessary to, for example, consider an effort as lean management. There must be respect for people in lean management. If it isn’t there, then I don’t think it is lean. It might be management using some ideas and tools from lean, but it isn’t lean management. Exactly how respect for people is manifest is up to the organization. The same thing holds for other principles.

Thoughts on No True Agile, No True Lean, No True Latte

Related: Dr. Deming: There is No True ValueHow to Manage What You Can’t MeasureInvolve IT Staff in Business Process ImprovementThe Illusion of Knowledge

Continue reading

Good Process Improvement Practices

Good process improvement practices include:

  • standardized improvement process (pdsa, or whatever)
  • Going to the gemba – improvement is done where the work is done. You must go to the where the action is. Sitting in meeting rooms, or offices, reading reports and making decisions is not the way to improve effectively.
  • evidence based decision making, data guides decision making rather than HiPPO
  • broad participation (those working on the process should be the ones working on improving it and everyone in the organization should be improving their processes)
  • measurable results that are used to measure effectiveness
  • pilot improvement on a small scale, after results are shown to be improvements deploy standardized solutions more broadly
  • visual management
  • Standardized work instructions are used for processes
  • one of the aims of the improvement process should be improving peoples ability to improve over the long term (one outcome of the process should be a better process another should be that people learned and can apply what they learned in future improvements)
  • quality tools should be used, people should be trained on such tools. The tools are essentially standardized methods that have been shown to be effective. And most organization just ignore them and struggle to reinvent methods to achieve results instead of just applying methods already shown to be very effective.
  • the improvements are sustained. Changes are made to the system and they are adopted: this seems obvious but far too often process improvements are really just band-aids that fall off a few weeks later and nothing is done to sustain it.
  • goals, bonuses and extrinsic motivation are not part of the process
  • The improvement process itself should be continually improved

Continue reading

Positivity and Joy in Work

John and Bill Hunter

After my father died, for years (at least 10), people I never had met before would emotionally share what a positive influence he had on their lives. He did great stuff helping organizations improve. But the majority of people were not telling me how much he helped the organization improve [there were also a bunch of engineers and statisticians :-) that were more impressed with his insights and expertise]. But most people talked about was how much happier they were because of the changes he helped them see they could make in their lives.

He helped them expect to take joy from work and so they did (and a big part in taking joy in work for most is helping others take joy in work – you don’t find many workplaces with 15 miserable people and one joyful person). Many had to leave their current organizations that were too broken for them to fix. But after they saw what they should expect they couldn’t just keep passing time without joy in work.

Now I am sure their were hundreds of people that never talked to me that never made any such change. But the number of people that did took what was a decent chance that I would continue working with the management ideas I absorbed from him (data based decision making, Deming, joy in work, respect for people…) and made it a very great one. Unfortunately I am nowhere near as affective as he was.

Creating organization that show respect for people in the workplace and give them tools to improve is far more powerful than most people understand. Most people get scared about “soft” “mushy” sounding ideas like “joy in work.” I have to say I sympathize with those people. But it is true.

To get “joy in work” it isn’t about eliminating annoyances. Fundamentally it is about taking pride in what you do and eliminating the practices in so many organizations that dehumanize people. And to create a system where the vast majority of people can have joy in work most of the time requires a deep understanding and application of modern management improvement practices (Deming, lean thinking, etc.).

The photo shows Dad, William Hunter, and me on the beach.

In response to A Breath of Lean Positivity – Paul Akers

Related: William G. Hunter AwardPeter ScholtesJoy in Work, Software Development

The Problem is Likely Not the Person Pointing Out The Problem

I believe the problem is likely not the person pointing out the problem. Now granted I have often been that person. Part of what I have been tasked with doing in various jobs is finding ways to improve the performance of the organization. I was told the managers wanted to hear about problems from someone working there, so I was asked to do so. What it often meant was they wanted someone to fix the problems they thought existed not point out the problem was the systems, not the people forced to deal with the systems.

I have learned managers are a lot happier if I just shut up about all the problems that should be addressed. There are happy if I can fix what I can (though really they seem to care much more about not being negative than any actually improving) and just be quiet about anything else – otherwise you are seen as “negative.”

How to Manage Whining with no Problem Solving

As individuals begin to focus on the negative and don’t engage in problem solving, this behavior is unacceptable

The first time, it is a venting and commonly a subject matter problem. The next time we have a trend occurring, and this is where we need to coach our team player to be constructive process improvement artists. If the whining continues, we may be dealing with a negative attitude which has begun to permeate our colleague.

explore the previous solution’s outcomes; help the individual to be empowered to resolve the issue. If it is absolutely above the teammate authority, offer to help and commit to actions.

I think it is right to focus the effort on problem solving to improve the situation. I fear that far too often though “As individuals begin to focus on the negative and don’t engage in problem solving, this behavior is unacceptable.” turns into ignore problems. Yes, I know that isn’t what the post is suggesting. I am just saying that the easy “solution” that is taken far too often is to focus on the words “negative” and “unacceptable.”

I believe the focus should be on “broken systems are unacceptable.” I would prefer problem solving to address the issues but a culture of ignoring issues and seeing those that don’t as being negative is often the real problem (not the person that points out the problems).

I have discussed this topic in some posts previously: Ignoring Unpleasant Truths is Often Encouraged and Bring Me Problems, and Solutions if You Have Them. Once I am given those problems I agree with you completely. Use them as an opportunity to coach effective problem solving and process improvement strategies to improve the situation. And to develop people.

Often the problem is not the person at all. The organization never adopts fixes. People have learned that they can bang their head against the wall and then never get approval for the fix or they can just whine. Blaming them for choosing whining is not useful. I don’t see how Asking 5 whys you get to blaming the employee, except in very rare cases for not problem solving. It seems to me the issue is almost always going to lay with management: for why people are frustrated with system results and are not problem solving.
Continue reading

Involve IT Staff in Business Process Improvement

I started out basically working on management improvement from the start of my career. My makeup (I am never satisfied and figure things should always be better) along with a few traits, experiences and probably even genes made this a natural fit for me. I tend to take the long view and find fire fighting a waste of time. Why fix some symptom, I want to fix the system so that problem doesn’t happen again. My father worked in statistics, engineering and business improvement and as I was growing up I had plenty of experience with process improvement, understanding variation, experimenting, measuring results

I came into the IT world as I had needs and found the best solution was to write some software to help me accomplish what I wanted to. One thing that better software tools allowed is this type of thing when organizations failed to use technology well, individuals could just do so themselves. Without these tools people had to rely on the organization, but today atrophied IT organizations can often be circumvented. Though the IT organizations often try to avoid this largely by bans (instead of by providing the tools people need), which is not a good sign, in my opinion.

I then spent more and more of my time working with technology but I always retained my focus on improving the management of the organization, with technology playing a supporting role in that effort. That is true even as where I sat changed. And I have become more convinced organizations would be served well by using the information technology staff as business process experts.

At one point I sat in the Office of Secretary of Defense, Quality Management Office where I was able to focus on management improvement and using technology to aid that effort. Then I went to the White House Military Office, Customer Support and Organizational Development office and focused largely on how to using technology to meet the mission. Then I was moved into the White House Military Office, Office of Information Technology Management.

And now I work for the American Society for Engineering Education in the Information Technology department. My role started as partially program management and partially software development and as we have grown and hired more software developers I am now nearly completely a program manager.

I believe technology is a central component of understanding business processes today. But the truth is, many business people don’t have as complete an understanding as I feel they should. Now I believe, most anyone interested in planning their management career needs to develop a facility with technology and specifically how to use software applications to improve performance. You don’t need to be an expert programmer but you need to understand the strengths, weakness, limits of technical solutions. You need to understand how technology can be used (and the risks of options).

At the same time I just don’t think it is likely management everywhere will get a decent understanding of application software development. I also believe that in many cases organizations should do software development in house. This is a issue that certainly can be argued (but I won’t do it here). Basically I don’t think organizations should cram their processes into designs required by off the shelf software. Instead I believe they should design processes optimal for their organization and using off the shelf software often does the opposite (forces the process decisions around what software someone decided to buy). There is plenty of use for off the shelf software that doesn’t force you to make your processes fit into them (and sometimes even if it does that is the business decision that has to be made – I just think far too often organizations look at short term costs and not the overall best solutions for the system).
Continue reading

The Illusion of Knowledge

The greatest obstacle to discovery is not ignorance; it is the illusion of knowledge. – Daniel J. Boorstin

Great quote on a topic I discussed in, How We Know What We Know. Dr. Deming included the theory of knowledge as one of the 4 pillars of his management system. When you do not question what you think you know, and conventional thinking, that will keep you from discovery. Now much of conventional wisdom is right, so you often do well accepting whatever most people believe. But to discover you have to seek out new knowledge. And often the process is stopped before you even form the questions, because you think you have knowledge.

How can you understand if your beliefs are in fact knowledge? Test them. Do you have evidence that performance appraisals add value to your organization? Do you have evidence that outsourcing production is beneficial? Do you have evidence that paying CEOs a king’s ransom is helping? What evidence do you have that sales bonuses help the organization? If you don’t have evidence then you have a belief, not knowledge. You can be ignorant and hold a correct belief. Knowledge requires understanding not just correctness. At least that is how I see it, I am not sure what the philosophers say about this.

I also believe you can have evidence that seems to support your belief but still be wrong. You could site examples where sales bonuses seemed to stimulate extra sales that helped your company. But you could be failing to understand the full system and the other factors that 1) helped make the sale and 2) what damage the sales bonuses did that you didn’t consider. Knowledge isn’t easy. But most that are knowledgeable seek to question their beliefs and assumptions.

Related: Bogus Theories, Bad for BusinessThe Illusion of UnderstandingFlaws in Understanding Psychology Lead to Flawed Managementconfirmation biasPragmatism and Management KnowledgeOptical Illusions and Other Illusions

Certainty is risky. But I am also basically certain about many things (and think that is wise). I don’t have any doubt about how gravity it going to act on what I see in my daily life. I don’t doubt if I don’t take in liquids for days I will suffer and die eventually. I don’t doubt in trying to manage an organization you need to account for the psychology of people.
Continue reading

Statistical Engineering Links Statistical Thinking, Methods and Tools

In Closing the Gap Roger W. Hoerl and Ronald D. Snee lay out a sensible case for focusing on statistical engineering.

We’re not suggesting that society no longer needs research in new statistical techniques for improvement; it does. The balance needed at this time, however, is perhaps 80% for statistics as an engineering discipline and 20% for statistics as a pure science.

True, though I would put the balance more like 95% engineering, 5% science.

There is a good discussion on LinkedIn:

Davis Balestracci: Unfortunately, we snubbed our noses at the Six Sigma movement…and got our lunch eaten. Ron Snee has been developing this message for the last 20 years (I developed it in four years’ worth of monthly columns for Quality Digest from 2005-2008). BUT…as long as people have a computer, color printer, and a package that does trend lines, academic arguments won’t “convert” anybody.

Recently, we’ve lost our way and evolved into developing “better jackhammers to drive tacks”…and pining for the “good ol’ days” when people listened to us (which they were forced to do because they didn’t have computers, and statistical packages were clunky). Folks, we’d better watch it…or we’re moribund

Was there really a good old days when business listened to statisticians? Of course occasionally they did, but “good old days”? Here is a report from 1986 the theme of which seems to me to be basically how to get statisticians listened to by the people that make the important decisions: The Next 25 Years in Statistics, by Bill Hunter and William Hill. Maybe I do the report a disservice with my understanding of the basic message, but it seems to me to be how to make sure the important contributions of applied statisticians actually get applied in organizations. And it discusses how statisticians need to take action to drive adoption of the ideas because currently (1986) they are too marginalized (not listened to when they should be contributing) in most organizations.
Continue reading

Interruptions Can Severely Damage Performance

Interruptions can severely degrade your performance. The type of work you are doing impacts the cost greatly. I have spent some of my time programming web applications. When I am doing that interruptions are huge drain on my performance (for me the costs of interruptions while programming are far higher than any other type of work I have done – many times higher). If the interruption disrupts my flow (an interruption needn’t necessarily disrupt it I found, instant messages may not, while speaking to someone else almost surely would – it is a factor of how much of your brain much shift focus I imagine) it can take a huge amount of time to get back into a high performing state. Other work I do can be interrupted with much less impact. I am easily able to slip back into what I was doing.

For me the main cost of interruptions is the time it takes to get back to where I was before the interruption. And the cost is related to how much focus is needed to address what you are working on. Most programming takes a huge amount of focus.

Another big cost of interruptions is the increased risk of mistakes. When people are distracted and then have to go back to a task, and then are distracted, and then go back and… it is more likely they will miss a step or miss noticing some issue than if they can work without distraction. One tool to help cope for distractions that can’t be designed out are checklists.

Paul Graham addressed the importance of managing the system to provide uninterrupted time very well in, Maker’s Schedule, Manager’s Schedule

One reason programmers dislike meetings so much is that they’re on a different type of schedule from other people. Meetings cost them more

Most powerful people are on the manager’s schedule. It’s the schedule of command. But there’s another way of using time that’s common among people who make things, like programmers and writers. They generally prefer to use time in units of half a day at least. You can’t write or program well in units of an hour. That’s barely enough time to get started.

Paul Graham’s article also shows why managers so often fail to adequately address this issue. Manager, by and large, work in an environment where interruptions are the work. I know, much of my time as a program manager is driven by interruptions and is doable even with many interruption every day.

When managing you need to understand how big a cost interruptions have and design systems appropriate to optimize system performance for all parts of the system. The design of the system needs to take into account the costs and benefits of interruptions for those people working on various processes in the system.

Related: Understanding How to Manage GeeksExplaining Managers to ProgrammersWhat Motivates Programmers?Joy in Work – Software DevelopmentProgrammers CartoonChecklists in Software Development

  • Recent Trackbacks

  • Comments