Procedures Versus Processes

Procedures and processes are integral parts of any documentation project.

In their simplest forms, procedures tell us how to do something and processes tell us how something is done.

A procedure is born of a task, and as a result, contains steps to achieve a desired result. It can be complex, containing many steps, or simple, containing only a few steps. A process defines the movement of, for example, information from one point to another, during which time a change is effected; hence, there is typically an input and an output in a process.

A procedure is static, as opposed to a process, which is dynamic, as it creates change. One can think of a procedure as being discontinuous, that is, the steps may be stopped and restarted at another time. A process is continuous, in the sense that it does not pause unless instructed to do so by human interaction or some other means.

Procedural steps may be completed by various people in different areas of a company. Note that each person may use the procedure to achieve a different objective; therefore, a procedure ensures that tasks are completed in a consistent manner no matter who is performing the task. On the other hand, a process tends to be completed by different people with the same objective; the department in which each individual works is not important.

Oftentimes procedures are mistaken for instructions. Instructions can be categorized as procedures only when they are carried out sequentially and are used to achieve a desired result.