RE: When users want jargon

["Rebecca Hopkins" <rhopkins -at- iconverse -dot- com>]

Anita,

Your problem goes beyond writing. You already know what you can do in the
manual to solve the problem of jargon - you need a political solution to
make sure the jargon doesn't get into the body of your text (index,
supplements - fine). Putting in non-standard jargon will hurt your chances
of make sales to people who use standard jargon, or English.

You might be able to handle this personnally with a few well-placed "I'm so
sorry, buts," you might need a manager with more clout, you might need the
president of your company, but you shouldn't let them get a foot in the
door. You'll be alienating your main audience - other potential customers.

Remember, they often scan the doc before they buy, and if they see a lot of
stuff they don't recognize, they'll look elsewhere.
-----
Rebecca Hopkins
iConverse.com


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Free copy of ARTS PDF Tools when you register for the PDF
Conference by May 15. Leading-Edge Practices for Enterprise
& Government, June 3-5, Bethesda,MD. www.PDFConference.com

Check out RoboDemo for tutorials! It makes creating full-motion software
demonstrations and other onscreen support materials easy and intuitive.
Need RoboHelp? Save $100 on RoboHelp Office in May with our mail-in rebate.
Go to http://www.ehelp.com/techwr-l
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit
http://www.raycomm.com/techwhirl/ for more resources and info.