Home Book Store Toolstore Consulting Room Contact FAQs & Search About

FAQ Categories
Managing quality
Management systems
Manag't system standards
Identifying processes
Purpose and mission
Stakeholders
Policies
Key Performance Indicators
Critical success factors
Objectives
Measures
Targets
Process elements
Procedures
Maintaing quality systems
Measurement
System auditing
Customer complaints
Problem solving
Training

Procedures/FAQ 1 / FAQ 2 / FAQ 3 / FAQ 4 / FAQ 5 / FAQ 6 / FAQ 7

What's the difference between a procedure and a process?

A MANAGED PROCESS

A DOCUMENTED PROCEDURE

  • Purpose
  • Scope and Applicability
  • Definitions
  • Inputs
  • Activities
  • Outputs
  • Reference documents
The diagrams above show how a procedure differs from a process. In simple terms a process produces an output on demand and a procedure is a way in which one works to accomplish a task. A procedure will only produce an output if placed in the hands of a people having the competence, authority and resources to use it. A process includes the procedures and resources needed for people to execute the activities need to produce the required process outputs. Some other differences are in the table below
Procedures Processes
Procedures are driven by completion of the task Processes are driven by achievement of a desired outcome
Procedures are implemented Processes are operated
Procedures steps are completed by difference people in different departments with different objectives Process stages are completed by different people with the same objectives - departments do not matter
Procedures are discontinuous Processes flow to conclusion
Procedures focus on satisfying the rules Processes focus on satisfying the customer
Procedures define the sequence of steps to execute a task Processes combine activities and resources to achieve an objective
Procedures are driven by humans Processes are driven by physical forces some of which may be activated by humans
Procedures may be used to process information Information is processed by use of a procedure
Procedures exist they are static Processes behave they are dynamic
Procedures cause people to take actions and decisions Processes cause things to happen

Procedures

In its simplest form a procedure can be a sequence of steps that include preparation, conduct and completion of a task. Each step can be a sequence of activities and each activity a sequence of actions. Work instructions can be procedures if they prescribe a sequence of activities that are to be performed to complete a task and this is the crucial difference. The only objective a procedure achieves is to effectively convey the requirements for executing a task. On its own a procedure cannot execute the task so that it achieves an objective - this is the role of the process.

Processes

Processes produce results. They often (but not always) create a change of state. They can take inputs (e.g. material, information) and pass these through a sequence of stages during which the inputs are transformed or their status changed to emerge as an output with different characteristics. Hence processes act upon inputs and are dormant until the input is received. At each stage the transformation tasks may be procedural, but may also be mechanical, chemical etc. Inherent processes do not normally recognize departmental or functional boundaries (but are often hindered by them) nor the boundaries between customers and suppliers. Each process has an objective with both quantitative and qualitative measures of its outputs directly related to its objectives. The transformation or process stages are designed to ensure the combination of resources achieves the objectives - the desired outputs. Of course this means that the process has to receive the right inputs to deliver the desired outputs and that the correct resources are applied at the right stages, in the correct quantities and in the right manner It is true that a process can be illustrated as a sequence of steps just as a procedure is illustrated, but the similarity ends there.

It's the way we use them

The way we use the words procedure and process tells us something about how they differ. We tend to start and stop processes. We implement procedures and commence and complete them. We process information. We do not procedure information but we may employ a procedure to process information. We have plating processes and there may be plating procedures. In this context, the plating process comprises the resources, people, plant and machinery, and the plating procedure contains the instructions on how to plate material.

We have process interrupt but not procedure interrupt, because processes are perceived as continuous and run until physical intervention. In our bodies we have processes, not procedures. The reproductive process, the digestive process, the respiratory process, these processes are certainly continuous and stop only when an intervention takes place. They may require human intervention in which a surgeon may employ procedures to effect a repair. Procedures on the other hand are perceived as being discontinuous, having steps which can be paused with activities or actions picked up or put down at will.

Procedures usually relate to groups of activities with a given output where that output may not be complete until acted upon by someone else at a later stage in the process. Therefore, procedures are the actions taken by individuals in a process that may span across several functions and use multiple resources to deliver a predetermined output at a given rate at a given location on a given date.

For more information see ISO 9000 Quality systems Handbook

 

Active scripting needs to be enabled in IE to use the pull down menus
Last amended 26/08/2008
Home | Book store | Tool Store | Consulting Room | Contact

© Transition Support 2008