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.
I think I'd approach it two ways: first, through my manager (or her manager,
if you're the doc department), pointing out that you've got some expertise
and could
both improve the product and shorten development time (by avoiding mistakes
in
the first go-round). Second, I'd reply to her request with more than she
asked
for, including good general examples of UI, the competition's UI, and maybe
some
books or reference works you've got lying about. Any bug reports or
enhancements
that have been filed against the UI would be nice to have available too.
And, of course, I'd offer to help her directly, as a team member...
Art
Art Campbell
Technical Publications
Northchurch Communications
Five Corporate Drive
Andover, MA 01810
978 691-6344
-----Original Message-----
From: Sarah Stegall [mailto:stegall -at- TERAYON -dot- COM]
Sent: Friday, April 30, 1999 1:53 PM
To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Subject: Educating Rita
Okay, her name's not really Rita, but let's use
that name anyway. She's a software
developer/engineer who works for us. Mainly she
writes code. Recently she started working on a
new version of a software product, and has asked
me for a copy of some technical illustrations from
an old manual to use in devising the interface for
the product. This is where the light bulb over my
head went on: she's designing a user GUI with no
previous training or experience, just basing her
design on what she's seen and worked with before.
I would very much like to get my oar in before the
development of this interface goes too far, so
that we don't get some god-awful color scheme like
last time, or confusing button labels (OK and
Accept on the same screen)etc.
My question: What's an effective way to approach
a touchy, rather defensive SME to offer help in
designing a GUI? Nothing that smacks of implied
criticism will work; she's very thin-skinned.
Also, her command of English is less than
perfect. Any suggestions would be very much
appreciated. Thanks.