Podcast: Building Organizational Capability

The Software Process and Measurement Cast 420 features an interview with me, by Thomas Cagley, on Building Organizational Capability (download podcast).

John Hunter in the podcast:

Changing how organizations are managed makes a huge difference in people’s lives, not all the time and I understand most of the time it doesn’t. But when this is done well people can go from dreading going to work to enjoying going to work, not every single day – but most days, and it can change our lives so that most of the time we are doing things that we find valuable and we enjoy instead of just going to work to get a paycheck so we can enjoy the hours that we have away from work.

photo of John Hunter

John Hunter, Zion National Park, Utah, USA

Here are some links where I go into more detail on some of the topics I discuss in the podcast:

Thomas Cagley: If you have the power to change any 2 things that affect decision making what would they be and why?

John Hunter:

First that results are evaluated. Make decisions then evaluate what actually happens based upon what you do. Learn from that, improve how you make future decisions and keep iterating.

That idea of evaluating what actually happens is extremely powerful and will reinforce going in the right direction because if you evaluate most decisions many organizations make nothing got any better. And after doing that many times you can learn this isn’t working, we need to do something better.

And the second would be more prioritization. Make fewer decisions but take more time to make those decisions, implement those decisions, evaluate those decisions, learn from those results and iterate again.

I hope you enjoy the podcast.

Related: Software Process and Measurement Podcast With John Hunter on my book Management MattersDeming and Software Development

Posted in Management, Systems thinking | Tagged , , , , , , , , , , , , , | 2 Comments

Continually Improving Using a Focus on Delighting Customers

ASQ asked the ASQ influential voices to respond to this question: What is the best way to ensure quality and customer integration grow together?

When I first got involved in the quality field that name (quality) seemed to vague for me. And different people and organizations seemed to have vastly different meanings in mind for efforts they all grouped under the heading of quality. What I came up with to capture what I was interested in was customer focused continuous improvement. Continual is actually a better word than continuous for what I had in mind, I now know.

But that phrase has held up in my mind (unfortunately it is a bit long and so isn’t ideal either). Focusing on continually improving with a deep understanding of customer needs and the marketplace will do you well. Customer integration is required in the customer focused continual improvement framework I have discussed on this blog and in my book: Management Matters: Building Enterprise Capability.

Beach with reclining chairs and thatched toped umbrella looking into the ocean with small boats in the view

Wonderful beach near Hoi An, Vietnam where you can order food and drinks in peace. See more photos by John Hunter.

Accepting that as a wise course of action leaves the question of how to continual improve with an integrated deep focus on customers. These shouldn’t be two isolated activities. And even to continually improve without worrying about customers requires viewing the organization as a system is critical in my view (which further enhances integrating the customer into the organization’s DNA). As anyone reading this blog knows my beliefs build on the work of W. Edwards Deming, so appreciating the importance of a systemic view is to be expected.

A deep appreciation for the long term needs of your customers and potential customers should guide where in the system to continually improve. And my belief on how to continual improve is to create and continually improving management system with principles of experimentation (with the necessary understanding of what conclusion can be drawn from results and what cannot), an understanding of the organization as a system and respect for people as principles to be guided by to achieve continual improvement.

Quality practices of experimentation directed at continually improving management practices and internal processes need to be completely integrated with the efforts to continual improve customer delight. Those efforts should be one process and therefore they automatically grow together.

Continue reading

Posted in Customer focus, Management, Process improvement, Systems thinking | Tagged , , , , | 1 Comment

Add Constraints to Processes Carefully

Take great care in adding constraints to processes to avoid doing so needlessly.

Online you will frequently find forms that have required fields that needn’t be. Certainly if you were designing with focus on what is best for customers those requirements rarely make sense. Occasionally a required field is a sensible constraint on an online form but so often they add unnecessary constraints.

I frequently find those forms even requiring a false answer since a response is required and none of the options are true. Often this is because the organization is thinking of the boxes they expect users to fit themselves into rather than thinking how to create the best user experience.

I wrote previously about a company representative that suggested a customer change their name because the computer system didn’t accept names with 2 characters. Constraints on creating a secure password are a frequent failure of web sites for the last 10 years.

Man without arms denied housing loan due to inability to provide fingerprints

because Wu Jianping has no arms, creditors claimed they could not give him a loan since he was unable to be fingerprinted.

After the case was publicized and there was a great deal of negative publicity on social media the banks modified their process and approved the loan. But your organization shouldn’t have as the mistake-proofing (obviously not mistake-proofing at all) that when the process doesn’t quite work well then rely on a massive social media outcry which is a signal to us to straighten out the issue.

