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: Your opinion, please! From:"Mark Baker" <mbaker -at- ca -dot- stilo -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Wed, 18 Jun 2003 11:13:43 -0400
Brian Das wrote:
> But the clients are completely baffled and frustrated by the whole
> regulatory environment, and how the software works in it. They
> don't get the
> concepts, including the underlying technology (XML). So they can't even
> begin to understand how those concepts function "on the ground"
> (i.e. in the
> software).
I think you have captured the essence of your problem in that last sentence.
If people do not understand the task, they will never understand the tool.
There is not going to be a successful information strategy for the tool
until you address the problem that people do not understand the task.
It seems to me that many of the companies the supply software to regulated
industries make themselves experts on the regulatory environment and supply
help and consulting on that environment as part of their offering. A lot of
our customers are consultants who create specific document processing
software for industries that must use specific SGML and XML DTDs, and our
customers base their business on their knowledge of those DTDs and the
regulations that accompany them. A lot of our own business is based on first
helping people to understand the issues involved in content engineering,
markup, reuse, and single sourcing, and then teaching them to use our tools.
Whether or not your company wants to change its business model in this way
is, of course, beyond your control. But don't get carried away with the idea
that there is some documentation design or packaging trick that is going to
help here. If you want people to understand your software, you, or somebody
else, will have to first get them to understand their task.
Perfectly ordinary documentation and training methods will probably suffice
to teach them their task, and perfectly ordinary documentation and training
methods will probably suffice to teach them your software. You just have to
apply them in the right order.
---
Mark Baker
Stilo Corporation
1900 City Park Drive, Suite 504 , Ottawa, Ontario, Canada, K1J 1A3
Phone: 613-745-4242, Fax: 613-745-5560
Email mbaker -at- ca -dot- stilo -dot- com
Web: http://www.stilo.com
This message, including any attachments, is for the sole use of the
intended recipient and may contain confidential and privileged
information. Any unauthorized review, use, disclosure, copying, or
distribution is strictly prohibited. If you are not the intended
recipient please contact the sender by reply email and destroy
all copies of the original message and any attachments.
---
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.