You probably have a firm grasp on some of the universal metrics of SaaS success: ARR, growth rate, churn rate, CAC, LTV, etc. There is no doubt that these are critical, but in many ways these metrics do not tell the whole story of “success”. So what’s the leading indicator that can give you a fuller picture of success? Your customers’ satisfaction.
Fewer Questions Means Better ResultsNovember 13, 2012
After persuading a Fortune 100 firm to run an A/B experiment, the Harvard Business Review (HBR) reports that asking fewer questions in a survey (four to five) will not only have more value, but will also appear less intimidating than asking a longer series of multipart questions. “Response rates for the fewer questions were over 11x better than for the full questionnaire. When one factored in the declining quality of ‘tail end’ answers, people clearly just ‘box ticking’ the final five or six answers to be done with it- less proved more.”
Here at Qualaroo, we believe that surveying is one of the most effective ways to get direct feedback and responses from customers and website reviewers. Although we agree with the article that “you’ll learn a lot more by asking a lot less,” instead of four or five questions, even asking one simple but effective query can prove to be even more valuable. Not only will one question appear more simple and easy to answer to a visitor, but it will also allow you to focus in on a certain type of feedback your company may be looking for, whether it is related to product development or increasing sales.
We’d love to hear from you and your thoughts on the benefits of asking fewer questions. What questions have you found to be most effective and on average, how many questions do you ask your customers for feedback? You can also read the full blog post from the HBR here.
We grouped our list of 29 questions into the different topics you should consider exploring in prototype testing. Aim to choose at least one from each section to make sure all your bases are covered. We’ve also included a few pro-tips here as food for thought.
This article will cover the major Dos and Don’ts of prototype testing. We’ll walk you through the most common mistakes we see in the field and share tips on how to avoid them.
Testing prototypes is an inherent part of finalizing designs. Nobody wants to wonder why users are not utilizing an app the way it should be utilized or why they can’t seem to complete a purchase on your website. And nobody wants to rework something that’s already been shipped.
UX designers are under a lot of pressure to produce designs that add value to users’ lives. But without input from your users, it’s nearly impossible to design an experience that actually helps alleviate their pain points. If you’re pressed for time and/or don’t have the help of a researcher, getting the user input essential to design a great product can certainly be a challenge.
As a UX designer, getting your leadership to support your major projects can be as much about talking the talk as it is about walking the walk. As much value as your work may provide, you also have to know how to sell it in a world of competing priorities and looming deadlines.
Even as UX design and user research are becoming a more prominent focus in today’s leading companies, it can still be tough to get executive leadership onboard with user research-related initiatives. We know the struggle.
This post originally appeared on UsabilityGeek.