For example: Operation A makes a mistake, doesn't catch it when it happened, and sends the work to Operation B. Operation B looks over the incoming work, doesn't catch the error, proceeds correctly with its operation and sends the work to Operation C. Operation C looks over the incoming work and catches the error made by operation A and passed on by Operation B. Operation C sends the work back to B, and now B (to its chagrin) must correct the error. Operation B is not allowed to send the error back to the originator, operation A.
The purpose? To ensure that people thoroughly check incoming work. In this case, you can bet that Operation B will be checking what it gets from Operation A very closely in the future. You can also bet that this model ensures that all downstream operations are very careful about what they accept from any upstream operation.
In case you were wondering, if Operation B doesn't have the know-how or equipment to fix Operation A's error in the example above, Operation A will fix the error. But the cost of the repair will then be charged to Operation B!
About Pelleyblog: We are striving to be a communication device for managers where many people can share their thoughts, ideas, opinions, perspectives and points-of-view. We focus on topics of interest to supervisors, group leaders, foremen, department managers, project managers, team leaders, assistant managers, associate managers, office managers, nurse managers, crew leaders, unit managers, and other first-line managers. But managers at all levels, and people interested in management topics are welcome and are encouraged to join us both as readers and participants.
Copyright © 2009 Daniel W. Pelley
All rights reserved.
All rights reserved.
No comments:
Post a Comment