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.
> -----Original Message-----
> From: Tony Chung
> Hey Cindy,
> Your client needs to lighten up. Apart from that, here is some
> justification you can use for actual people names: It makes the
> and situations more realistic.
> Rather than grabbing names out of thin air, why not think of the
> or circumstances the person is in at that moment? At work we talk about
> some of our personas as being "frustrated", "contented", "efficient",
> "newcomer", etc. So when describing a high-intensity transaction
> the frustrated user, we refer to him as "Fred Frustrated". Likewise the
> contented user, in a more easygoing transaction, would be "Cindy
> The alliteration is a mnemonic, and the attitude is a characteristic of
> interaction. Realistic names help to build attachment to the idea.
> Hope this helps.
If you start your scenario or set of steps with Fred Frustrated,
a) need to undergo a sex-change before the sequence completes successfully, or
b) need to change his name before the sequence completes successfully, or
c) never actually get to success/accomplishment (like that arrow that Zeno postulated,
or maybe that poor Achilles, looking ahead at the turtle he'd never catch ... 1/2, 1/4, 1/8, 1/16) ?
One would think that to depict your product or processes in the
best light, you'd want the user to go through the sequence with
name and primary sexual characteristics unmolested, yet with a
reasonable hope of success at the end.
Why do you ask? :-)
The information contained in this electronic mail transmission
may be privileged and confidential, and therefore, protected
from disclosure. If you have received this communication in
error, please notify us immediately by replying to this
message and deleting it from your computer without copying
or disclosing it.
Create and publish documentation through multiple channels with Doc-To-Help. Choose your authoring formats and get any output you may need.
Try Doc-To-Help, now with MS SharePoint integration, free for 30-days.