1

Theoretically there is always going to be some degree of bias in research, so it would be more appropriate to aim for practices that aim to minimize the degree of bias. The problem with the way the feedback is being collected isn't so much to do with the question being a little bit 'loaded' so that you are likely to get a particular response (but you should ...


1

From the way you've put parts of the question in parentheses, I interpret that the actual proposed question reads something like: "If our organization offered a way to book travel without having to check other websites and with a cheapest-price guarantee, would you be interested in using it?” with actual, specific information like that in both of those ...


1

It seems to me that you'll want to present this through two multiple-choice questions, both short and to the point and with a limited range of possible answers, but more than a single presumed goal (data point 1) and more than two top-tier, also presumed, pain points (data point 2). To that end, you'll need info on alternate goals and pain points - hard to ...


1

That's definitely a tricky situation to be in. If you are conducting some qualitative user research you could possibly use the data to confirm the pain point and support the goal which you are working towards. Another way I can think of is: If you want to add it as a survey question it might be good to ask: How useful would this feature/functionality be ...


1

You are right. This really needs a deep understanding of context. However, do not tell users what are their pain points ( this creates a bias). Instead, ask them what are their pain points, and goals. Survey is to get their views not to confirm your beliefs. Also, ask them what is the motivation for them to use existing system. See if that is accomplished ...


1

From a marketing perspective, I wouldn't even mention the deprecated plan -- it'll just show customers that you've hiked up prices, and make them unhappy before they even purchase (or they might take it as a sign to haggle and call in to request the lower price). What percentage of your customer base will be asking about this? You might be able to wait it ...


1

This sounds like they're trying to catch user stories in components, and constrict those components in usage. That's not exactly what user stories are about. A user story is supposed to be a short statement about a task a user wants to do with a particular software. It briefly describes the user, the task, and what benefit the user gets from it. However, in ...


Only top voted, non community-wiki answers of a minimum length are eligible