Taking a team-based approach

Getting procedures right


The same procedure was used for information requested from the employee--they were asked to provide details of what information they were usually tardy in presenting to other departments.

The total exercise was completed two weeks past the projected three-week time frame, but we honestly never expected to get through it so quickly.

Milestone 1

After all the information was gathered, the materials manager was responsible for writing up all the "requirements" (as they were now called) on a flip chart, as illustrated in Figure B.

Planning meetings

An all-day Saturday meeting was called that involved all the players that were part of the exercise. Besides Sunday, this was the only day we could get a full six-hour commitment from busy business unit managers and sales staff.

We taped the flip charts on the walls, and teams filled in causes and effects using codes, as shown in Figure C.

Getting answers

The blue type in the cells in Figure B illustrates the typical answers for each column. Teams rotated, so that one team would fill in the causes for one group of problems and another would fill in the effects.

After the day was over, everyone felt a sense of accomplishment; employees were able to acknowledge weaknesses in the systems that they had followed for years. This way, they were pointing out problems, and we hoped they would embrace the changes more easily because they would be aware of the possible benefits. One of the mistakes many firms make is not involving the users in the preparation for change.

Stay tuned for the second part of this series, in which I’ll explain how we evaluated potential solutions and ultimately chose a new product.

Figure B

Cause Effect Findings Solutions
    (a) Suppliers
 
EX
OE
Not sticking to promised delivery date
EX
    No communication on change of delivery date
 
    Slow response to request for information
 
    Invoices not received on time
 
    Company still communicating via faxes
 
    (b) Product Manager/Salesmen
 
    Missing information on foreign requisition form
 
    Duplication of work by product managers and purchasing department
 
MA
OE
Placing verbal orders with suppliers
TE
    Setting unrealistic delivery dates
 
TE
DU
Duplication in order follow-ups
TE
    Lack of communication re. Setting realistic delivery dates, changes, and updates on products, etc.
 
LA
$C
Not updating purchasing department on revised information for purchase orders
TE; BPR
    (c) Freight Forwarders
 
    Lack of communication on goods received in their warehouse
 

.
Figure C


Key
Causes
Effect
CO - Control (lack of)  
DE - Deficiencies
CU - Customer satisfaction
DU - Duplication
EX - External
LA - lack of timely information
IC - Internal customers
OE - Operations efficiency
MA - Manual
MI - Management inefficiencies
PA - Superfluous paper
SE - Security
PE - Personnel
SP - Space
UR - Untimely reporting
UU - Under utilization
TE - Technology
TR - Training
$C - Cost to company
$F - No cash flow management
CC - Communication (lack of)
 
LI - Lack of information
DI - Data integrity

Advertisement

Talkback 0 comments

Latest Videos

Sponsored content

Power Centre - Content from our premier sponsors

Blogs

  • Phil Dobbie A guide to the future of the internet
    Last week we looked at the history of the internet in Australia. It's been around for 20 years and changed our lives in so many ways. Imagine what it could do given another 20 years.
  • Array Carelessness busts Linux security
    No operating system can ever properly protect a computer from trojans as long as users continue to do silly things. Just because Linux is immune to your standard drive-by viruses it does not mean that it can escape trojan horses.
  • Array Sun shining on Ajnaware
    Graham Dawson talks about the future of iPhone app development and augmented reality.
  • More blogs »

Tags

Back to top

Featured