Hi Ravi. Information Mapping makes a very clear distinction between process and
procedure:
A process is a series of stages or phases that describe a series of events or
how something happens. The language used is typically descriptive: "The manager
signs off the invoice.". Processes are usually documented at a fairly high
level.to illustrate to the reader the overall flow of events. A process can be
described verbally or in some sort of diagram showing the relationship between
stages.
A procedure is a series of steps that tell the reader what to do to complete a
specific task. The language is typically instructive: "Sign off the invoice."
Procedures are usually a the most basic instructional level required to ensure
that the reader is told exactly what to do to complete the task. A procedure
can be described verbally or in a flow chart that shows the relationship
between the steps. You could say that a work instruction was one step out of a
procedure (depending on how you define the scope of the work instruction).
Steve
On 28 September 2020 at 12:13 FreeLists Mailing List Manager
<ecartis@xxxxxxxxxxxxx mailto:ecartis@xxxxxxxxxxxxx ;> wrote:
austechwriter Digest Sun, 27 Sep 2020 Volume: 18 Issue: 070
In This Issue:
Process versus Procedure
----------------------------------------------------------------------
From: Ravi Warrier <warrier.ravi@xxxxxxxxx mailto:warrier.ravi@xxxxxxxxx ;>
Date: Mon, 28 Sep 2020 09:12:13 +1000
Subject: Process versus Procedure
I am having some difficulty clearly separating the scope of a technical
writer from that of a process analyst.
I've tried 'what' versus 'how', but it looks as if one can apply this
distinction at any two levels between 'Run the business' and 'Enter the
date and click OK'.
Any advice on a practical way to draw a border between a process, a
procedure - and, for that matter, a work instruction?
Regards, Ravi
Dr Ravi Warrier
Mobile: 0420 641 188
------------------------------
End of austechwriter Digest V18 #70
***********************************
