Interesting Discussion Procedure vs. Work Instruction (WI) - What is the difference?

[jadejes]

"a procedure is a document describing the processes of an organization.It is written with a general overview of what will be done and who will be responsible for making sure it is being done while a work instruction is a document describing a specific activity or task within the organization. It contains the greatest amount of detail."

 

[jadejes]

hi Mr. Collin,
i am just confused regarding procedures: general procedures or procedure manual, what do you think is the correct term or difference of the two? Is it possible that a company established a work instructions without the general procedure?For example, in a certain department, all documents established are work instructions without any general procedure?

 

[Xjopsong]

As a guide to differentiate the two, a procedure is inter-departmental while a WI is intra-departmental.

Huang

 

[vanputten]

I disagree that a procedure is always inter-departmental. The input to a procedure can come from within the same department.

Actually, I think the definition of procedure and work instruction has little to do with departments. They have a lot to do with work flow, value streams, etc.

Depending on what one means about "detail", a work instruction can have tremendous detail where as a procedure may not. A procedure may have more information than a work instruction but less detail. A work instrucution on how to set up a machine may have a lot of details.

I agree with Bill Goss. I am not sure if it is necessary to define these terms to a really specific degree. The key is to have the appropriate information at the necessary points of use.

 

[Colin]

hi Mr. Collin,
i am just confused regarding procedures: general procedures or procedure manual, what do you think is the correct term or difference of the two? Is it possible that a company established a work instructions without the general procedure?For example, in a certain department, all documents established are work instructions without any general procedure?

I think the only reason for referring to a 'procedure manual' is because companies put them together in a file or folder - don't worry about the name, it isn't important really.

Sure, you can have work instructions without documented procedures - you may have a competent person operating a machine so s/he doesn't need a documented procedure to do so but they may have instructions for setting the machine like temperatures, pressures, etc.

 

[Makeal]

This thread sure cleared the difference for me.

Well actually it filled my head with new questions, but that's life I guess

 

[AndyN]

This thread sure cleared the difference for me.

Well actually it filled my head with new questions, but that's life I guess

So, welcome, and please feel free to ask for answers!

 

[goodnede]

It is interesting to me that it was stated that you can have a work instruction with out a top level procedure for it. My management absolutely will not have that. If there is a WI on anything it has to be referenced in a procedure. The logic is how will someone know it is there if their procedure doesn't "point" them to it.

 

[Stijloor]

It is interesting to me that it was stated that you can have a work instruction with out a top level procedure for it. My management absolutely will not have that. If there is a WI on anything it has to be referenced in a procedure. The logic is how will someone know it is there if their procedure doesn't "point" them to it.

Folks who depend on a WI to perform their job, do not need access to a procedure. Your bosses get too wrapped up in old-fashion terminology. Documents do not need to be categorized, numbered, titled, or whatever. Call them John, Dick, and Harry if you wish. Just make sure that your folks have the latest version available to them and off they go.

Stijloor.

 

[Jim Wynne]

It is interesting to me that it was stated that you can have a work instruction with out a top level procedure for it. My management absolutely will not have that. If there is a WI on anything it has to be referenced in a procedure. The logic is how will someone know it is there if their procedure doesn't "point" them to it.

How do they know that there's a procedure?