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.
RE: Working with developers (was Re: About The Cloud: Quick-ReadSuggestions)
Subject:RE: Working with developers (was Re: About The Cloud: Quick-ReadSuggestions) From:Joyce -dot- Fetterman -at- L-3com -dot- com To:"Keith Hood" <klhra -at- yahoo -dot- com>, "Weissman, Jessica" <WeissmanJ -at- abacustech -dot- com>, <salt -dot- morton -at- gmail -dot- com> Date:Thu, 4 Apr 2013 14:05:01 -0400
<<"It helps, of course, to bother them as little as possible and to ask
the smartest questions you can.">>
In my experience, I've found the "how" of asking questions to be just as
important as asking the right questions. I'd ask my developers how they
wanted to approach my questions. Did they want one email a day with all
of my questions lumped together? Perhaps one email for each issue for
better tracking? Some preferred F2F discussions. I learned which ones
were grumpy at what part of the day and tried to avoid Grumpy Time.
When I demonstrated that I valued their time and wanted to be mindful of
their preferences, they generally reciprocated.
Joyce Fetterman
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>From our sponsor Doc-to-Help: Want to see a Doc-To-Help web-based Help sample with DISQUS for user commenting?
