Procedure vs. Task vs. Flow

["Papa, Amy" <PapaA -at- COMCELL -dot- COM>]

Greetings.

I have been working to set up a policies and procedures writing format
for my department.  I already have people writing procedures and
documenting workflow using templates and standard format.

I just received a reference book that I ordered on writing P & P (wanted
the reference primarily for writing policy, not procedure).  Lo and
behold, the book says something different than what I have already
implemented for writing procedures. The book says that *Procedures*
always involve 2 or more people, and that *Tasks* are the set of
instructions that one person follows to complete a procedure step.

I have set up a system where procedures for more than one functional
group are *Workflow* documents written in playscript format.  I have
called individual sets of instructions *Procedures*, not tasks if they
are for people within the same functional group (e.g.  "Help Desk
personnel procedure for doing such-and-such").

Does anyone have some thoughts on whether using "Workflow" and
"Procedures" is still fundamentally correct?


Amy Papa
Comcast Cellular Communications, Inc.
Technical Writer;  MIS Department
papaa -at- comcell -dot- com
610.995.5405
Amy Papa
Technical Writer
MIS Department
610.995.5405


   If it's about technical communication--post it! If not, don't!
Posts: mailto:techwr-l -at- listserv -dot- okstate -dot- edu
Commands: mailto:listserv -at- listserv -dot- okstate -dot- edu (e.g. SIGNOFF TECHWR-L)
Archives: http://listserv.okstate.edu/archives/techwr-l.html,
	http://www.documentation.com/, or http://www.dejanews.com/
Subjects: JOB:, QUESTION:, SUMMARY:, ANNOUNCE:, or none of these.