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.
In my opinion, satisfaction surveys are different depending on if you're
addressing training recipients or application implementation. I don't have
any handy that I can send you right now, but I can give you some
suggestions:
Break the survey down into categories. For example, if the customer
received training, you might have a section on location, (easy to get to,
convenience, etc.) the training room (light, temperature, seating
arrangements, etc.), the delivery (variety of presentation media -
overheads, flip charts, demos, hands-on time, etc.), the handouts (easy to
follow, room for notes, complete, etc.), the instructor (knowledgeable,
professional, pleasant to deal with, took the time to answer questions,
etc.). Provide a satisfaction scale for each question (1 - 5 works well)
for them to indicate their satisfaction.
For each category, allow room for them to add individual comments. At the
bottom, ask about their overall satisfaction, what they liked the most and
why, where they thought improvements could be made, whether they would
recommend other employees of their company to take the course, whether they
would recommend other companies to take the course, etc. Say thank you at
the bottom. Make the name of the person completing it optional, but you
might say something like "Please provide your name and company if you would
like us to call you to discuss any concerns you have."
This type of survey allows you to quickly tabulate results, and also
pinpoint the exact reason for dissatisfaction (ie, if they were
dissatisfied with the room, you would like to know that it was because it
was too hot, not because the room was too bright.)
Suzette
-----Original Message-----
From: Gina Hertel [SMTP:Ghertel -at- ALPHA88 -dot- COM]
Sent: Thursday, June 04, 1998 3:44 PM
To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Subject: Post-initiative Customer Satisfaction
Sorry for the cross postings, but I'm working with a deadline (8am
tomorrow-aah!)
I was wondering if any doc departments have been responsible for creating a
satisfaction survey-not for documentation, but for your company's
products/services. I need to create a customer satisfaction survey that is
submitted to the client after we've implemented a new app, an Exchange
migration, training program, etc. You know a checkpoint to ask "How did
our company do?"
If you can mail me any sample surveys or point me in the direction of some,
I would be most appreciative.
We can debate the value of using surveys to obtain feedback later.
Thanks,
Gina