The Organizational Learning Goal at Ford’s EFHD

 

Electrical and Fuel Handling (EFHD), the smallest division at Ford Motor Company, employs about 7,000 people and does approximately $1.5 billion in sales annually. At EFHD, we manufacture starters, alternators, injectors, ignition coils — everything that sparks and gasses your car. Over the past five years, we have faced tremendous challenges in terms of our global competitiveness, some of which have to do with our unique relationship to Ford Motor Company. Even though EFHD is a division of Ford, the program managers at Ford are not obligated to purchase our parts — they are free to buy from our Japanese and German competitors. And yet, we are affected by Ford’s policies and practices in ways that make it difficult for us to compete against those foreign suppliers. For example, we need to invest in best-in-class technology and a high-powered engineering corps, but as part of the Ford 2000 restructuring program, we are expected to reduce our engineering resources.

We also need to stay cost competitive, but because of our union workforce, we have a high wage rate relative to our competitors.

Multiple Approaches

Culture: Provide a culture based on trust, honesty, and openness.

Awareness: Increase awareness of organizational learning by developing communications and media that are available to all employees.

Capacity Building: Provide resources and capacity to meet employees’ demands for learning courses, projects, facilitation, and documentation.

Involvement: Increase involvement of all employees in learning projects to create maximum performance in manufacturing operations, customer relations, and shared vision.

Community: Build relationships with other organizations and learn “state-of-the-art” methods and tools.

The Ford 2000 program has also pushed us to become global. In the last four years, we have launched plants in Northern Ireland and Hungary, and engineering centers in Michigan, England, Germany, and Japan. We are currently opening plants in Brazil and Mexico, and we have been given direction to launch plants in the Far East in the very near future. In order to meet these challenges, we know we need to operate in entirely new ways. That’s why, in 1992, we made the goal of becoming a learning organization part of our strategic initiative.

Knowledge vs. Understanding

Our organizational learning efforts have focused on enhancing our tactical knowledge with a better understanding of the larger systems. For example, we are very good at analyzing processes that are out of control; however, a process that’s completely in control might not necessarily be functioning optimally. So, in addition to working on root causes, we need to tackle common cause issues. And while we are analyzing, we also need to synthesize, to understand the interrelationships in the system. We need to augment our accounting methods and fishbone diagrams with hexagons and causal loops. And in addition to knowing how to discuss, we want to be able to dialogue. Through this synthesis of traditional methods with organizational learning tools, we hope to leverage our process knowledge with a level of systems understanding that can lead to quantum improvements.

Deployment: Five Areas

To embed the learning organization approach within EFHD, we have been working simultaneously in five areas: culture, awareness, capacity, involvement, and community (see “Multiple Approaches”).

Culture. In order to create a work environment in which people feel empowered to learn, we need to build a culture based on trust and openness so people can feel comfortable taking risks. We want to encourage people to share best practices and discourage competition between plants or product teams.

Awareness. Building awareness of our activities across teams includes communications methods such as e-mail, as well as documentation of our work and the lessons learned. It also involves internal facilitation. We have assembled a staff of seven people who facilitate team learning projects and communicate the learning initiatives across the division. These facilitators are supported by outside people, such as MIT researchers and faculty from our local Washtenaw Community College.

Capacity. In order to strengthen our internal capacity, we have developed a learning course in partnership with our local community college. In this intensive, week-long course, people from our Michigan and Indiana plants come together with employees from our overseas divisions to learn the basic theory and skills of the learning organization. They also work through concrete examples of how we have applied systems thinking and team learning at EFHD.

Involvement. All of the involvement in organizational learning at our division has been done through invitation, not by mandate. We believe that this type of change simply can’t be forced upon people. People who do want to get involved can do so through the learning organization course, through our Total Productive Maintenance workshops (which incorporate an organizational learning approach), or by participating in learning teams. Upper management is also involved in the efforts. Our top 16 executives took the MIT core competency course together, and they now participate in a weekly two-hour dialogue, in which they work on their own team issues and provide a leadership example for the whole division.

Community. As another focus of our work, we are striving to build a learning community by cultivating relationships inside Ford, with MIT Learning Center participants, and in the Washtenaw community. By nurturing these relationships, we feel we can maximize our learning from all opportunities, and also become good corporate citizens both inside and outside of Ford.

To implement these five objectives, we have concentrated on three activities: the introductory course, dialogue circles, and learning teams.

Introductory Course

For the past several years, we have conducted an introductory class with the local community college on systems thinking and organizational learning. In this course, participants learn the basic concepts of organizational learning and gain hands-on experience with tools such as systems archetypes and dialogue. The course is taught by a professor from the college, who provides the conceptual and theoretical framework, and an EFHD facilitator, who helps participants apply those tools to real business issues. Currently, we are running six courses per year in our Michigan facility, and we plan to host three courses in our overseas plant by the end of 1996.

