Ambika,
Some inputs for WI development.
1. The purpose of WI: A person who does not know the job should be able to read and understand the WI and perform the job (like we use Windows Help or the instruction manual of a new gadget). So the language should be very simple.
2. The activities should be sequenced in the way they are to be performed. If there is a set of activities to be performed at startup/shutdown, but not to be repeated, these should be categorized separately in the same WI or made into a separate startup or shutdown WI.
3. After the activity description, add a separate column for the key points (pertaining to quality or operation) of that operation, if relevant.
4. Any safety instructions while performing the operation or PPE to be worn should be mentioned in the WI.
5. Illustrate the operations with a photograph, at least where relevant. For example, if the activity is "release the emergency stop button by rotating clockwise," you can show a photo of the emergency stop button on the panel so that even a new person can locate it on the panel and perform the operation.
6. WIs are required in the language that the person performing the job understands. So, if your operator understands only a regional language, then the WI has to be in that particular regional language.
7. After developing the WI, go to the concerned section and try to perform the operation by reading the WI. If not possible, observe a skilled operator and match their activities to the ones written in the WI. This will help spot errors or fine-tune the WI.
Regards,
Biju