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.
So the question is: does a company want to bind themselves to a rigid,
expensive system that requires extensive "non-writing" maintenance overhead to
get reusability, change management, and eventual ROI.
Let's place tech writing groups into three categories to analyze this benefit:
1) Basic: 2 - 5 writers, 20 to 50 documents produced per year. 75% generation
of new docs, 25% maintenance of old docs. Docs are very prone to change. The
group is mostly savvy writers who work independently.
2) Intermediate: 5 - 20 writers, 50 to 200 documents produced per year, 50%
new doc generation, 50% maintenance docs. Many docs are static with little
change, but new stuff is still in flux. The group is a mixture of independent
writers and corporate drones.
3) Large: 20+ writers, 250 to 500 documents produced per year, 25% new doc
generation, 75% maintenance. Lots of basically static documents, some new stuff
is in flux, but this is minor. The group is mostly corporate drones with few
Now, let's ask ourselves, which groups would REALLY benefit from a structured
Basic: No way. Too small. The expense would crush such a group. Not to mention
the fact that structured systems are not well suited to new doc generation.
This group would be better off setting very basic standards and hiring very
capable writers allowing their group to grow and mature naturally. Reliance on
savvy, independent writers basically precludes any hope of centralizing the
Intermediate: Possibly. With a larger percentage of maintenance docs, there is
a powerful argument to standardize those docs for quick turn around. Such a
group may benefit from a limited change management system. Although the drones
should be put in charge of the system while the independents do all the
writing. A full structured system would probably be excessive.
Large: Probably, if they can stomach the cost. With such a huge margin of
maintenance documentation, a large structured system becomes almost a
necessity. Also, with lots of initiative-lacking drones, large complex systems
with lots of rules and regulations give the drones a sense of purpose in life.
Thus, the tipping points for a rigid documentation system are:
- Scope: Does your group have a ton of documents?
- Static vs dynamic: Are those docs essentially static or do they go through
- New vs. Maintenance: What percentage of your docs are "new" versus merely
updates to existing docs?
- Personnel: Are you a group of free-wheeling independents who don't need no
stinkin' rules or a pack of committee-philes who need a crystal clear path from
ignorance to tepid achievement?
If you have money, time, drones and a ton of documents, call Tim and Dan. I am
convinced they can make your XML/DTD thing work.
If you have no money, no time, and are basically about to be kicked in the ass
by the CTO for not having decent docs - call a freewheeling independent (like
me) who can hammer the docs back into shape.
However, one last point: interesting documents do not come from organization.
Only a capable writer who comprehends the subject matter can write in an
interesting manner. Thus, no DTD/XML thing can make your documents more
interesting. You got to have a clue to do that.
Sponsored by SOLUTIONS, Conferences and Seminars for Communicators
Publications Management Clinic, TECH*COMM 2001 Conference, and more http://www.SolutionsEvents.com or 800-448-4230
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.