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.
RE: Motivation and satisfaction in technical writing
Subject:RE: Motivation and satisfaction in technical writing From:"Jim Shaeffer" <jims -at- spsi -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Tue, 24 Jun 2003 12:35:11 -0400
Here is an excerpt from "Moving from Information Transfer to Knowledge
Creation: A New Value Proposition for Technical Communicators", the
Outstanding Article of 2002 from Technical Communication: Journal of the
Society for Technical Communication. It may provide another way to see
(and talk about) the value of what we do.
================================================================
In essence, this discussion lays the groundwork for an expanded value
proposition for technical communicators: They escalate knowledge within
an organization, thereby increasing the value of that organization's
knowledge assets.
TECHNICAL COMMUNICATORS AS CREATORS OF KNOWLEDGE
Technical communicators make three important contributions as creators
of knowledge within an organization.
They help experts make their tacit knowledge explicit.
They help design teams arrive at consensus about what the product is or
does. In this regard, they are facilitating knowledge creation at the
group level (or at a minimum, escalating individual knowledge to the
group knowledge level).
They create knowledge assets. That is, they transform tacit knowledge
into explicit artifacts so that it can be accessed by others within the
organization.
<end excerpt>
==============================================================
In this view, we make knowledge explicit that used to be implicit and we
build "knowledge artifacts" that can be accessed by others in the
organization. These "knowledge artifacts" (documents, templates, white
papers, etc.) are ways that organizations learn things. Once in place,
these artifacts allow the organization to build on that knowledge,
increasing the value of the organization.
RoboHelp Studio maximizes your Help authoring power by combining
RoboHelp Office and RoboDemo, so you can easily create professional
Help systems that feature interactive tutorials and demos.
---
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.