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.
> Scott asks:
> Any opinions on when it's ok. to use "you" in documentation?
Misti (ncr02!mdelaney -at- attmail -dot- com) replies:
> I use it whenever possible because i think, again, that it makes the
> document more readable. The reader is usually also the "doer" and it saves
> a mental step if the document makes that assumption.
I use it a lot in 'how to' material. The point is that there is a person
sitting in front of a keyboard with my manual on her lap. She should hear
a voice as she reads the page. In fact the whole thing works best when
I can picture the reader as I write, and they can hear me as they read.
I do avoid 'you' in introductory material. If I'm talking generally
about what the product can do, I prefer to make the product the subject
("COS/Manager can do.." rather than "You can use COS/Manager to...").
This isn't an iron rule; I just use 'you' less often in the introduction
and more often in the instructions.
Stuart Burnfield (slb -at- fs -dot- com -dot- au) Voice: +61 9 328 8288
Functional Software Fax: +61 9 328 8616
PO Box 192
Leederville, Western Australia, 6903