How to use surveys to get feedback


A couple of weeks ago, I explored how user interviews can help with your discovery efforts. One of the key messages was the questions you ask will go a long way to determining how effective your user interviews are.

You need to know what you’re trying to find out, and you need to ask people questions about what they actually do, not what they think they might do.

You want stories, not predictions.

And you may have read that newsletter and said “sounds like a great idea. An example would be handy right about now.”

Ok. Here you go.


Product Management Newsletter Survey

I’m curious what newsletters you read for product management knowledge, and why you read them. Please fill out this survey and let me know.

It’s only six questions, and your input will help me immensely.


Good interview questions work in surveys

Did you take the survey yet?

No? I’ll wait.

Ok. What did you notice about the questions?

I tried to word them to get you to answer what you do (So you pay to subscribe to any of these newsletters?) rather than predict what you would do (Would you pay to subscribe to a newsletter?).

I also asked a question to find out why, but again why you took a particular action, not why you think you would or would not do something.

We’ll see what results I get, but I suspect asking the questions this way will provide more meaningful results. It’ll also reduce the chances that people will lie to me.

I didn’t mean you, of course.

Surveys work well alongside user interviews.

User interviews can be time consuming, so you’re only going to talk to a few people. It makes sense to supplement those user interviews with a survey to get feedback from more people.

You may want to do the survey first to get a broad picture about what folks are doing, then use the user interviews to dig more into why.

Of course, to make sure people respond to your survey, you’ll want to keep it short so you’ll need to be real clear on what you want to find out, so your research question is important as well.

I’m going that route with this survey by opening the option for people to let me know if they’d like to discuss further, but not requiring that.

If you’ve got feedback from surveys and interviews, I’d love to hear about your experience.

And if you haven’t taken the survey yet, now’s a great time to take it now.

Thanks for reading

Thanks again for reading InsideProduct.

If you have any comments or questions about the newsletter, or there’s anything you’d like me to cover, just reply to this email.

Talk to you next time,

Kent J. McDonald
Founder | KBP.Media

InsideProduct

Hand-picked resources for product owners, business analysts, and product managers working in tech-enabled organizations. Check out the resources I offer below and sign up for my newsletter!

Read more from InsideProduct

I try not to overuse click bait titles, too much. For this particular topic, however, it was just too tempting. As I mentioned in a previous newsletter, there were several reasons I went to Agile2024 after a six year hiatus. One was to get a sense of the current state of agile. There’s been a bit of chatter about the decline in agile coaching opportunities as well as trends in agile transformations in general. I certainly caught some inklings about what’s going on, but I didn’t want to rush...

I’m back from Agile2024, and it was good to be back after a 6 year hiatus. I caught up with some old friends, made some new acquaintances, and had some great discussions along the way. Some of those discussions will influence future issues of InsideProduct, and others will go down as obnoxiously long running inside jokes. If you're wondering about the latter, ask me about retractable stairs or comic sans the next time you see me. While I’m not going to talk about those topics here, I did want...

For the last few weeks, I’ve explored what prioritization looks like in a variety of different scenarios. This week finished up that series with a look at how you can go about prioritizing a bunch of stakeholder requests. This is a common scenario when you’ve already built software for your company (ie internal product) and you’re trying to optimize or maintain it. A unique aspect for internal products is that most requests for changes come from other people inside your company who may, or...