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:Alternatives to "tasks" From:Ben Kovitz <apteryx -at- CHISP -dot- NET> Date:Wed, 20 Jan 1999 10:48:20 -0700
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.
The internal people also have some need to do the external tasks. I want
to divide the manual into two main sections, each named for the kind of
tasks that it's about.
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.
To replace "internal" and "external" I'll use the company's name and
"customer" (as an adjective). But "tasks". Ecch. Such a distasteful
word. We tech writers call them "tasks" when we speak of things like
"task-oriented organization." Sounds like some dreadful chore to try to
get out of. Does anyone have any suggestions for a better word?
Well, obviously those are even worse, except for "job". I don't want to
use "job", though, because it sounds more like the complete set of, um,
tasks that one was hired to do.
"Responsibility" is another option, but the external tasks mostly have to
do with placing orders, which I wouldn't call a "responsibility" (or a
"job").
"Procedure" might do, but it seems that there ought to be something better.
My braims are just not finding words today...
--
Ben Kovitz <apteryx -at- chisp -dot- net>
Boulder, Colorado