- Focus on writing a quality survey. Talk to your subject matter experts for research
- Do some usability testing - this step for me really counts. I find having a few people in your target audience try out the survey really helps.
- Change it as necessary - feel free to change or customize a survey for best results, especially if users test and you discover readability issues.
- Never assume users understand the questions. Make sure you rid yourself of a question if it isn't meeting the scope of the survey or standards you work by.
- Keep an open-minded attitude on the survey and the data collected. This is definitely something I learned getting my doctorate. Also watch for outliers and think about them. You may or may not want to discard them but don't ignore them.
- Focus on data and metrics that are actionable. Remember you need results to tell you something about what you are asking.
- Finally, get more involved feedback from users, subject matter experts etc. That way you can continuously modify if the survey is ongoing.
You know, what have we learned here today? Perhaps it's that no one can take your mojo! - Jerry Springer
Have you thanked your technical writer today?
The Mojo of technical communication and writing as mused by Dr. Lu Kondor
Friday, October 11, 2013
Writing Surveys to Collect Technical Information at Organizations
I have recently finished writing a number of surveys to acquire technical information from users. I actually love creating surveys because I learn a great deal about asking all the right questions for the information I need. They are also a collaborative effort sometimes involving quite a few individuals from subject matter experts to management.I thought I would write about it because I think this aspect of technical communication is rarely thought about. Here's what I have learned on creating surveys from my recent batch of them. I'm not getting technical like the type of instrument such using a Likert scale, but more in the area of basic ideas to keep in mind.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment