Article View: bit.listserv.quality
Article #263Re: TQM and Teams/G'house
From: L. H. Garlinghouse
Date: Tue, 19 Aug 1997 00:00
Date: Tue, 19 Aug 1997 00:00
53 lines
3377 bytes
3377 bytes
> Date: Sat, 16 Aug 1997 22:55:14 -0400 > Clint Pheeney posts: > the organisation where I work (15,000+ employees) is trying to introduce > teams into the work environment. One of the difficulties (amongst many) > I see is that the organisation is traditionally autocratic and > militaristic. There are major issues here for managers re controls and > accountabilities etc. My view is that teams work best in a 'quality' > environment, and to try to implement them in an organisation that is not > committed to quality is doomed to failure. > > In my experience teams are inextricably linked to quality. Whilst > quality in the workplace can exist without teams, I do not believe that > teams can operate successfully without a commitment by the organisation > to quality. I would be interested in peoples observations and/or > experiences on this issue. ============================= Quality, or its lack, is probably the least of your problems. The most important thing is the WHY of "doing teams." Doing it so managent can have some snappy buzz-words to drop at cocktail parties with other management types? Or is there some genuine interest on the part of management to actually change the way things are done? If teaming is going to be pursued seriously there needs to be some training of facilitators, and team members. If the Theory X culture is going to be maintained, then management needs to be aware that they have the responsibility to define boundries and limits and at least rough out mission statements for the teams as well as expect feed back as to team activities. They can't just say "Go and team! (And Oh! by the way, let us know when you solve something.)" Another problem is overloading teams with skills that the organization is not ready for. Don't train for SPC if there aren't going to be control charts. If I were to be given a carte blanche for a Quality program, I would probably start with teaming, and would not be concerned if initially Quality was not even part of the agenda. Once the skills and abilities are developed, they are useful for safety, environmental, ISO and even Quality - anything of importance to the business. There is probably cause for concern, but I don't see the lack of Quality as being of great significance. Eventually teaming will lead away from Theory X management, but it doesn't have to be the first step. Good luck and enjoy the show. << All opinions, statements, &c are my own>> L.H. Garlinghouse, C.Q.E. Pocahontas AR U.S.A. (870) 892-4586 ext 7659 garlinghou@waterlooindustries.com
Technical Details
Message-ID:
<1F926F54AC7@poca.waterlooindustries.com>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 1159be,e5b6e65375338096,start X-Google-Attributes: gid1159be,public From: "L. H. Garlinghouse" <garlinghou@waterlooindustries.com> Subject: Re: TQM and Teams/G'house Date: 1997/08/19 Message-ID: <1F926F54AC7@poca.waterlooindustries.com> X-Deja-AN: 265389254 Sender: TQM in Manufacturing and Service Industries Discussion List <QUALITY%PUCC.BITNET@vtbit.cc.vt.edu> Priority: normal Comments: ******************************************************** Approved-By: "Bill Casti, CQA (System Administrator)" <help@QUALITY.ORG> X-Received: from SpoolDir by WI-POCA (Mercury 1.30); 18 Aug 97 09:47:19 -0600 Organization: Waterloo Industries, Inc. Newsgroups: bit.listserv.quality