Frequently I see unnecessary constraints creating the edge case excuse. By burdening your process with unnecessary constraints you create edge cases that fail and then use the excuse that each of the edge cases is rare and therefore you can’t justify the expense of fixing them.

But if you designed the process sensibly in the first place the edge case never would have failed and you wouldn’t need special work arounds for such “edge cases.” A simple example of this is unnecessarily complex web page code that fails if to submit a button without javascript. Yes, a small number of users won’t have enabled all javascript to run (today anyway) so it is an “edge case” to deal with if you don’t have the form work without javascript. But there is no decent reason to have it fail in most cases.

Continue reading

Posted in Customer focus, IT, Software Development | Tagged , , , , , , , | Comments Off on Add Constraints to Processes Carefully

Bell Labs Designing a New Phone System Using Idealized Design

I remember hearing this same story when Russ Ackoff spoke at the Hunter Conference on Quality (which was named in honor of my father) in Madison, Wisconsin.

If you haven’t heard this story you are in for a treat. And if you haven’t heard Russell Ackoff before you get to enjoy a great storyteller.

"Tape" of Ackoff’s Bell Lab Lecture at the US Navy.

If you would limit yourself to paying attention to 5 thinkers to advance your understanding of managing organizations Ackoff should be one of them. Of course, many managers don’t even try to learn from 5 leading management thinkers to do their jobs better over their career. So for many people just learning from Ackoff, Deming, Scholtes etc. they would be far ahead of the path they are now for their career. Of course you are not limited to learning from 5 people so you can learn from more if you want to be a better manager and leader.

I probably remember a great deal from maybe 5 talks from the more than 5 years I attended the Hunter Conference (and they were the best conferences I have attended – this might explain why the last conference I attended was maybe 7 years ago). This was one of them. And I realized that Ackoff was someone I could learn a great deal from and it caused me to learn a great deal from Russ Ackoff over the next decade.

Watch the video for much more but the basic idea of idealized design is to create a new design for a product, service or the organization based on existing feasibility but without the constraints of the existing setup. Then you can use that ideal to figure out a plan to move from the existing state to that idealized design. Russell Ackoff co-authored a good book on the topic: Idealized Design.

Related: Ackoff, Idealized Design and Bell Labs (2006)Corporations Are Not Led By Those Seeking to Maximize Shareholder Value, Russ AckoffTransformation and Redesign at the White House Communications AgencyRussell L. Ackoff: 1919 -2009Dr. Russell Ackoff Webcast on Systems ThinkingDesigning a New Organization (2005)

Posted in Innovation, Management, Process improvement, Systems thinking | Tagged , , , , , , , , | 3 Comments

Burning Toast: American Health System Style

Democrats and Republicans have created a health care system in the USA over the last 40 years that “burns toast” at an alarming rate. As the symptoms of their health care system are displayed they call in people to blame for burning toast.

Their participation in the “you burn, I’ll scrape” system is even worse than the normal burning then scraping process. They create a bad system over decades and ignore the burnt toast just telling people to put up with it. And when some burnt toast can’t be ignored any longer they then blame individuals for each piece of burnt toast.

They demand that those they bring before them to blame, scrape off the burnt toast. And they act shocked that the “toaster” burns toast. It is the same “toaster” they designed and maintain at the behest of those benefiting from burnt toast and of course it burns toast (those results are the natural outcome of the system they designed and maintain).

We need to fix the decades old broken toaster that the Democrats and Republicans built and have maintained. Dr. Deming called excessive healthcare costs a deadly disease decades ago yet Democrats and Republicans allowed it to continue harming us year after year and decade after decade.

We don’t need distractions blaming a few individual for what the two parties have created and maintained for decades. We need leaders to address the real issues and stop the distraction that those benefiting from the current system want to continue to see from those in Washington.

You don’t fix the system if all you do is blame individuals for each piece of burnt toast. Fixing blame on each piece of burnt toast is exactly what those that have continued to make sure the system is designed to continually burn toast love to see. It is a good way to make sure the fixes needed to the design of the toaster are not addressed. Both political parties have done well by those they receive payments from to ensure that the current toaster isn’t changed.

For decades the data shows the USA health care system costs are nearly double that of other rich countries with no better results. And we are not comparing to some perfect ideal, those efforts we compare to need much improvement themselves. So how bad much the USA health care system be to cost nearly twice as much as those systems that have plenty of room for improvement themselves?

Related: EpiPen Maker Also Hiked Prices on a Slew of Other MedicationsUSA Health-Care System Ranks 50th out of 55 CountriesDrug Prices in the USA, a system continually burning toast (2005)USA Heath Care System Needs Reform (2009)2015 Health Care Price Report – Costs in the USA and Elsewhere

