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.
Priorities (was RE: Yahoo has no staff tech writers)
Subject:Priorities (was RE: Yahoo has no staff tech writers) From:"Dick Margulis " <margulis -at- mail -dot- fiam -dot- net> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 11 Oct 2002 10:48:20 -0400
John Posada <JPosada -at- book -dot- com> wrote:
I simply said
>that when it comes to priorities, I place them in the that order.
>
>If I only have time for one of the priorities, #1 comes first...if time for
>two of them, then 1 and 2 come first....etc. If I have time to get to 6,
>then I try to follow the rules as much as I can, but not at the expense of
>the ones preceding.
>
>
John,
Forgive me for taking the above quote out of its intended context, but it brings up an interesting question.
It is a common--maybe standard--practice to sort a list of needs/tasks/bugs/whatever into A, B, and C priorities, and then to say, "We'll do the A list first; then, if we have time, we'll do the B list; then, if we have time, we'll do the C list."
I have some trouble with that approach, and I think this may be what's bothering Bonnie, too (I'm not speaking for her, however).
Let's take the example of software development. If adding new features is always an A item and fixing what is already in the product is always a B item, and improving usability is always a C item, you end up with MS Word. Unfortunately, that model only works if you have as much clout in the market as Microsoft has. For the rest of the world, that's a formula for failure.
The issue is that nobody ever gets to the C items using your approach.
What I try to do instead, given the same priority list, is to devote some small quantity of resources to the C items, more to the B items, and the largest amount to the A items, but to do all three simultaneously (that's the key difference). That way, the priorities are still in order, but the C list stays a manageable length.
If grammatical flaws are on your C list, that's entirely appropriate. But if there are enough of them, the overall perception of quality will suffer and customer confidence in the accuracy of your content will fall off.
My two cents.
Dick
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
All-new RoboHelp X3 is now shipping! Get single sourcing, print-quality
documentation, conditional text and much more, in the most monumental
release ever. Save $100! Order online at http://www.ehelp.com/techwr-l
Buy ComponentOne Doc-To-Help 6.0, the most powerful SINGLE SOURCE HELP
AUTHORING TOOL for MS Word. SAVE $100 on the full version and $50 on the
upgrade. Offer ends 10/31/2002 (code: DTH102250). http://www.componentone.com/d2hlist1002
---
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.