Blog posts on continual improvement

Posts selected fromManagement Blog - Engineering Blog - Investing Blog and other blogs

• Management Tools for Quality Improvement Succeed When Practicing Respect for People

  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: Management Tools for Quality Improvement Succeed When Practicing Respect for People
• Applying Toyota Kata to Agile Retrospectives

  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.

  continue reading: Applying Toyota Kata to Agile Retrospectives
• Examine the Results of Your Testing Practices and Continually Improve Your Methods

  The idea of delibrately examining your software development and testing practices will be familar to those using agile retrospectives. The power of continually improving the development practices used withing the organization is hard to appreciate but it is immense. The gains compound over time so the initial benefits are only a glimpse of what can be achieve by continuing to iterate and improve.

  continue reading: Examine the Results of Your Testing Practices and Continually Improve Your Methods
• How to Lead From Any Level In the Organization

  From an interview with me:

  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.”

  continue reading: How to Lead From Any Level In the Organization
• Unpacking the Components of Hard Work to Design Better Work Conditions

  “Hard work” is often code for “work I despise doing.” If you create a system where people take pride and joy in their work the same time spent working is not nearly as “hard.” If they are proud of what they accomplish a difficult task is often rewarding, and not seen as working “harder.” As is so often the case “hard work” is really packing together numerous ideas in one phrase.

  • long hours
  • difficult tasks (physically, emotionally or intellectually)
  • unrewarding work
  • unpleasant tasks
  • inflexible work (It is a “hard job” if it prevents you from for example, seeing your child’s basketball game. If you were able to see the game and finish up 2 hours of work after they went to bed that is less hard.)

  continue reading: Unpacking the Components of Hard Work to Design Better Work Conditions
• Break Down Barriers Between Departments

  Addressing these secondary, tertiary… effects is usually more challenging. We normally can’t directly tackle the issue. Just telling people to work together doesn’t do much good if the management system drives them to different behavior. Such support for “teamwork” is merely a slogan without the necessary management commitment. We need to change the management system and the behavior of those in leadership positions in the organization.

  continue reading: Break Down Barriers Between Departments
• Improving the System to Reduce Costs Isn’t The Same as Cost Cutting

  Cutting costs by fiat via executive orders reduces the capability of the organization. Those costs are often born by customers. In the short term reducing costs in such a manner improves the financial statements. In the long run those cost reductions harm the companies ability to innovate, improve and delight customers.

  If instead we create a continual improvement capability and culture in the organization we will make improvements that in turn reduce costs (the Deming chain reaction).

  continue reading: Improving the System to Reduce Costs Isn’t The Same as Cost Cutting
• Using Deming’s Ideas When Your Organization Doesn’t

  First, you can transform yourself. You can transform your understanding and how you learn (with an appreciation for the theory of knowledge and what conclusions you can and cannot draw from the data you use). You can transform how you act.

  View your organization with an understanding of Deming’s management ideas. Think of the organization as a system. Even if you can’t persuade others to do this, you doing so will help you understand the situation more clearly and allow you to think of solutions that take advantage of this understanding. System thinking will allow you to find leverage points that can be used to multiply the benefits of improvements.

  continue reading: Using Deming’s Ideas When Your Organization Doesn’t
• Podcast: Building Organizational Capability

  From a podcast with me:

  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.

  continue reading: Podcast: Building Organizational Capability
• Google: Experiment Quickly and Often

  this is basically piloting changes on a small scale, analyzing the results and repeating that quickly. Quick, frequent experimentation with iteration is a tactic all organizations would benefit from.

  continue reading: Google: Experiment Quickly and Often
• Improving Management with Tools and Knowledge

  Both the tools and the underlying principles are catalysts to better management. Alone each can result in a bit of improvement. But when they are used together is when you see remarkable improvement. The effective integration of the principles and the tools is what separates the remarkable companies we respect (and maybe envy) from all the others that are having some success but that are also struggling in many ways.

  continue reading: Improving Management with Tools and Knowledge
• New Toyota CEO’s Views (2005)

  Toyota has grown in the past few years, but [there’s a risk] that a belief that the current status is satisfactory creeps into the minds of employees. That’s what I’m worried about.

  We should never be satisfied with the current status. In each division, function, or region, we still have numerous problems to cope with. We need to identify each one of those tasks or problems and fully recognize them and pursue the causes. This needs to be done by all the people working for Toyota.

  continue reading: New Toyota CEO’s Views (2005)
• Technological Innovation and Management

  Organizations need to be designed to be robust and to cope well with the increasingly rapid pace of transformative innovation. This again reinforces the importance of management improvement practices that I have been writing about here (on the Curious Cat Management Improvement blog) for more than 10 years. Organizations that do not delight customers, know the jobs to be done that their customers have, focus on the future (long term thinking), understand how to use data, have well designed processes that allow those at the gemba to know what to do and know how to rapidly adjust based on new realities and possibilities are at great risk.

  continue reading: Technological Innovation and Management
• Agile Software Development and Deming's Ideas

  It's one of the reasons for "people over process" and all that; they believe that a software developer should be respected. Yes, they should. Factory workers should be respected, too. Everyone should be respected. That's what Deming was talking about. So then the idea that Deming was trying to impose on software developers some rigid controls that they shouldn't be subject to is not so. And not only wasn't he doing that, he wasn't doing that to factory workers either.

  continue reading: Agile Software Development and Deming's Ideas
• Dangers of Forgetting the Proxy Nature of Data

  We use data to act as a proxy for some results of the system. Often people forget that the desired end result is not for the number to be improved but for the situation to be improved. We hope, if the measure improves the situation will have improved. But there are many reasons this may not be the case (one number improving at the expense of other parts of the system, the failure of the number to accurately serve as a proxy, distorting numbers, etc.).

  I find something I learned from Brian Joiner an excellent summary – which I remember as:

  Data (measuring a system) can be improved by

  1. distorting the system
  2. distorting the data or
  3. improving the system (which tends to be more difficult though likely what is desired)
     Brian Joiner’s book, 4th Generation Management is a great book for managers.

  continue reading: Dangers of Forgetting the Proxy Nature of Data