Office Lean Overview
•
1 like•726 views
This document discusses various Lean concepts and tools including 5S, visual controls, Kaizen, value stream mapping, pull vs push scheduling, mistake proofing, changeover time, Six Sigma, activity-based costing, Theory of Constraints, ergonomics, and knowledge management. It also briefly discusses costs of accidents and conducting effective meetings.
![OUTLINE ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
More Related Content
What's hot
What's hot (19)
Viewers also liked
Similar to Office Lean Overview
Similar to Office Lean Overview (20)
More from ahmad bassiouny
More from ahmad bassiouny (20)
Recently uploaded
Recently uploaded (20)
Office Lean Overview
Editor's Notes
- There are many more examples of waste. Can you think of some?
- It is good at this point to emphasize the notion that JIT is a philosophy not simply delivery of small lots at specific times. It is also helpful to emphasize that JIT requires an ongoing effort.
- Mistake-proofing is the use of process or design features to prevent errors or their negative impact. Mistake-proofing is also known as poka-yoke, which is Japanese slang for avoiding inadvertent errors. It was formalized by Shigeo Shingo, whose picture is up here in the corner, and comes out of the Toyota product system. I understand that there is a long way between the Toyota product system and medical operations, but I think there are also some worthwhile similarities. Mistake-proofing is inexpensive. Mistake-proofing is very effective for manufacturers that are aware of it. Not all manufacturers are aware of it. It is also based on simplicity and ingenuity. But let me be clear that simplicity, in its true sense, is rarely an easy thing to accomplish. Finally, mistake-proofing is something you probably already have in isolated instances in your organization. So, as you look around you will find examples.