The success of a new product depends on many factors.
Is there a market for the product? Is the product solving a major issue? And is your product being accepted by users and customers? In this article, we want to shed some light on the topic of product validation and answer the question: What can you do before you start developing a new product?
What Can You Do Prior to Developing a New Product?
There are different things you can do before you start development of a new product.
The most important things are market research, user research (including interviews with potential users and customers), development of a prototype as well as user testing of this prototype.
I will now go deeper into these points and explain what happens after the initial idea for a product has been created.
Is There a Market for Your Product Ideas?
You have an idea for a new product.
Your product is solving a specific problem, but is there also a market for this problem?
Think about the following things:
- What similar products already exist on the market? What are the competitors charging?
- Who are your customers? Where do they come from?
- What is the current evaluation of the market?
When you’re answering those questions, you will learn a lot about the volume of the market and about potential customers. This can also help you determine a pricing structure that you can offer to businesses, start-ups or individuals.
Talk to Potential Users
The start of the development phase of a product is the best time for talking to potential customers and asking them about their specific problems and challenges. That way, you can find out whether your problem is actually a problem and how exactly your product could be used.
From these interviews, you will also learn a lot about workflows and maybe also the willingness of using new products. You will also learn which product modifications are necessary.
Peter Buchroithner, CEO of the decision-making app Swell asked 200 people about the name of the product prior to moving the company to the USA. Because of this survey, he decided to change the name from “Dvel” to “Swell”.
Another important thing to think about are the reasons why a customer would pay for your product.
During the interview, try to understand the motivation and requirements of the users as this is where your product can come in. Maybe you can also gain some early prospective buyers during this interview before the product is even finished.
A further option is asking interview partners, which tools they are currently using and what advantages and disadvantages they see in it. This can help you focus on certain features that you can use to distance yourself from your competition.
Ask about their experiences instead of asking what they “want”. For a long time, Netflix made the mistake of asking its users what they would like to watch.
Foreign independent movies and documentaries. As you can probably guess, this isn’t quite the most-streamed content on Netflix… 😉
Experiences are more helpful. You can use them to draw consequences for the development of your own project.
Developing a Prototype
A prototype can have many different forms, as we explained in an earlier blog post.
The advantage of the prototype is that it can be changed faster and the changes cost less time and money.
A first prototype might consist of only drawings on a piece of paper (low-fidelity prototype). For high-fidelity prototypes, you generally have to invest more time and effort.
Often the low-fidelity prototype is the point of origin for the high-fidelity prototype.
Here are a few blog posts that we can recommend for this topic:
- What we Learned From Prototyping
- How to Develop a Prototype for Your Website or App
It’s important not to spend months on the development of a first prototype during this phase.
The interesting thing now is to test your prototype with your users.
This can take on many different forms, depending on how far developed your prototype is. The tests can either be personal tests with individuals using Skype or various other tools. By the way, many of our customers are currently using Usersnap for this project phase. 😉
Again, the testing of the prototype is a relatively cheap option to get feedback from the users before the product launch.
In this phase, it’s more important to receive quality feedback from customers instead of having a large quantity of bad feedback. If you recognize obvious flaws now, you still have the chance to change them without damaging your brand.
We have written various blog posts about user testing as well, maybe they will be interesting to you:
- Introduction to User Testing
- User Acceptance Testing Checklist
- 6 Tips for a Successful User Acceptance Testing
There are many things you can do prior to developing a new product.
The most important ones are market research, user research (including interviews), development of a prototype and user testing.
Once you have completed these four steps in a satisfactory way, you can start product development with increased market knowledge and user experience.
Is Email the best customer support channel?
A lot has been written on how companies can grow their business through customer success. The terms “customer success” or “customer experience” seem to be the new buzzwords in the growth-driven tech world. These discussions are great, and we at Usersnap believe that customer support and customer success are important factors when it comes to business…
6 proven ways to boost customer happiness in 2016
Finding bugs in your product is part for your customer’s journey. A stable product means happier users and less user tension. But there’s more to making customers happy than having a bug-free product. This is where customer success comes in. The term customer success was coined only recently but it is already big with SaaS…
Top 8 SaaS Monitoring Tools for DevOps
As a SaaS business, we’re regularly trying new products and tools to help us with DevOps. We recently started to evaluate a lot of different SaaS monitoring tools and wanted to share some of our findings. You’ll find some thoughts about the following tools in this post.
7 unexpected lessons learned from writing 200+ articles
I love to write. For me, writing is a special place where I feel good and happy. Writing is so much more for me than just the process of writing. It motivates me, it educates me, it inspires me, it connects me with like-minded people. Just recently, I discovered something pretty awesome. In the last…
A practical guide to building fast web applications in the cloud
This post originally appeared on loige.co, written by Luciano Mammino. Luciano is a web developer & entrepreneur from Italy. In this article, Luciano highlighted some of the most common principles you should consider while building high performing web applications (specifically on the backend part). The following concepts discussed here can be applied to any language and framework.…
Designing a language switch: Examples and best practices
Building a global SaaS product isn’t easy. You have to localize your product, translate your website, and make sure that everything’s still up and running. And there might be a major interface problem, which looks like a tiny thing at first but is actually something to think about a little longer. What I’m talking about…
Get experts insights & cutting edge ideas for digital product development.
We have asked six experts to bring you lessons learned about user testing and product development.