I have subject matter experts (SMEs) who insist on talking and writing in "geek speak." It's fine for an audience of peers, but when you're creating user documentation or proposals, you need to make sure that your audience understands the language and gets the message. You also need to be aware of the audience. I read a study recently about how the Baby Boomers, Generation X, Gen XY, and all other mutations are now having to work together and the gap is really evident when it comes to technology.

The Boomers and GenX have not been immersed in technology their entire lives. When they receive proposals to review, and they're in techno-speak, it's often interpreted as kitchy, slangy, or sloppy. Your stuff was dismissed before you even had a chance to communicate its worthiness. Do your homework.

1. Know your audience. Be succinct and clear.
2. Use acronyms sparingly. Don't saturate your work with them. It looks like alphabet soup.
3. When you use acronyms, make sure to define them. (Is ASP a programming language, an application service provider, or a snake.)
4. It's fun to use or make up new words, but it doesn't help your cause if you lose your readers. Save the creativity for other genres and marketing projects.

Remember, it's your job to make sure that your work is "impossible to misunderstand."