¡Descarga Gemba walks de seguridad y más Monografías, Ensayos en PDF de Gestión de Calidad solo en Docsity! Ivan Carillo FOR AN EFFECTIVE GEMBA WALK 11 ESSENTIAL STEPS Ivan Carillo If you detect: → Lack of standard work instructions → Resistance to change among frontline workers → Failure to sustain continuous improvement efforts You should switch to a go-see management approach. Ivan Carillo Inform the team beforehand about the Gemba Walk and brief them properly about it. For example, you can do a brief meeting to discuss the purpose and benefits of Gemba Walks. Ivan Carillo THINGS TO DO: Give earlier notice to reduce anxiety Explain the purpose of the Gemba Walk Create an open environment for everyone Ivan Carillo THINGS TO AVOID: No support functions involved Make it a fault-finding mission Use it to evaluate team performance Ivan Carillo THINGS TO DO: Establish clear goals for the walk Create a list of concerns to address Identify focus areas for the walk ahead Ivan Carillo THINGS TO AVOID: Overlooking the activity schedule Wasting time on irrelevant matters Not utilizing tools for data collection and recording Ivan Carillo 3. FOLLOW THE VALUE STREAM Ivan Carillo THINGS TO AVOID: Ignoring some types of waste Overlooking transitions between workflows Only focusing on problem areas while ignoring the whole process. Ivan Carillo 4. ALWAYS FOCUS ON THE PROCESS, NOT PEOPLE Ivan Carillo Understand the process flow. Don’t judge people's performance. For instance, If you’re improving a data entry process, you can scout for improvements in the software rather than find employee faults. Ivan Carillo 5. DOCUMENT YOUR OBSERVATIONS Ivan Carillo Keep taking note of all details noticed during the walk. This way, you can point out the root cause of the problems and improve on them later. Ivan Carillo THINGS TO DO: Keep taking notes throughout the walk Document suggestions or ideas that arise Use visuals such as photos or sketches to capture details Ivan Carillo Ask specific questions to understand why the work is being done in a particular way. For example, you can ask why reports are generated manually when automation tools are available. Ivan Carillo THINGS TO DO: Inquire about workflow obstacles Prepare a list of open-ended questions Use the 5 Ws: Who, What, Where, When, and Why Ivan Carillo THINGS TO AVOID: Asking leading questions. Overlooking feedback from workers. Assuming processes are followed as documented. Ivan Carillo THINGS TO DO: Practice active listening. Reserve suggestions for later discussion. Process all information collected before proposing changes. Ivan Carillo THINGS TO AVOID: Jumping to conclusions. Making impulsive changes. Offering on-the-fly solutions. Ivan Carillo 8. WALK IN TEAMS Ivan Carillo THINGS TO AVOID: Conducting the walk alone. Intimidating the on-floor team members. Restricting team members from sharing their viewpoints. Ivan Carillo 9. MIX UP THE SCHEDULE Ivan Carillo Schedule the walks at different times to understand processes fully. When you break from the schedule, you can understand everything better. For example, you might usually conduct walks in the morning but can have one in the evening or afternoon to grasp any variations in the workflow. 10. FOLLOW-UP WITH
EMPLOYEES
y
Ivan Carillo
Ivan Carillo It means discussing the outcomes of the walk with employees, including any action plans. For example, you might schedule a meeting after the walk to discuss identified issues and potential solutions. Ivan Carillo THINGS TO DO: Acknowledge all contributions. Share the results of the walk with the team. Discuss potential action plans with all stakeholders. Ivan Carillo Keep conducting Gemba Walks with a regular cadence to promote a culture of continuous improvement. You can set the frequency regularly to ensure a smooth mechanism overall. Ivan Carillo THINGS TO DO: Schedule Gemba walks regularly. Constantly follow up on action plans. Review previous walks when planning. Ivan Carillo THINGS TO AVOID: Adopting a one-and-done mentality. Ignoring changes during subsequent walks. Ignoring lessons learned from previous walks. Document Your Observations: ↳ Note down every detail and insight during the walk. Ask Questions: ↳ Use open-ended queries to understand workflows better. Don’t Suggest Changes During the Walk: ↳ Save improvement ideas until after the walk is finished. Walk in Teams: ↳ Conduct the walk with other team members for diverse perspectives. Mix Up the Schedule: ↳ Hold walks at varied times to get a complete operational picture. Follow-up with Employees: ↳ Review the walk findings with the team and discuss action plans. Repeat the Process: ↳ Conduct Gemba walks regularly to ensure continuous improvement. I post daily tips for starting your continuous improvement journey. Stay tuned! REPOST THIS
