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: How much educating do your 'clients' need? From:Gwen Barnes <gwen -dot- barnes -at- MUSTANG -dot- COM> Date:Wed, 11 Oct 1995 22:12:51 GMT
-> My question to the list: How can we work together to educate higher
-> management on the value we add to projects? Then, can we suggest ways they
-> can implement that education?
You can try, but my impression of the situation is that nothing will
happen to educate higher management until it becomes a "bottom line"
issue. They may be willing to hear from people within the organization,
but more often it will be their competitors that drive them to it.
If your organization has an "innovative" style of management, listens
to customers, and empowers employees to serve the customers as the first
priority rather than the organization, then talking to management about
quality documentation as part of a quality product makes good sense.
If the organization is mainly concerned with organizational things and
puts the customers at a lower priority, the only likely outcome if you
attempt to "educate" them will be animosity. It's like trying to reform
a drunkard all by yourself. Doesn't work, never will, and the only thing
that reforms a person is that person.
Choose the right company to work with, and management will solicit your
expertise because they consider you a valuable, useful part of the team.