Posted in Economics, Health care, Management, Public Sector | Tagged , , , , , | Comments Off on Burning Toast: American Health System Style

Lead by Building Organizational Capability

The result of a recent interview with me has been posted: How to Lead From Any Level In the Organization [broken link replaced by new link to content hosted on this site]

2. Help people solve their problems.

Similar to helping other people grow their careers is the idea of helping other people to solve their problems. Again, this starts with a clear understanding of your sphere of influence. “It determines what strategies you can pursue, and building your sphere of influence should be part of your decision making process.”

What it comes down to is proving yourself in this way—and doing so consistently. “It isn’t some secret sauce. Prove yourself to be valuable and you will gain influence. Help people solve their problems. They will be inclined to listen to your ideas.” And helping people to solve their problems doesn’t mean you are giving them the answer. It may mean you asking empowering questions.

John says if you focus on building the capability in the organization to understand variation and to appreciate how to use data—then you are on the right path, and can increase your influence in addition.

“You need to build into the organization things like a focus on pleasing the customer instead of pleasing your boss.” When combining all of these methods, that is when your leadership is going to be most effective.

Hopefully you will find the entire post worthwhile.

More links related to interviews with me about improving management: Leadership While Viewing the Organization as a System, Business 901 Podcast Deming’s Management Ideas Today, Meet-up: Management Improvement Leader John Hunter.

Posted in Deming, Management | Tagged , , , , | 1 Comment

Applying Toyota Kata to Agile Retrospectives

Hakan Forss, King (interactive entertainment games), presentation at the GOTO Copenhagen 2015 conference.

I strongly recommend Mike Rother’s book: Toyota Kata.

Description from Workshop description “The Toyota Kata Experience”

Kata means pattern, routine, habits or way of doing things. Kata is about creating a fast “muscle memory” of how to take action instantaneously in a situation without having to go through a slower logical procedure. A Kata is something that you practice over and over striving for perfection. If the Kata itself is relative static, the content of the Kata, as we execute it is modified based on the situation and context in real-time as it happens. A Kata as different from a routine in that it contains a continuous self-renewal process.

I think the great number of worthwhile conference presentations we can all now get sitting wherever we are provides us a great opportunity (and lets us avoid missing out of good ideas because “How could they know“).

A point made in the presentation that is very simple but still constantly the source of failure is that the current system isn’t supporting improvement. Retrospectives are a good method to help improve but if there is no time to think about the issues raised and come up with experiments to improve and review of whether those experiments worked or not and why failure to improve is the expected result.

Creating a culture where it is expected that any improvement ideas are tested and evaluated is one of the most important changes on the path to a company that will be able to continually improve. If not, what happens is some changes are good, many are not and soon people lose faith that any effort is worth it because they see how poor the results are. By taking care to evaluate what is working and what isn’t we create a process in which we don’t allow ad hoc and unsuccessful changes to demoralize everyone.

Continue reading

Posted in Lean thinking, Process improvement, Software Development | Tagged , , , , , , | 3 Comments

Understanding Design of Experiments (DoE) in Protein Purification

This webcast, from GE Life Sciences, seeks to provide an understanding Design of Experiments (DoE) using an example of protein purification. It begins with a good overview of the reason why multi-factorial experiments must be used while changing multiple factors at the same time in order to see interactions between factors. These interactions are completely missed by one-factor-at-a-time experiments.

While it is a good introduction it might be a bit confusing if you are not familiar with multi-factorial designed experiments. You may want to read some of the links below or take advantage of the ability to pause the video to think about what he says or to replay portions you don’t pick up immediately.

I have discussed the value of design of experiments in multiple posts on this blog in the past, including: Introductory Videos on Using Design of Experiments to Improve Results by Stu Hunter, Design of Experiments: The Process of Discovery is Iterative and Factorial Designed Experiment Aim.

He also provides a good overview of 3 basic aims of multivariate experiment (DoE):

  • screening (to determine which factors have the largest impact on the results that are most important)
  • optimization (optimize the results)
  • robustness testing (determine if there are risks in variations to factors)

Normally an experiment will focus on one of these aims. So you don’t know the most important factors you may choose to do a screening experiment to figure out which factors you want to study in detail in an optimization experiment.

It could be an optimized set of values for factors provides very good results but is not robust. If you don’t have easy way to make sure the factors do not vary it may be worthwhile to choose another option that provides nearly as good results but is much more robust (good results even with more variation within the values of the factors).

Related: YouTube Uses Multivariate Experiment To Improve Sign-ups 15% (2009)Combinatorial Testing for Software (2009)Marketers Are Embracing Statistical Design of Experiments (2005)

