Saturday, December 12, 2009

Selling OD by Doing OD

Getting top management support for OD efforts in an organization is absolutely crucial. Because OD works on whole organizations, significant change needs to be understood and fully supported by senior management. Sometimes we learn this the hard way: I know of a very successful plant redesign project that used the conference-based model developed by Dick and Emily Axelrod. It was highly participative, with large cross-section groups from all plant functions meeting for three days at a time, integrating the outcomes of the session, then meeting again for three days--five cycles of conferences. The focus for each one was built on the outcomes of the previous one. They worked on generating a shared vision for a better, more effective way to operate, followed by an analysis of the plant's technical production system, then an analysis of the social system, then a redesign of key aspect of the plant to optimize both technical and social system goals, and finally an implementation planning conference.

This all worked very successfully and generated creative new approaches for organizing the work and also great enthusiasm for implementing the changes. And then they hit a catastrophic glitch: The internal consultants and plant manager had made an early decision to not include a key vice-president in planning the project. He had a reputation of not supporting participative work methods, so they thought they would demonstrate the success of the project to him after it was completed and thus get his approval. Instead, the VP walked in on the implementation planning session, having missed all the previous ones, and was outraged. He declared the new design totally inappropriate: "This is communism--we're not doing it." And that was that. The whole project was canceled and everyone went back to the old way of doing things, though with great disappointment and frustration.

So what should one do when the needed support at the top is not there? For one thing, it depends on the role of the OD practitioner. External OD consultants learn to focus on the clients who are genuinely interested and ready to work in this different way. Rather than convincing or "selling" managers that this would be good for their organizations, the strategy is to work only with those organizations that have a demonstrated readiness, understanding and interest in an OD project. Since these projects are much more likely to succeed, they will create the track record of effective change projects, and word of these successes will quickly get around to other organizations that were almost ready, often leading them to consider the OD approach themselves. I learned this perspective from Herb Shepard, who was my mentor at Case Institute of Technology, and one of the founders of OD. One of his rules of thumb for change agents was "Never work uphill."

But what about internal OD consultants or managers who see the potential for OD in their organization, but don't have the support of higher managers? Shepard also said, "Start where the system is." He meant by this that one must assess the situation and propose projects that the organization and its leaders understand as relevant and appropriate. These may be less ambitious than the consultant can envision, but they are much more likely to be accepted and to succeed--thus laying the foundation for more comprehensive projects. This way of working requires great patience, and great empathy. One must see the world through the managers' eyes, and design and propose projects that are relevant to their current view of the organization.

This is a tough discipline and requires patience, self-acceptance, and a focus on the long view--even if that key manager is being driven by this quarter's business numbers. Shepard also used to say, "Think globally and act locally." The corollary of that statement might be, "Think about the future and act in the present."

I invite further comments and questions.

No comments: