The Coaching Manager -- Toyota Kata and Scientific Thinking

Just this month, Tilo Schwarz and Jeffrey K. Liker published a new book entitled Giving Wings to Her Team: A Novel About Learning to Coach the Toyota Kata Way, which presents a story about the benefits of becoming a coaching manager and how to get there. We follow the fictional character, named Denise, on a journey of discovery and skill development, as she moves beyond the tools and concepts of Lean and focuses on daily practice that helps her supervisors achieve their goals. It's about the Toyota Kata approach, which helps anyone develop and apply scientific thinking -- an exploratory mindset of curiosity and experimentation.

When I recently spoke with Tilo and Jeff, I had the chance to ask them some questions specific to the concepts discussed in their current book, and how those concepts apply to daily work.

Question 1: What are the benefits of becoming a coaching manager?

In general terms, a coach teaches, watches the student, gives appropriate feedback, and assigns drills to learn specific skills.  You can coach anyone on any skill.  In Giving Wings to Her Team, the central character Denise learns a specific type of coaching for a particular skill set -- scientific thinking.

We often think that to navigate today’s complex challenges we need decisive leaders with a clear roadmap that they rigorously implement.  In reality, the more complex the challenge the less a roadmap will be helpful.  Instead, we need adaptive problem-solving, testing ideas rapidly, and learning our way to goals.  In Toyota Kata, this way is called scientific thinking—focus on facts, formulate hypotheses, test ideas instead of making assumptions, reflect, and learn.

Toyota Kata teaches a coaching approach that enables your team to become increasingly adaptive, innovative, and resilient – fostering a culture of continuous learning and improvement, so your team can meet their current challenges and be ready for more.

Question 2: How does Toyota Kata help you to become a coaching manager?

The term “kata” is used in Japanese martial arts and are the small skills the black belt teaches and then the student practices repeatedly, with feedback, until doing it the right way becomes a habit. Michael Jordan put it nicely: “You can practice shooting eight hours a day, but if your technique is wrong, then all you become is very good at shooting the wrong way.” 

In the novel, Denise faces the biggest challenges of her life as a manufacturing manager and is fortunate to get coaching help from Maggie who runs the local gym.  Maggie has studied and used Toyota Kata in her gym.  She helps Denise learn to work with her team to set big challenges they can relate to, study the current condition, set short-term target conditions, and then experiment toward these targets.  Denise struggles at first, but through practice, and Maggie’s coaching, she gets better and better at giving wings to her team.  

You can learn along with Denise how to become a coach of scientific thinking and by coaching your team to achieve goals that at first seem impossible.  In this book, we go beyond laundry lists of coaching best practices and demonstrate how to develop actual skills in yourself and your team.  

We hope our novel will help you start a learning journey of your own.

What are your experiences with Toyota Kata? Have you applied it in your organization? How has it benefited your managers and teams? 

The ”Just Do It” Approach to Strategy Deployment Has Proven to “Just Not Work”

Randy Kesterson recently published a book titled The Basics of Hoshin Kanri, and it explains the basic steps to a strategy deployment and execution approach that has proven to be highly effective by companies such as Toyota, Danaher, and 3M.

The book includes interviews with many of the world’s leading Hoshin Kanri experts. For example, when asked to define Hoshin Kanri, Jeffrey Liker stated: “It’s a method for deciding the strategic direction from the top and then cascading that down to goals and objectives and then the means to achieve those goals and objectives.” Lisa Boisvert defined Hoshin Kanri as: "a strategic planning practice that defines a direction and priorities, aligns the organization around that direction through dialog and detailed plans, then implements and measures against those plans in a disciplined way.”

My direct question to Randy was: "What makes Hoshin Kanri a unique and useful strategic objective delivery system?" Here is Randy's complete answer:

What makes Hoshin Kanri unique can be summed up in two words … Catch Ball (which is an interactive process of tossing items and possibilities back and forth like a game of “catch.” It sometimes results in changes to proposed objectives, means and measures). 

Hoshin is unique in that it involves an unusual level of employee engagement in the strategy deployment process by means of the Catch Ball process, which is explained in the book. Hoshin Kanri and employee engagement enjoy a symbiotic/synergistic relationship. Hoshin Kanri requires employee engagement to be effective, and the effective use of Hoshin Kanri will dramatically improve employee engagement within an organization. 

What do you think of Randy's summation of Hoshin Kanri? Has Hoshin Kanri been applied in your organization? Feel free to discuss your results.

Toyota Benchmarked... Yet Again

There's a great article worth checking out over on the CNNMoney / Fortune site. It's one thing to see software companies adapting Lean methodologies, but it's quite another to see them transform their culture, and Menlo Innovations seems to be doing the latter. Jeffrey Liker confirms: "Any piece you see in Menlo you'll see somewhere else. What you won't find [elsewhere] is all the pieces working together…."

The article covers four techniques that contribute to Menlo's success -- Assigning bite-sized pieces of work, Keeping projects in plain sight, Observing the customer in action, and Training workers to stay flexible -- but, it's this last area that I found quite insightful, and CEO Rich Sheridan's explanation of "towers of knowledge." Because all programmers at the company work in pairs, no one employee becomes the sole "owner" and facilitator of a particular project. This keeps programmers available to delve into other areas as well making all projects team efforts.

What do you think of Menlo Innovations' work atmosphere and business techniques? Will it become a benchmark for its own industry? Do you know of any other software developers that are building this type of culture?

Redeveloping Product Development at Volvo

I came across this interesting article that provides a little insight into how Volvo developed one of its new trucks -- the Volvo FMX. According to Gunnar Eliasson (a market manager for Volvo Trucks), customer input and specific requirements are now influencing the design of Volvo's trucks in a much more direct fashion. As product lifecylces are much shorter due to increased competition, response to customer demands must be more immediate.

With the Volvo FMX, the development process included customers, drivers, sales staff, and marketing specialists and then prototypes were built and tested after input and "wish lists" were distilled. A very crucial point of the article is a quote from Jeffrey Liker (author of The Toyota Way) who noted that this new process is what separates Lean product development from traditional product development: "In Lean production, specialists work together freely across several departments and areas, all so as to be able to better meet customer demands. At the same time, this approach promotes constant learning about the production processes and understanding of how product development is conducted."

Do you know of any companies that include this type of input very early in the process? How has it affected lead times?

Most companies' major concern with this type of process is the dissemination of important "secrets" to competitors. The more various "outsiders" involved in the development process so thoroughly increases the potential for leaks. Eliasson, however, reveals that the priorities and outcomes have greatly changed: "The benefits of inviting customers into the product development process far outweigh the risk that information might spread to our competitors."