Re: When is it too much information?

Subject: Re: When is it too much information?
From: Keith Hood <klhra -at- yahoo -dot- com>
To: yehoshua paul <ysp10182 -at- gmail -dot- com>
Date: Mon, 18 Feb 2013 10:06:12 -0800 (PST)

I never thought there was a major hassle between the two of you. My point was there's no point in possibly starting any hassle of any size between the two of you over something so minor. The guy may have a point. I say shrug and put in the one short sentence he wants. I understand you don't like wasting words, but in this case it *might* not be a waste. Putting in what he wants can't hurt, might help, costs nothing but three seconds.

And, ask him how often he gets calls from customers that are caused by the lack of such a brief "no need" sentence. Maybe putting it in could save him some time; it would be worth it to find out. That information may give you a pointer toward refining your documents in the future.




________________________________
From: yehoshua paul <ysp10182 -at- gmail -dot- com>
To: Keith Hood <klhra -at- yahoo -dot- com>
Cc: tech2wr-l <techwr-l -at- lists -dot- techwr-l -dot- com>
Sent: Monday, February 18, 2013 11:23 AM
Subject: Re: When is it too much information?


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.

Yehoshua



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.
>
>Yehoshua
>
>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>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
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
>
>
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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 archive -at- web -dot- techwr-l -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


References:
When is it too much information?: From: yehoshua paul
Re: When is it too much information?: From: Keith Hood
Re: When is it too much information?: From: yehoshua paul

Previous by Author: Re: When is it too much information?
Next by Author: Yahoo!'s telecommute policy (was Re: Telecommuting ( was: Do as I say, not as I do ))
Previous by Thread: Re: When is it too much information?
Next by Thread: RE: When is it too much information?


What this post helpful? Share it with friends and colleagues:

Sponsored Ads


Sponsored Ads