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.
> I have been provided with a list of acceptable names to use in a
> training project that includes things like "Deadlines, Expects Many,"
> "Flare, Shiny Red" and "Paint, Many Colors."
> As an alternative, I presented a list of names like "Sarah Bellum,"
> "Les Payne," and "Jean Poole" (it's a medical application) and most
> people liked it. But there is an objection that if it could possibly
> be a name of someone anywhere that it can't be used.
> Someone pointed out that if Beyonce can name her daughter "Blue Ivy"
> that nothing can be ruled out for a name. But some are still fearful
> of consequences.
> I feel the users will be distracted by these names.
I agree that users are likely to be distracted by any name that tries to be too cute in its artificiality.
And I agree that nearly anything is fair game for a given name these days.
So I think my approach would be to use given names that are as common as possible and surnames that are obviously not real but are not trying to convey a message (whether overtly cute or subliminal) or make a pun. I might use names like
Frank Flattery (well, maybe just one or two puns...)
and so on
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.