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 have been working as part of the design team defining what the latest
module of our software package will look like and what it will do. Much
of my contribution has been to write scenarios - how various end users
will use our software along the lines of "Joan, a group manager, logs on
and sees ..." It focuses on their needs, their problems, and how they
will use our software to accomplish their goals. This has been very well
received by our customers. Surprisingly, the developers also like it.
They tell me that when they're writing the code based on the specs and
scenarios, they really appreciated for the first time how people will
actually have to USE what they code.
The power of storytelling ...
John Garison
Principal Technical Writer
Integrated Development Enterprise, Inc.
150 Baker Avenue Extension
Concord MA 01742-2174
978.318.9380 x407
978.318.9376 Fax
-----Original Message-----
From: Justin Soles [mailto:jsoles -at- TYPHOON -dot- CO -dot- JP]
Sent: Tuesday, April 27, 1999 8:36 AM
Subject: Technical Writing as Storytelling (?)
I was walking along an underground corridor when I saw an ad for Avid (a
video-editing software company) with the caption "Tools for
Storytellers".
At the time, I just thought it was a good tagline and walked on.
Later, I realised that a lot of what we do in technical writing is just
that: storytelling. We may frame and present it in different terms,
(minimalist user guides, context-sensitive online help, etc.) but the
focus
is in engaging our reader / viewer / audience, having them resolve a
particular conflict and move forward towards a conclusion. George Lucas
may
have a wider scope, better special effects and a bigger budget, but the
idea
of telling a story to educate, illustrate and demonstrate is the same.
I'm curious as to whether anyone is taking or has taken this approach to
technical writing. If so, how did you do it and what was the result?
Reply
onlist of off, your choice.
Cheers,
Justin
------------------------------------------------------------------------
----
-----------------------
Justin Soles
PacificData Inc.
