RE: Tasks vs. Procedures

["Steve Hudson" <steve -at- wright -dot- com -dot- au>]

What MAY be going on is a confusion between task and process.

A process is a higher level document than a procedure and generally speaking
it consists of a number of procedures. A process can interact with more than
one department and a number of roles - whereas procedures tend to be limited
in the roles that can perform them.

A process has defined inputs and outputs, but may not have rigid channels
for the datum to flow through. Thus, if a task can be said to be the
process, than yes, this is a higher level document than a procedure. Some
say, myself included, that a task is closer to a single set of work
instructions - whereas a process is a process is a process.

Steve Hudson
Principal Technical Writer
Wright Technologies (Aus)
steve -at- wright -dot- com -dot- au
(612) 9518-1822
The best way to predict the future... is to create it!



-----Original Message-----
From: Ellen Vanrenen

I am floundering in trying to define policies and procedures docs. I was
told a task differs from a procedure. Does anyone know in what way(s) it
does? I have looked into it and cannot find a difference.

I am sorry that my questions are so basic.


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

A landmark hotel, one of America's most beautiful cities, and 
three and a half days of immersion in the state of the art:
IPCC 01, Oct. 24-27 in Santa Fe.  http://ieeepcs.org/2001/

  +++  Miramo -- Database/XML publishing automation.  See us at  +++
  +++  Seybold SFO, Sept. 25-27, in the Adobe Partners Pavilion  +++
  +++ More info: http://www.axialinfo.com  http://www.miramo.com +++

---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit 
http://www.raycomm.com/techwhirl/ for more resources and info.