Re: useful customer feedback

Subject: Re: useful customer feedback
From: David Locke <locke -at- SUGAR-LAND -dot- ANADRILL -dot- SLB -dot- COM>
Date: Wed, 20 Nov 1996 15:30:53 +0000

At 01:10 PM 11/20/96 -0700, you wrote:
>Karen Brown asked, "Anyone had luck in extracting usable feedback
>from customers?"

If you have a technical support line, you should be getting all the feedback
you need. Every call has a reason. And, you need to figure out the reason
for the call. It might be that some topic is not covered. If that was
deliberate, don't do anything, but if it was an acidental ommission,
remember to include it next time. It might be that the topic was
inaccessible, a process was described incorrectly. Then again the user may
be trying to do something beyond the scope of the software, or the user may
just be aliterate. You need the technical support peoples help. It is not
enough to get a summary of topics. You will need details.

I have included a list of tasks on a reply card and asked the users if they
sucessfully performed those tasks. This will get you a low response and
unrepresentative survey. You can increase response rates by making some kind
of offer, like a T-shirt, a coffee cup, or a raffle for free software. The
responses will not be representative, but you will get some responses.

David

Locke -at- sugar-land -dot- anadrill -dot- slb -dot- com
Engineering - Drilling Information Products
200 Gillingham Ln. Voice: 281 285 4722
Sugar Land, TX 77487 Fax: 281 285 8098


Previous by Author: Re: Word 7 etymology
Next by Author: FW: Ventura to Acrobat
Previous by Thread: Re[2]: Documenting a Programming Language. WAS:Syntax Diagra
Next by Thread: Re[2]: useful customer feedback


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

Sponsored Ads


Sponsored Ads