Article View: bit.listserv.quality
Article #266Re: TQM and Teams
From: Gregg Jacobsen
Date: Tue, 19 Aug 1997 00:00
Date: Tue, 19 Aug 1997 00:00
44 lines
3010 bytes
3010 bytes
Based on the discussion Mr. Pheeney generated, I was reminded of an approach I came up with to help harness the wayward tendencies of teams in medium to large firms. Mr. Pheeney is right to be concerned that implementing TQM and/or teams in a quality-hostile environment is probably a doomed effort, but this method can put the senior managers in the position of either standing up for process improvement teams or... go back to their caves. The basis for this includes a presumption that there needs to be some nominal establishment of a formal quality assurance program, like ISO9001 or 9002. The construct implied in MIL-STD-1520C of Quality Improvement Projects (QIPs) was the seminal spark for this idea. First, you have an executive-level group (the erstwhile Corrective Action Board?) that reviews the health of the business (from a quality and nonconformance perspective) and charters a QIP team to "go after that problem or opportunity to improve." Thus, the teams have top-level awareness and sponsorship that mid-level management is inclined to "salute." Then, as internal audits, factory floor and incoming inspection rejects, test failures, customer complaints, et cetera, are evaluated for the need to initiate corrective/preventive action, those found "worthy" are elevated to the Board. Either the "new" problem is assigned to a team already working with the culpable process owner, or a new team must be chartered. The idea is simple: don't just rush out and train everybody and turn them loose (some call it empowerment, I call it setting them adrift sans paddle). Define clear teams and tasks, as justified by virtue of the seriousness (cost and customer impact) of the problem. I had a busy little flowchart with a lot more detail to the process, but I trust you get the idea. In a company of 15,000 heads, launching a TQM or teams initiative without this kind of structure is like pumping an aphrodesiac into the water coolers. It may sound like fun when proposed, but the consequences, well... Hope this helps, Gregg Jacobsen <grewjac@ix.netcom.com> Quality Management Consultant www.netcom.com/~grewjac/consult.html _____________________________________________________________________ Sent by RocketMail. Get your free e-mail at http://www.rocketmail.com
Technical Details
Message-ID:
<19970819220302.14369.rocketmail@send1.rocketmail.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,ae4f794cc4dd0b27,start X-Google-Attributes: gid1159be,public From: Gregg Jacobsen <grewjac@rocketmail.com> Subject: Re: TQM and Teams Date: 1997/08/19 Message-ID: <19970819220302.14369.rocketmail@send1.rocketmail.com> X-Deja-AN: 265475152 Sender: TQM in Manufacturing and Service Industries Discussion List <QUALITY%PUCC.BITNET@vtbit.cc.vt.edu> Comments: ******************************************************** X-Received: from [144.166.176.176] by attach1; Tue, 19 Aug 1997 15:03:02 PDT Approved-By: "Bill Casti, CQA (System Administrator)" <help@QUALITY.ORG> Newsgroups: bit.listserv.quality