Implementing effective Work Instructions

Have you ever bought a bicycle for a child? Comes in a box and the kid stands impatiently waiting for assembly. Inside the box are parts and 50 page manual written in 50 languages. Looks simple enough. Maybe you can assemble it without reading the instructions. Execute and find that you forgot the sprocket tie downs or now you have to take the back wheel of to install the chain. 

Or maybe you’re the other type of person who, in fact, reads the work instructions only to find that a step was missed or that the illustrations are so confusing – no one could understand. 

One of the most important characteristics of great leadership is the ability to communicate. Thus, organization that communicate well have serious strategic advantage over the competition. 

 

Implementing effective Work Instructions

By Eric Roberts

Written work instructions

You should be proud. Your team did a great job doing a value stream map. Not a single step was missed. The result, a 30 page document that no one will ever take the time to read. 

Reality is, that written work instructions are more of an instrument for disciplinary action than actually making a process easier to understand. 

Telling a new employee to read thirty pages, have them sign off on a sheet indicating they did – then expecting them to effectively run an operation is LUNACY. Regrettably, this is a standard practice every day. 

 

TIMES HAVE CHANGED – NEW THINKING FOR WORK INSTRUCTIONS

It’s time to start making work instructions that align with today’s culture. Today, your next generation work force goes to YOUTUBE and other forms of media to watch a video on topics of interest. 

Now is the time to capitalize on that very media to make effective work instructions. Lose the paper and build the video library. Leaders will find immeasurable productive benefits. 

 

 

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes:

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>