TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Alternatives to "tasks" From:Scott Havens <SHavens -at- ELCOTEL -dot- COM> Date:Wed, 20 Jan 1999 13:12:05 -0500
I think I'd make the internal ones "Burdens for the Indentured," and the
external ones "Deadweights for the Masses." Seriously, you might
consider something like "activities" to describe the tasks. It almost
makes them sound like fun. (Little do they know, heh heh.)
"Procedures" would be my second choice.
By the way, how many "braims" do you have?
SRH
> From: Ben Kovitz [SMTP:apteryx -at- CHISP -dot- NET]
> Subject: Alternatives to "tasks"
>
> I was just about to put together a user's manual that has some tasks
> for
> people inside the company and some tasks for people outside the
> company....
>
> Well, I sure don't want to call these things "internal tasks" and
> "external
> tasks", but I'd like to make a clear division between them in the
> manual.
...
> "Procedure" might do, but it seems that there ought to be something
> better.
> My braims are just not finding words today...
>
