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 one reason for this is that we expect our users to go out and invent
new uses for our products. That is, we don't necessarily know all the
potential uses our product may have, so we document how it works, and leave
the rest to end users.
Our product here at SchlumbergerSema is a good example. We manufacture RF
LAN technology. Our manuals tell how to install and configure the network
components, which were originally intended for use by utilities in
monitoring electric/water/gas consumption. But some end users have used the
technology to create test systems that monitor parking meters, or the fill
level on vending machines. I, at least, would never have thought of these
uses.
Once the user knows the basics of how to use the product, they'll come up
with unique ways to use/extend it. Inventing new uses for existing
technologies is practically a way of life here in the States. Look at the
guys who put weed-trimmer engines on those ubiquitous scooters, or the way
HTML has "evolved" from a mark-up language to a layout tool (however poor).
Just my opinion, of course.
Dan
Dan Hall
Sr. Technical Writer
SchlumbergerSema GTSRN
All the opinions, errors, sarcasm, and wit (if any) expressed in this
e-mail are solely mine. SchlumbergerSema takes neither credit nor blame
-----Original Message-----
From: bounce-techwr-l-72045 -at- lists -dot- raycomm -dot- com
[mailto:bounce-techwr-l-72045 -at- lists -dot- raycomm -dot- com]On Behalf Of R. Johnson
Sent: Tuesday, July 17, 2001 3:00 PM
To: TECHWR-L
Subject: Documents I'd like to see...
I'd like to see more documentation that illustrates
potential real-world solutions based on the functionality
of particular software applications. For example, I?d be
interested in seeing how others have used mail merge in
ways other than creating form letters; or how to create a
knowledge base that enables you to maintain, update or
generate an entire policy and procedures manual at the
click of a button; or how (and why) to create an animated
movie using layers in PhotoShop; or creating CBTs in Power
Point.
Why is there such a dearth of ?solution? based
documentation? Everything seems to be ?process-oriented?
rather than ?results-oriented.? Reference manuals and user
guides are fine, but sometimes I?d like to see an example
of the functionality in actual use, rather than
?Select-File-Click-OK.? Am I alone in this or do others
feel this way too?
*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available now at http://www.devahelp.com or info -at- devahelp -dot- com
TECH*COMM 2001 Conference, July 15-18 in Washington, DC
The Help Technology Conference, August 21-24 in Boston, MA
Details and online registration at http://www.SolutionsEvents.com
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
