If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting!
I've been on two Toyota plant tours and visited another 20, or so, plants in Japan. The Georgetown, KY tour was great. The conversation with Gary Convis, President TMMC, was outstanding. Norman Bodek has been on hundreds of plant tours looking at lean. In his words, "I've never learned more on a tour than the one hour we spent with Gary." At the end of the Toyota tour I asked the executives and project coaches to share the lessons they were bringing back to the construction project setting. I went around the room giving each person the opportunity to offer a lesson. We did this two times. Here are their lessons in the order offered:
- The use of visual management was far more than expected. Will attempt to over communicate project key performance indicators and goals.
- Stopping to fix the problem — jidoka — could lead to far fewer quality problems.
- Executives have a role to play in project kaizen activities. Gary Convis, President of Georgetown operations, got involved in kaizens in a coaching capacity.
- Staff project roles with people with the appropriate skills and interests. Develop the basic skills for the work in construction.
- Use five whys at the time variances (problems) are identified.
- Encourage trade labor to change roles throughout the day. This avoids repetitive motion injuries, reduces boredom, and builds an appreciation for the conditions of completion for work.
- Clean as we go throughout the day. Assign accountability for workplace orderliness. Use indicators — andon — to signal that the work teams recognize that they are keeping their workspaces in a condition for others (and themselves) to proceed with work.
- Thinking that we already know — that we are the best — is the enemy of learning and becoming lean. We must overcome that.
- Celebrate success as it occurs. Celebrate the work of teams.
- A lean approach requires a different culture (from the usual AEC project).
- Don't hesitate to display banners, mottos, and team improvement projects across the project work site.
- Keep everyone informed everyday (throughout the day) of the key performance indicators for the project.
- See that the whole project organization — owner, architect, contractor, sub-consultants, and sub-contractors — are all using the same language of improvement.
- Training can begin at the earliest encounters with prospective employees. It can help us select the best people for our projects.
- Have the client involved at appropriate times throughout the project.
- Pay attention to the details. It can lead to higher quality and customer satisfaction.
- Evolve a lean approach on projects and throughout the organization. Start with a focus on quality. Follow that with improving production throughput. Finish by reducing costs.
- Use color charts, displays, and signaling to draw attention to anomalies and to what is important.
- Organize people into small teams — five people — with a working leader who can fill in for everyone else. Use multi-skilling to develop a response capability.
- The person performing the next operation is your customer. Make sure people know who will be working next in the workstream, especially when they work for another organization or company.
- We observed a simplicity in the language at Toyota. Find ways to communicate what is requested, standards of performance, and details so that they will be understood.
- Have a 15 minute stand-up meeting every morning with all the supervision to review progress and to pursue an improvement agenda. Finish the day with a similar meeting to provide the opportunity for supervision (last planners) to declare complete on the promised work for the day.
- Establish standard work — the currently understood best way — for key project operations.
I didn't have the opportunity to share my impressions with the group. Here are three key lessons:
- Work to a pace that both allows the team to meet the project goals and doesn't overburden them. Pacing reduces one source of variability while simplifying planning.
- Use improvement activities — project kaizen — as the principal means of engaging project team members in meaningful work that advances their careers.
- As leaders, involve yourself to ease the work of the project team members rather than operating in the illusion that you can control.
Norman Bodek made numerous comments. Here are three of the more memorable ones:
- As managers, adopt the approach of ask questions, don't tell.
- Small, very small improvements that don't require management approval will accelerate project performance. Norman calls it Quick and Easy kaizen. Using that approach Toyota got
4020 million adopted improvements in2040 years. That is more than 100 adopted improvements/person/year. - Teams are far more creative than individuals. Organize recurring team activities for sharing and improving upon individual creativity.
We'll do a Toyota Georgetown visit again. But before that I am taking another 18 lean construction leaders to NUMMI. That is where Gary Convis started out. I can't wait to listen to the lessons from that tour. I'll share them with you.
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=03314884-90d1-47e5-acf3-2821313e9fdc)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=4ce3f392-8989-448a-a97a-c1432dd3fce6)
{ 6 comments… read them below or add one }
what an awesome summary these folks made, Hal!! this is, in itself, a wonderful summary of Lean.
Importantly, these execs will learn more as they do it. They are fortunate to have you as a coach.
How impressive for Gary Convis to spend a valuable hour of his time with you…that speaks volumes by itself.
I agree with Joe. This is a wonderful summary and a wonderful demonstration by Gary Convis that executives are not “too important” to spend time helping others grow. That’s an example all leaders should follow.
Great article. It looks like your team came away with some valuable lessons from the benchmarking trip to TMMK.
I question the 40 million ideas in 20 years, 100 per person per year. That’s practically one every other day, per person. More likely 4 million ideas, working out to one per month per person, which is Toyota’s stated rate for their suggestion system. Impressive numbers, nonetheless.
Jon is right questioning my numbers. I got them backwards. Norman published a book on it 40 Years, 20 Million Ideas: The Toyota Suggestion System, Productivity Press.
Great post. One question I have — Toyota was influenced by Deming who said to get rid of the slogans and exhortations hanging on the walls. When I toured NUMMI, I saw a lot of that and you’re describing it at TMMK. I wonder if that the Toyota approach or an “American-ization” of the system, to use those slogans and such since they are so common (and so often mis-used) in U.S. factories. Any thoughts?
Most of the stuff hanging on the walls had to do with current team efforts for improving their work. There were a few large banners — Customer Service Awards — but few slogans. However, I don’t see a problem per se with slogans, in spite of Dr. Deming’s advice. I think the general worry is walking the talk. I don’t see a danger of that at Toyota.