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.
Just saw this on How-To Geek, and it was entirely apropos:
Repetitive Brain Injury
In the context of tech support and customer service, Repetitive Brain
Injury is a condition affecting individuals who end up answering the same
questions over and over again on a daily basis.
-------
Oddly enough, several of my past employers charged for their tech support,
so they wanted people to call. Perhaps that one aspect of corporate policy
should be a cue to whether they're interested in good documentation and
their tech writing team.
On Wed, Sep 17, 2014 at 12:24 PM, Bowes, Rebecca <Rebecca-Bowes -at- idexx -dot- com>
wrote:
> One way to limit support calls might be to make support available by email
> only, with a response in 24 hours. I'd bet most people aren't willing to
> wait that long if a quicker answer is available in a help system or quick
> ref. Or at least that's the way it works with me :) -- having to wait 24
> hours has kept me from contacting Flare support every time I have a
> question.
>
> It could also be that users are much more likely to read the manual if the
> software is critical to what they are doing, it's their main tool, and they
> need its deeper features. OTOH, if a user's needs are shallow - they just
> touch the surface of the software and only for short tasks - they aren't
> going to invest time in reading doc. This theory is purely anecdotal and
> based on my own experience. I hate reading manuals, but I do delve deeply
> into many Flare resources, take Flare classes and webinars, and read lots
> of the Flare OLH. For other software I rarely use, I just muddle through.
>
> Rebecca
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Read about how Georgia System Operation Corporation improved teamwork,
> communication, and efficiency using Doc-To-Help | http://bit.ly/1lRPd2l
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as kathleen -dot- eamd -at- gmail -dot- com -dot-
>
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
>
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwhirl.com/email-discussion-groups/ for more resources and
> info.
>
> Looking for articles on Technical Communications? Head over to our online
> magazine at http://techwhirl.com
>
> Looking for the archived Techwr-l email discussions? Search our public
> email archives @ http://techwr-l.com/archives
>
--
Kathleen MacDowell
kathleen -dot- eamd -at- gmail -dot- com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Read about how Georgia System Operation Corporation improved teamwork, communication, and efficiency using Doc-To-Help | http://bit.ly/1lRPd2l
