Tag Archives: continual improvement

How to Lead From Any Level In the Organization

This was originally published on the Aileron blog; since it has been deleted from the blog I have reposted it here.

In looking to create great results, we have to balance getting results in the near-term with building our organization’s capability to maximize results in the long-term.

But what are the methods and ways in which we can help encourage this kind of continual improvement within our organization? And how can anyone, no matter their role or authority level, create value and shape their influence so that the company can amplify positive results?

To answer these questions, we asked John Hunter, a Senior Facilitator for the W. Edwards Deming Institute. John has also written a book called Management Matters: Building Enterprise Capability, a book that provides an overview for using a systems view of management.

The Art of Influence in an Organization

John says that in Steven Covey’s book, The Seven Habits of Highly Effective People, there are three concepts brought up: the circle of control, the circle of influence, and the circle of concern. When it comes to leading and influencing other people in an organization, these concepts provide an effective framework to look at how you can influence decisions over time.

The circle of concern is what we are concerned with at work. “Our circle of concern covers those things we worry about. Often, we believe because we worry, that we should find solutions,” explains John. For example, an employee who regularly has face-to-face interaction with customers might have a sphere of concern that is centered on pleasing customers.

In your circle of control, you have much more autonomy—and much more perceived control. “The idea is that this domain is totally within your control, you don’t have to worry about convincing other people,” he says.

“This is a useful construct, but it is often much more complex than it sounds. What it really comes down to is almost everything is in your sphere of influence. When you’re talking about organizations—which are made up of people—nearly everything is about sphere of influence. Even the stuff that’s called circle of control is largely influence,” says John.

Recognize that you can change (and grow) your sphere of influence over time

Continue reading

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

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

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

Don’t Ignore Customer Complaints

I find Paul Graham’s ideas very useful. I disagree with his recent tweet though.

tweets from Paul Graham

Update: See note at bottom of the post – Paul tweeted that his original tweet was wrong.

Base your assessment of the merit of an idea on the actual merit of the idea, not the category you place the person in that is expressing the idea.

His reply tweet addresses the problem with the first one in a very specific case. But you have “bugs” that are part of your management system, “policies,” products or services. Few customers will bother to voice those problems. Rather than ignoring some of what you hear, you should evaluate the merit of the complaint.

If the complaint is not something that should be addressed or explored fine. But that has nothing to do with the category of the person (“complainer” or not); it has to do with the merit of the complaint.

I understand some people are annoying because they make lots of meritless complaints. Ignoring the meritless complaints is fine with me. But just as I think ignoring advice because the person giving the advice doesn’t follow it is a bad practice I think having a policy of basing decisions on something other than the merit of the complaint/suggestion is unwise.

This is especially true since organizations on the whole do a lousy job of listening to customers and understanding customer desires. We need to greatly enhance the practice of customer focus not seek to reduce it. Every organization is unique, however, and if customer focus is exceptionally great, I can understand the idea of the tweet: that we are devoted to customer focus and each new insight, but we have taken it too far and need to discriminate better. I still think discriminating based on the merit of the complaint is a better than doing so based on our categorization of the complainer but in that case (which is very rare in organizations) the advice isn’t nearly as bad as it is for most organizations.

Continue reading

Take Advantage of the Strengths Each Person Brings to Work

The players have weaknesses. But it is our job as coaches to find the strengths in what our guys do. They all have strengths, and that’s what we highlight. What really helps is having Russell. He is so committed to improving on the littlest things every day. I try to find a word for this sometimes, but I can’t … it’s his refusal to fail. No detail is too small, and he makes sure to stress that every day.”

Darrell Bevell, offensive coordinator of the world champion Seattle Seahawks and former quarterback of the Wisconsin Badgers provides a good guide for managers. “Russell” in the quote is Seattle’s quarterback Russel Wilson; also a UW-Madison alumni.

Street art in Singapore 4 people sitting and a kid

Street art in Singapore. Photo by John Hunter.

Managers should be setting up the organization to take maximum advantage of the strengths of the people in the organization while minimizing the impact of weaknesses.

“Refusing to fail” by saying you refuse and yelling and stomping around if you fail doesn’t work. But if you commit to improve, not just the exciting stuff but every important detail you can create a climate of success. You create a system that works and builds on the skills, ability and desire to do great work that your employees bring to work.

Sure you fix what is broken. But you also improve what is working well. You figure out where the system isn’t optimized for the abilities of the people and you address that by changing the system to take advantage of everyone’s capabilities while limiting the impact of people’s weaknesses.

Continue reading

Revolutionary Management Improvement May Be Needed But Most Management Change is Evolutionary

This month the ASQ Influential Bloggers were asked to respond to the question – will the future of quality be evolutionary or revolutionary?

I think it has been and will continue to be both.

Revolutionary change is powerful but very difficult for entrenched people and organizations to actually pull off. It is much easy to dream about doing so.

Often even revolutionary ideas are adopted in a more evolutionary way: partial adoption of some practices based on the insight provided by the revolutionary idea. I think this is where the biggest impact of W. Edwards Deming’s ideas have been. I see him as the most revolutionary and worthwhile management thinker we have had. But even so, few organizations adopted the revolutionary ideas. Most organizations nibbled on the edges and still have a long way to go to finally get to a management system he was prompting 30,40 or more years ago.

