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: Bullets, numbers, ego conflicts From:"Teri A. Ward" <taw0200 -at- eeidf002 -dot- ca -dot- boeing -dot- com> To:techwr-l -at- lists -dot- raycomm -dot- com Date:Thu, 27 Apr 2000 13:33:03 -0700 (PDT)
A possible compromise is:
a. One thing
b. Another thing
c. Something else
Although the letters may *suggest* a sequence, I
don't come across "step a" too often. Letters
also make it easier to refer to individual
items when there is a fairly long list.
My two pesos worth.
Tammie Ward
Technical Writer/Web Designer
Seattle
______________snip_________________________
> I had a job in a strife-filled office a few years ago, and this question of
> bullets vs. numbers came up there. We had documents with as many as 20 or
> more bullet items on a page in some cases. These were not sequential like a
> series of steps; they were suggested features or potential risks.
>
> In review meetings, I would have a question on, say, bullet 17, and everyone
> around the table would count down the list with their pen tips (the smart
> ones didn't move their lips *G*)
>
> I suggested that we number the line items, and the idea was shot down
> because assigning numbers suggested ranking and setting priorities. Sigh.
> That was when I realized that every line item in the document was the result
> of clashing personalities and differing approaches to the problem. The
> documentation suffered because it accurately reflected the divisiveness and
> conflicts festering among the writers and editors.
>
> I left that job, and as far as I know, that company never did succeed with
> the project the documentation covered.
>