Same format for WI (Work Instruction) and Procedures?

[AndyN]

It´s clear what Procedures should contain (what, when, who)
and format is Objective,Scope, responsibles,references, etc,

In the case of WI what is the format?
it is the same or just plain instructions, let´s say

e.j. For calibrating a device

1 take the device
2 clean it
3 Take the manometer....
etc

Excluding how the procedures begin with?
------------------------
Other 2 points
Will be recommended to include the Wi into the procedure document
thus avoiding to create a lot of WI´s?
is there an iso rule for this?
-----------------------------------
I have seen some WI but the file name is e.j. "Procedure for managing documents"
and they begin with Objective, scope,purposes,etc.
why that?
I suppose that the difference it´s its contents
Procedures= what, who ,when
WI=how to do it, with no other text
what is your point of view?
--------------------------



Hope somone can help me

Lot of thanks

Tvillan:
The advise you've had here is great, if you feel you must stay with that kind of structure. I believe that this level of formality is one of the reasons that no one likes the quality system documentation - because to use that format makes documentation into a bureacracy. There are threads recently posted which are asking for help to 'energize' people. I'd wager a large part of the problem is the 'heavyweight' formality of the documentation they were told to use. Most of these 'formal' documents started in heavily regulated/military style requirements and have been passed on through the 'ISO' world. You don't have to do it that way.......

Work instructions are best made as pictures with little or no words - for an example you only have to look how effective the emergency instructions are on a plane.(Yes. I know we hope we never have to use them........)

Procedures can be introduced 'This is the way we do.........XXXX'. If you are having to make long lists of definitions etc., then who are you writing them for? The people who do the job should help create the documentation. I have helped document systems using both formats and I have seen which style people prefer.

In the USA everyone talks about the 'KISS' principle - you can use this too.....

(I think it means Keep It Short and Sweet..............)

 

[Marc]

Tvillan:
The advise you've had here is great, if you feel you must stay with that kind of structure. I believe that this level of formality is one of the reasons that no one likes the quality system documentation....

Good point. I'm a flow chart proponent for system and departmental procedures. The best ones are linear with inputs and outputs on either side. They have a lot more details than when I first started using them in the late 1980's.

Work Instructions are another matter. I've seen lots of formats for work instructions. For some years now electronic pictures has made for some very nice formats with visuals

 

[BradM]

Tvillan:
The advise you've had here is great, if you feel you must stay with that kind of structure. I believe that this level of formality is one of the reasons that no one likes the quality system documentation - because to use that format makes documentation into a bureacracy. There are threads recently posted which are asking for help to 'energize' people. I'd wager a large part of the problem is the 'heavyweight' formality of the documentation they were told to use. Most of these 'formal' documents started in heavily regulated/military style requirements and have been passed on through the 'ISO' world. You don't have to do it that way.......

Andy, this is such a well-worded paragraph, I just wanted to repeat it again. The only thing that would have made it better is if I had stated it!

Let's pick Taco Bell. Is this organization not concerned with consistency and standardization? By all means. Observe their posters/ pictures on the wall inside the work area (sometimes not easy to see from the register; but look for them and you'll see them). They are simple, clear, and easy to follow. They are written for their workers to follow. Some just have pictures, some are diagrams, and a few are statements of sorts. All are simple, easy to follow and very clear. Then, management concerns themselves with training and supporting the policies.

Know thy audience.

 

[AndyN]

Why, Brad, thank you very much!

I'm a Taco Bell afficionado myself and use that analogy for documentation (or McDonald's) as part of related discussions when running a class! (and I have teenagers, so we have to 'do' Taco Bell sometimes!!)