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: When is it too much information? From:yehoshua paul <ysp10182 -at- gmail -dot- com> To:Keith Hood <klhra -at- yahoo -dot- com> Date:Mon, 18 Feb 2013 19:23:01 +0200
Let me clarify. This is NOT a major disagreement between me and the support
guy. He sits next to me in the open space, and we get along fine.
This is a minor issue, and I am curious as to what other people think.
I am just not a big fan of wasting words. If I don't include a procedure, I
don't see why users would invent in, but has been already pointed I'm not
the one dealing with the customers on a daily basis.
On Mon, Feb 18, 2013 at 7:16 PM, Keith Hood <klhra -at- yahoo -dot- com> wrote:
> I think adding such a note can't hurt the users. I don't see it
> 'hindering' them in any way. And adding it may help your relationship with
> the support guy. If the inclusion really is so tiny and meaningless, then
> there's no point in starting a controversy with him.
> *From:* yehoshua paul <ysp10182 -at- gmail -dot- com>
> *To:* tech2wr-l <techwr-l -at- lists -dot- techwr-l -dot- com>
> *Sent:* Monday, February 18, 2013 9:07 AM
> *Subject:* When is it too much information?
> While reviewing the latest release notes that my company sends out every
> couple of weeks, one of the support guys suggested that I add the following
> words (or something similar) to one of the change descriptions: "The user
> does not need to do anything." What changed is information that was
> displayed in one area of the UI is no longer displayed. The support guy
> thought the users might think they need to do something, now that they no
> longer see this information.
> I told him, if the users needed to do something, I would write this in the
> release notes like I did with some of the other changes, and include the
> relevant steps, or the appropriate reference to the online help. If I
> didn't write anything, why would the users think they need to do something?
> His argument was that it doesn't hurt to add the sentence, and it may
> prevent confused customers from calling customer support.
> What do you guys think? Would adding a superfluous sentence (in my opinion)
> help or hinder users.
> EPUB Webinar: Join STC Vice President Nicky Bleiel as she discusses tips
> for creating EPUB, the file format used for e-readers, tablets,
> smartphones, and more.
> Learn more: http://bit.ly/12LyN2z
> You are currently subscribed to TECHWR-L as klhra -at- yahoo -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
> 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
EPUB Webinar: Join STC Vice President Nicky Bleiel as she discusses tips for creating EPUB, the file format used for e-readers, tablets, smartphones, and more.