May 30, 2005

Self-Managed Teams and Culture Shifts

The field of socio-technic systems work design emerged in England at the Tavistock Institute in the 1960s. Eric Trist and Fred Emery discovered that coal miners had developed an unusual work arrangement: they preferred to mine coal as a self-managed cross-functional team. Upper management tried to organize them into conventional structures of specialization and hierarchical supervision, but their productivity and morale plummeted. When they were allowed to work again as a team, they regained their very high output.

Trist and Emery thought there might be something in that work pattern that could be generalized and applied in other settings. Out of that investigation came the understanding that there is an intrinsic interdependence between the way work arrangements are structured and the way people feel and act toward the work and toward each other--that a change in the technical work system affects the social work system, and vice-versa. Looking for descriptive terminology for this they came up with "socio-technic systems." They developed ways to design new work arrangements, or to redesign old ones, guided by these discoveries. Most often--though not always--the redesign process led to self-managed teams that included all the skills and resources needed to complete a whole job from beginning to end.

The increases in productivity and work spirit in a range of organizations where this was implemented during the next two decades were astounding. In a world that was beginning to experience accelerated change, technological innovation, and globalized competition, these self-managed teams had a superior ability to adapt and innovate, and to move up any learning curve quickly. And they showed an amazing intrinsic motivation to do so. They didn't need a supervisor to tell them to improve the work--they had an interest in doing it themselves and did it quite well. In fact, supervisors tended to get in the way.

The emerging realization was that there is a fundamental clash of cultures between these two ways of structuring work. Emery distilled the difference in terms of a Design Principle I, referring to the conventionally vertical coordination of work through hierarchy, and a Design Principle II, referring to the horizontal coordination and self-regulation of self-managed teams. Part of the difference, too, was the shift from organizing departments according to function--marketing, fabrication, R&D, etc. (what we now refer to as silos), toward the inclusion in any team of all the skills required by the job--they were not only self-managed teams, they were cross-functional self-managed teams. The classic example is the redesign of the Volvo assembly line, so that instead of each individual attaching the same part to each car moving by on the assembly line, a team of assemblers traveled with the car from beginning to end, putting the whole thing together. At the end, they engraved all their names on the engine block.

But the shift from Design Principle I to II is not an easy one. It affects technology, organization, supervision, reward systems, assumptions, and interaction skills. Supervisors, especially, can be problematic because their role seems to become redundant. It takes considerable time, planning, training, and support to implement this shift successfully. At an oil extraction plant in Canada where I was part of the consulting team supporting this shift, the staff of the Utilities Division (that produced all the electricity, steam and processed water for the mine) was released from work for one week per month for six months to carry out the planning and training needed to make the shift (yes, temporary workers were hired during this time). At a Motorala cell-phone assembly plant in Florida, teams went through several phases of change, in which supervisors first became participative leaders, then coaches, then on-call consultants.

The tragic error among managers who learn about the benefits of teams is to implement them by memo--to decree the end-result structure while skipping the participative analysis of all work processes, the appropriate tailoring of the new work design to their core work situation, the necessary investment in training and support, and the time people need to integrate a fundamentally different work culture. In the end, the experiment therefore fails, and work structures revert to the old ways--problematic but familiar. And some managers breathe an unconscious sigh of relief--they are needed after all, and they don't have to change their old ways of managing.

Use the Comments link below to respond.
Enter you email in the box on the right margin to receive notification of new messages posted here.

Posted by eisen at May 30, 2005 02:56 PM
Comments

Thanks for the background, again. Yes, it sounds like they missed some of the transition points along the way as they attempted to implement SMWTs at Medtronic. I think we will need to take a few steps back toward education, support, and clarity of roles, before we can have this system truly add value.

I will be consulting with our operations directors to revamp the system. First step will be a plus delta on the current system from all levels including of course the operators, supervisors and support groups (engineering, equipment, HR, etc.).

I will keep th blog posted on progress and questions as they arise.

Posted by: Jessica at June 5, 2005 05:12 AM