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: Ned Bedinger
> Sent: Saturday, 12 April 2008 3:17 PM
> To: Michael West
> Cc: kemulholland -at- yahoo -dot- com; techwr-l -at- lists -dot- techwr-l -dot- com
> Subject: Reading meanings into information (Was:: Replacing "master" and
"slave"
> terminology)
>
> Michael West wrote:
> >
>
> > ...there will always be people around who make it their
> > business to read into words and pictures "meanings" that have nothing to
do
> > with the matter at hand.
>
>
> Speaking of this, and I agree with you, I've seen a brief training
> demonstration of something like it, designed to illustrate the
> importance of careful listening and writing. [...]
And here's a real-life example. In this case, as in the exercise cited by
Ned, the audience was innocent of any hidden agenda. This isn't always the
case.
I recently gave the CFO and the GM a preview of a slideshow I prepared to
inform the company about a new business initiative.
In the slideshow I had some clip art of generic office-buildings that I
intended to represent the concept of "office".
Our GM has an engineering background, so to him the buildings were objects
of interest. He asked me questions about the buildings. The CFO, on the
other hand, who wasn't an engineer, took the drawings as I intended them --
just non-specific representations of buildings: any buildings, anywhere.
The slide show was a success, they told me. But as soon as I got back to my
desk, I ripped out the "building" clip art and replaced it with
non-representational figures. Extrapolating that 50-50 split across the
entire organization, the risk of confusion or distraction from the main
topic was just too great.
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-