Posted in Design of Experiments | Tagged , , , , , | Comments Off on Understanding Design of Experiments (DoE) in Protein Purification

Integrating Technical and Human Management Systems

ASQ has asked the Influential Voices on quality management to look at the question of integrating technical quality and human management systems. How do different systems—technical or human—work together? How should they work together?

My view is that the management system must integrate these facets together. A common problem that companies face is that they bring in technical tools (such as control charts, PDSA improvement cycle, design of experiments, kanban, etc.) without an appreciation for the organization as a system. Part of understanding the organization as a system is understanding psychology within this context (as W. Edwards Deming discussed frequently and emphasized in his management system).

To try and implement quality tools without addressing the systemic barriers (due to the management system and specifically the human component of that system) is a path to very limited success. The failure to address how the organization’s existing management system drives behaviors that are often counter to the professed aims of the organization greatly reduces the ability to use technical tools to improve.

If the organization rewards those in one silo (say purchasing) based on savings they make in cutting the cost of supplies it will be very difficult for the organization to optimize the system as a whole. If the purchasing department gets bonuses and promotions by cutting costs that is where they will focus and the total costs to the organization are not going to be their focus. Attempts to create ever more complex extrinsic incentives to make sure the incentives don’t leave to sub-optimization are rarely effective. They can avoid the most obvious sub-optimization but rarely lead to anything close to actually optimizing the overall system.

image of the cover of Managmenet Matters by John Hunter

Management Matters by John Hunter

It is critical to create an integrated system that focuses on letting people use their brains to continually improve the organization. This process doesn’t lend itself to easy recipes for success. It requires thoughtful application of good management improvement ideas based on the current capabilities of the organization and the short, medium and long term priorities the organization is willing to commit to.

There are principles that must be present:

  • a commitment to treating everyone in the organization as a valuable partner
  • allowing those closest to issues to figure out how to deal with them (and to provide them the tools, training and management system necessary to do so effectively) – see the last point
  • a commitment to continual improvement, learning and experimentation
  • providing everyone the tools (often, this means mental tools as much as physical tools or even quality tools such as a control chart). By mental tools, I mean the ability to use the quality tools and concepts. This often requires training and coaching in addition to a management system that allows it. Each of these is often a problem that is not adequately addressed in most organizations.
  • an understanding of what data is and is not telling us.

An integrated management system with an appreciation for the importance of people centered management is the only way to get the true benefit of the technical tools available.

I have discussed the various offshoots of the ideas discussed here and delved into more details in many previous posts and in my book – Management Matters: Building Enterprise Capability. An article, by my father, also addresses this area very well, while explaining how to capture and improve using two resources, largely untapped in American organizations, are potential information and employee creativity. It is only by engaging the minds of everyone that the tools of “technical” quality will result in even a decent fraction of the benefit they potentially can provide if used well.

Continue reading

Posted in Management, Psychology, Systems thinking | Tagged , , , , , , , , | 2 Comments

Unintended Consequences

Using data to understand your processes and improve them is very useful.

But using data often results in unintended consequences. If you don’t have a good understanding on the pressures collecting data will bring to bear on the system you can create pressure for results that damage the delivery of value to customers.

In this example there are requirements to take action if certain conditions are present. In this case, if the airplane is pushed back from the gate for more than 3 hours without taking off passengers must be given the opportunity to get off.

The Tarmac Delay Rule in 2010 has led to a jump in the rate of flight cancellations

Indeed, to avoid the fines, airlines are now far more likely to cancel flights that are sitting at the gate or on the tarmac than they once were, explains Vikrant Vaze, an assistant professor of engineering at Dartmouth and a co-author of the study. That means you’re now more likely to board your plane, sit there, and then still have the flight canceled.

It doesn’t seem the conditions imposed are unreasonable to me. But the expectation was for airlines to make sensible adjustments and not force customers to wait so long in the airplane sitting on the ground. The system could be improved by having more gates in operation, not pushing loading planes if you knew plane wasn’t going to leave for more than 30 minutes, etc.. But when customer value is taken very lightly (as USA airlines do) it isn’t surprising the USA airlines would take a very customer unfriendly method to avoid the issue that was the source of the new rules.

Distorting the system or distorting the data are often the result, instead of the process improvement that is desired and expected.

Related: Bad Weather is Part of the Transportation SystemPoor Customer Service at USA AirlinesData is Important and You Must Confirm What the Data Actually SaysUnited Breaks GuitarsRespect for Employees at Southwest Airlines

Posted in Customer focus, Management, Process improvement, Systems thinking | Tagged , , , | 1 Comment