Classes consist of about 50 people, and we try to balance attendance between hourly and salaried workers, and local and overseas employees. As part of our community-building efforts, we also invite spouses of Ford employees, as well as people from local universities, city government, the community college, and other companies. This gives us a diversity of perspectives, which we find invaluable.

Our Division Operating Committee also participates in each course by joining us for some of the group presentations around culture and visioning. They also take part in a dialogue so that attendees can experience a dialogue session conducted by people familiar with the process. Finally, they join us for the opening reception and participate in the celebration dinner and graduation ceremony.

Activities: Dialogue Circles

Strategic dialogue has become one of the most useful tools for team learning and effective problem-solving at EFHD. In part, this is because it provides an opportunity to think about issues and problems on a different level. As teams practice dialogue, they create an infrastructure for more open, honest communication.

Teams throughout the division use dialogue on an ongoing basis, and the practice is now becoming global. When the Division Operating Committee members visit overseas plants, they sit in a circle and talk for a day. No books. No reviews. No measurements. Just an open conversation about the issues facing the plant and how they might do things differently. When you have a plant located in a place like Belfast, Northern Ireland, there’s a lot going on besides producing parts. We believe the dialogue approach provides a broader perspective on the issues and helps us tackle them more effectively.

In the weekly dialogue, the Division Operating Committee’s one ground rule is that committee members don’t necessarily have to tackle specific problems, nor are they required to come out of the sessions with solutions. But they very often will talk about specific issues and come to a much better understanding of the problems, which leads to more effective solutions.

The fact that there are no “hard” measurements in a dialogue session does not mean that this process lacks hard results. Peter Senge once said, “You’re not a learning organization because you know how to dialogue. You’re a learning organization when you know how to turn dialogue into decision.” In our dialogues, there’s no such thing as taking notes or trying to transcribe the conversation. But, if we do hit an “aha,” we stop, have the team leader write down the insight or action item, and assign it to someone. Attaching accountability and responsibility to our processes is a key role in all of our learning organization work.

One of the best examples of the “hard” results that can come from this process emerged from a dialogue among members of the product launch success team. At one point in the dialogue an engineering manager asked, ‘Why is it that the machines always seem to work fine on Saturday?” The assumption behind his statement was that union workers are pleased when machines break down Monday through Friday, because they can get two hours’ overtime to fix them. If a machine breaks down on Friday, it’s even better, because the workers get all day Saturday to fix it. However, by 3:30 on Saturday afternoon they want to go home and spend the weekend with their families, so the machines don’t break down.

A UAW representative immediately took offense to the remark. “I’m sick of you guys implying that the UAW sabotages the machines. It’s my opinion the machines don’t work at EFHD because you have young engineers buying these machines, and all they do is buy crap.”

At that point, someone from purchasing joined in. “You know, I buy the same darn machines for seven other divisions at Ford, and they seem to work fine everywhere else. I think you guys have trouble with equipment because you have terrible Total Productive Maintenance procedures.”

This was not a pleasant exchange, but the surfacing of mental models and assumptions helped pave the way for honest communication and a more effective approach to the problems that were raised. In order to address the issue of machine breakdowns, the group developed an equipment specifications manual that covers all aspects of testing and installing new machinery. This manual has proven so effective that it is going to be the prototype for the whole company. When they looked into the supplier/purchasing issue further, the team discovered that some suppliers were, in fact, taking advantage of EFHD’s young engineers. They were selling us six or seven spare parts for machines when only one would break down in an entire lifetime. The team subsequently developed a consignment policy that required suppliers to keep the spare parts in their inventory. That step alone saved us hundreds of thousands of dollars in inventory costs.

Learning Teams

Most of the activities that take place around organizational learning at EFHD occur in “learning teams.” These are cross-functional groups of people who are applying organizational learning tools to their jobs and processes in order to become more effective. Learning teams are an important part of our organizational learning activities, because they provide an infrastructure for approaching problems from multiple perspectives. In fact, we have found that our most successful learning efforts are the ones that contain the most cross-functional diversity.

Most learning team projects follow a similar process. The teams begin by generating issues to be studied — usually during dialogue sessions or through the use of graphical facilitation techniques (such as hexagons). Then the teams use causal loop diagrams and system archetypes to look at the critical core issues that have surfaced. They also incorporate visioning and talk about their desired outcomes — for our processes, but also for the future of EFHD. Once they feel they have a good understanding of both the problem and the desired outcome, they go into action and figure out what tools will be most effective — TPM, value management, total cost management, kaizen, etc. Throughout this process, the team spends a lot of time in reflection, particularly through ongoing dialogue, which generates more issues and leads to more action. This becomes a continuous improvement loop.

