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.
Sean,
Here are few things that helped me work successfully with my GUI
developers:
Sit near the developers, in the same room if possible.
Interview your users, in person or by phone, and learn how they use your
product to do their work (task analysis).
Learn as much as you can about the product you're all working on and
share what you learn with the developers that haven't stopped learn the
same things.
Always provide constructive criticism: give them an alternative design,
even with pencil and paper.
Go to the development status meetings and listen a lot before talking.
Strike alliances: with enlightened developers, testers, and customer
support people.
Get on the development managers' good side. If they respect you, they
might even get their developers to listen to you.
Subliminal: reward them with treats for good behavior (when they consult
you or tell you about changes they make).
