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.
Subject:Re: Documenting A Moving Target From:WandaJane Phillips <wandajp -at- ANDYNE -dot- ON -dot- CA> Date:Wed, 21 Feb 1996 18:06:28 -0500
beth_staats -at- artisoft -dot- com wrote:
> [<snip:> I am trying to document a product that
> is still being developed, not just tweaked.]
> I had to document a very complicated piece of that software. It was a tangled
> web of many interrelated windows. In an effort to figure it all out, I wound up
> doing an Alt+Print screen of each window, pasting them into a Word doc,
> printing it out, then cutting out the windows and taping them to my cubie wall
> with arrows showing the flow. Seeing it all together even helped the
> developers; one saw it and said "there's TOO MANY windows."One similar experience happened when we ran some simple usability tests
using sales and tech support folks as crash test dummies. The developers
were in a room with a television monitor watching over the shoulders of
the testers. It was really enlightening to them to *see* someone try to
figure out their work, and how it really balled the works up when the
docs said go right but they'd changed it to left!!
Now, I know about most changes because the developers come to ask my
Senior Technical Writer -- Pablo
Usual disclaimers in effect