The first learning team that we formed was the product launch success team. This seemed an appropriate place to start, since traditional business tools such as root-cause analysis had been inadequate for the type of process redesign we wanted. As part of our product launch project, any group that has completed a launch is required to share its experiences with people who are launching products in the current year. We’ve incorporated this practice into the process of “handing over the baton” in the last four years, and now any new product launch team has access to the lessons provided by program managers from 1992 through 1995.

We started the learning team concept in 1992. By the end of that year, we had two teams involving a total of 32 people. In 1993, the numbers jumped to seven teams, 120 people. In 1994, they hit 20 teams, about 500 people. We now have 32 teams and 1200 people involved in the team learning projects, totaling 20% of our workforce. Each team is organized around a particular goal or objective. The product launch teams, for example, continually work to improve our quality, cost, and timeliness on new products. We have 21 product teams that focus on removing costs from our products. Other teams include QOS (quality operating systems), scheduling, customer relations, capacity planning, and total productive maintenance.

Results

We feel that the results of our organizational learning work speak for themselves. Our earnings have increased significantly over the past four years. Our launch costs, timing, and technology have improved every year since 1992. Our quality metrics have increased by double-digit percentages, and we have saved millions of dollars in warranty costs. Last year we cut 50% out of our product launch budget. We have reduced our response time to material cost changes from 89 weeks to about 60 weeks, which has yielded significant savings. We now have full-service technology and design responsibility in house, and our product launches have become so smooth that it’s almost impossible to tell that we are going through them. Our division leads all the divisions of Ford Motor Company in its achievement of Total Productive Maintenance checkpoints.

On the people side, our surveys reveal that employees have noticed a positive change in our culture. They feel less stressed and more empowered than before. All of our management team — especially our general manager, who reports on our progress to the executive committee at Ford — is willing to say those results are associated with our organizational learning activities.

Next Steps

Our future plans are twofold: (1) deepening the level of understanding among people who are already involved in organizational learning projects; and (2) spreading the awareness of organizational learning more broadly throughout ER-ID. To deepen the learning, we’ve talked about designing an advanced course for people who want to gain more expertise in the organizational learning tools, and we are considering adding computer modeling to our approach.

As for increasing awareness throughout EFHD, we still have a long way to go in taking the organizational learning practices to our overseas plants. The challenge we face there is how we can learn together as a global organization when the people involved not only have different viewpoints, but also different cultures and worldviews. For example, in the U.S. we talk a lot about “fear of management.” But the people in our plant in Hungary — who have grown up under a communist regime — have pointed out that the American definition of fear is very different from theirs! Surfacing such mental models becomes even more of a challenge when you are speaking across different languages. We need to find ways to transcend the linguistic and cultural barriers that exist and make the concepts of organizational learning accessible to everyone.

Learning and Survival

The tremendous impact that organizational learning has had at EFHD over the last four years is apparent in both our improvement in metrics and the increased involvement and initiative of our employees. At one recent week-long program, an hourly worker said, “For years and years, not only the mental model but the reality at EFHD was that employees were used strictly for their physical abilities. It’s really a pleasure that now we’re being asked to use our minds.”

Five years ago, the Big Three auto manufacturers were convinced they did not need to have their component suppliers be part of their company. Chrysler got rid of most of theirs. GM has set up many of its component suppliers as subsidiaries. But EFHD still exists. The fact that we are in business today is probably the best proof I can offer that organizational learning really does work.

David Berdish is the process leadership manager at the Electrical and Fuel Handling Division of Ford Motor Company. He is responsible for organizational learning, Total Productive Maintenance, and value management. Editorial support for this article was provided by Colleen P. Lannon.

Reward and Recognition

In order to deeply embed organizational learning in our infrastructure, we have paid particular attention to our reward and recognition practices. One of the challenges we had to overcome was our tendency to reward results over improvement efforts. If product managers are promoted based solely on the success or failure of their launch, they will be less open to sharing their most successful strategies (for fear of losing their “competitive edge” over other managers) and less willing to share their failures (for fear of “looking bad”), both of which decrease the learning opportunities for the division as a whole.

To overcome this tendency, we have tried hard to reward commitment to organizational learning. In the last three years, the program managers that have been the most honest and most open with their learning — both in terms of things gone right and things gone wrong — have been promoted. In one of those cases, the launch was less successful in terms of the hard metrics, but the manager did a wonderful job of making sure that all current and future managers knew what went well and what didn’t. When these promotions were announced, the message was clear: these people were recognized not only for launching their products successfully, but also for supporting organizational learning throughout EFHD.

Learning is now seen as a critical metric for whether people exhibit the leadership styles necessary to be part of top management at EFHD.

Sign up or sign in to bookmark this article.