Emma Maguire (née Campbell)
May 15, 2023
No doubt you're brimming with exciting new feature ideas you believe will add significant value to your business. However, simply asking customers about their thoughts on these ideas may not be the best way to gauge their chances of success. In this article, we'll discuss why this approach can be risky and provide some tips for validating ideas with customers more effectively.
It's natural to want to ask customers directly about new feature ideas, but doing so may not give you the insights you need to make an informed decision. For example, when you ask customers what they think about a specific idea, they may be inclined to say they like it, even if they don't. Additionally, customers may not fully understand how a new feature will fit into their current workflow or how it will impact other value propositions of your product or service. As a result, you may invest time, budget, and resources into building something that doesn't have the impact you thought it would.
Another risk of asking customers about specific ideas is feature bloat. Feature bloat is when you continuously add features without considering how they fit together. It can lead to a disjointed experience that ends up frustrating customers rather than helping. Simple solutions suddenly become complex.
Instead of asking customers about specific ideas, there are other ways to validate them. Here are our recommendations:
Arrange to observe your customers where they naturally interact with your product or service. Watch their interactions, what environmental factors they must deal with and the steps they take to complete a task. Get an understanding of actual use cases. Would your feature or idea fit in with this? Would it help or hinder them? Is it necessary to complete the task?
Instead of asking customers directly about a new feature idea, you should ask questions that help you understand the problem you're trying to solve. For example, if you're considering creating a chat feature that allows users to communicate with support, you could ask questions like:
By asking these types of questions, you can establish why someone might need support and their expectations. You might even uncover that many customers are having the same issues. Therefore, it might be more worthwhile to put time into ensuring they don't occur rather than adding a communication feature.
If possible, create a prototype or simulate the environment of your idea to test it in a realistic scenario with your customer. You can create prototypes digitally in software like Figma or even by utilising paper-based prototypes. Alternatively, it could be testing a process or service, such as creating an environment with an issue and prompting the user to resolve it to see the steps they would take and how your team responds. Combining questions and following up with a prototype would be the most useful way to validate ideas.
We recommend always saving the prototype to the final step so it doesn't introduce any bias from the customer.
It's crucial to do it in a way that provides meaningful insights and doesn't lead to feature bloat or a disjointed experience. By observing customers in their natural environment, using indirect questions, and creating prototypes, you can better understand their needs, preferences, and pain points. This approach will help you build a better customer experience and avoid investing time and resources into something that doesn't solve the real problem.
Remember, don't always trust what people say; trust what people do.
At Bo Studio, we're your agritech experience design specialists. If you're ready to work with an experience design studio, or you're already in the midst of a project and want a fresh perspective, don't be shy to get in touch with us for an initial consultation.Get in touch
Implement user observations into your agritech product development to gain impactful insights on improving your UX.
Discover how to make the most out of your time at events like Fieldays and gain valuable insights with these simple tips: actively listen, prepare a short script, be curious, keep a record, and share your insights with your team.