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 work at a software company that sells billing software. Recently, I asked
the management team for some high-level ideas about what the company's goals
are for system administrators, and what role (if any) documentation could
play in achieving those goals. Here's the response:
"I think that we have to cater to the more experienced audience. We want the
more experienced user to get what they need out of the system admin
section - we can't forget that we may generate, ultimately, more business
from the less experienced users who will look at the information and may
feel that it is too much for them to do thereby opening up an opportunity
for us to offer our services down the line as an extension of our
implementation where we are in control of these duties."
So, the strategy seems to be: Provide information that's only useful to
people who already know the product well. Less experienced people will get
frustrated and call us for consulting hours.
Does this seem like a good plan to you? How would you respond? Thanks for
your thoughts,
Brian
---
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.