A few organizations really did some revolutionary things based on Deming’s ideas, for example: Toyota. Toyota had some revolutionary moves and adopted many revolutionary ideas brought forward by numerous people including Taichii Ohno. But even so the largest impact has been all those that have followed after Toyota with the lean manufacturing strategies.

And most other companies have taken evolutionary steps from old management paradigms to adopt some new thinking when trying out lean thinking. And frankly most of those efforts are so misguided or incredible small they barely qualify. But for those that successfully improved their management system they were mainly evolutionary.

Continue reading

Root Cause, Interactions, Robustness and Design of Experiments

Eric Budd asked on The W. Edwards Deming Institute group (LinkedIn broke the link with a register wall so I removed the link):

If observed performance/behavior in a system is a result of the interactions between components–and variation exists in those components–the best root cause explanation we might hope for is a description of the interactions and variation at a moment in time. How can we make such an explanation useful?

A single root cause is rare. Normally you can look at the question a bit differently see the scope a bit differently and get a different “root cause.” In my opinion “root cause” is more a decision about what is an effective way to improve the system right now rather than finding a scientifically valid “root cause.”

Sometimes it might be obvious combination which is an issue so must be prevented. In such a case I don’t think interaction root cause is hard – just list out the conditions and then design something to prevent that in the future.

Often I think you may find that the results are not very robust and this time we caught the failure because of u = 11, x = 3, y = 4 and z =1. But those knowledge working on the process can tell the results are not reliable unless x = 5 or 6. And if z is under 3 things are likely to go wrong. and if u is above 8 and x is below 5 and y is below 5 things are in trouble…

To me this often amounts to designing systems to be robust and able to perform with the variation that is likely to happen. And for those areas where the system can’t be made robust for some variation then designing things so that variation doesn’t happen to the system (mistake proofing processes, for example).

In order to deal with interaction, learn about interaction and optimize results possible due to interactions I believe the best method is to use design of experiments (DoE) – factorial experiments.

Continue reading

A Good Management System is Robust and Continually Improving

imagine various people working within it, somehow swapping out gears and cogs without the clock stopping or slowing down even a little.

This is a fairly good quote on a good management system. Some people might not like the mechanistic model – comparing an organization to a clock, and I agree that isn’t the right model, but even so it is a good quote.

The quote, from a story about the San Antonio Spurs captures what should happen with a good management system. Things just keep running well as inevitable changes take place (and keep getting better in the case of a management system).

A good management system doesn’t rely on heroic efforts to save the day. The organization is designed to success. It is robust. It will succeed with all the variation thrown at it by the outside world. A good management system takes advantage of the contributions people offer, but it is not perform poorly when others are relied on.

A well run organization has graceful degradation (when one component fails or one person is missing the performance doesn’t suffer, bad results are avoided).

With software for example, a decently created web sites may use javascript to enhance the user experience but if javascript is unavailable the site works fine (just missing some neat features that are nice but don’t prevent users from getting what they need). Poorly designed software has critical dependencies on conditions that cannot be guaranteed to be present for end users and the software just fails to work when those conditions are not met. Ungraceful degradation is too common in software. It is also too common in our management systems.

An organization succeeds because of the efforts of many great people. But the management system has to be created for an organization to prosper as what we all know will happen, happens: people will leave and need to be replaced. And the people that stay will need to adjust to new conditions inside the organization and in response to external forces. A good management system is constantly improving performance, innovating, increasing the robustness of systems and increasing the capability of people.

Related: Bad Weather is Part of the Transportation SystemHow to Sustain Long Term Enterprise ExcellencePerformance dependent on specific individuals is not robust and not capable of continuous high quality performanceEuropean Blackout: Human Error-Not

Toyota Understands Robots are Best Used to Enhance the Value Employees Provide

Toyota has always seen robotics as a way to enhance what staff can do. Many USA executives think of robotics as a way to reduce personnel. Toyota wants to use the brainpower of employees to continually improve the organization. Toyota wants to free people for monotonous or dangerous work to let them use their minds.

Humans Steal Jobs From Robots at Toyota

Humans are taking the place of machines in plants across Japan so workers can develop new skills and figure out ways to improve production lines and the car-building process.

“We cannot simply depend on the machines that only repeat the same task over and over again,” Kawai said. “To be the master of the machine, you have to have the knowledge and the skills to teach the machine.”

Kawai, 65, started with Toyota during the era of Taiichi Ohno, the father of the Toyota Production System envied by the auto industry for decades with its combination of efficiency and quality. That means Kawai has been living most of his life adhering to principles of kaizen, or continuous improvement, and monozukuri, which translates to the art of making things.

“Fully automated machines don’t evolve on their own,” said Takahiro Fujimoto, a professor at the University of Tokyo’s Manufacturing Management Research Center. “Mechanization itself doesn’t harm, but sticking to a specific mechanization may lead to omission of kaizen and improvement.”

We need more companies to learn from the executives at Toyota. They show real respect for people. They are not focused on how much they can extract from the corporate treasury to build themselves castles at the expense of other employees, customers and stockholders as far too many USA executives are.

Toyota has been extremely innovative in investing in robotics as human assistants (partially this is due to the extreme demographic problems Japan faces): Toyota Develops Thought-controlled WheelchairToyota’s Partner RobotToyota Winglet – Personal Transportation Assistance.

Related: Webcast on the Toyota Development ProcessDon’t Hide Problems in ComputersAkio Toyoda’s Message Shows Real Leadership