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.
Like Geoff, I've also started getting involved in interface design. I think
one of Geoff's points is a key to success (or at least to my success):
"But in each case, note that I offered a way to make someone's life
easier rather than acting as a critic (thereby inherently trying to make
their efforts at interface design look foolish). "
You can't just point out problems - you have to offer solutions. And your
solutions need to not only solve the problem from the original design, they
have to be fairly easy to implement (and if they aren't, they better provide
a lot of value). I've also had success in suggesting several variations or
different alternative approaches - of course, during crunch time, I know
which solution will be implemented (the easiest one!). But a "killer
solution" may be implemented for a later release.
If you know your product well, you can often suggest solutions that copy
from other areas of the product - this is often the easiest way to get your
suggestions into the release.
One other thing to remember is to use the golden rule - treat others as you
would want to be treated. We often complain on this list of people reviewing
the docs and making suggestions that have no impact on the actual accuracy
or readability of the docs. Instead, it is simply matter of personal style.
Don't make the same mistake with UI design. Look for REAL areas where you
can add value to the product, not just do something cool.
It starts with one great suggestion, and builds from there.
NEED TO PUBLISH YOUR FRAMEMAKER CONTENT ONLINE?
?Mustang? (code name) is a NEW online publishing tool for FrameMaker that
lets you easily single-source content to Web, intranets, and online Help.
The interface is designed for FrameMaker users, so there is little or no
learning curve and no macro language required! See a live demo that
will take your breath away: http://www.ehelp.com/techwr-l3
---
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.
