Accelerating Product Discovery with “No Code” Tools
The process of Product discovery helps to answer critical questions of product teams,
- Are we building product which people need (Desirability)?
- Will people be willing to pay for our product (Viability)?
- Is this possible for us to build this product (Feasibility)?
Once the answer to these questions is YES, then the next questions came to like,
- Is this user experience is right for customers?
- What difficulties will you face during the completion of task A?
- What other problems are they facing which are essential for them to solve?
The list of questions goes on.
Role of Software Development Tools in Product Discovery
Old fashioned product companies try to guess the solution and build products on assumptions. The majority of times, they fail.
Smart teams have figured out that the best way to get answers to these questions is to ASK FROM the customers, validate the assumptions and then invest in building the right product.
There is no standard way for product discovery, from problem space to market space, from the stage of the product to market conditions, there are different ways to validate and proceed ahead.
For technology products, one common thing is “Prototyping,” where teams build various prototypes of their technology product, present to customers, get their feedback and iterate it.
For years, the following process has been relatively driven by technology teams by software engineers. It was cost-intensive to make a real working prototype and then test the whole idea and iterate on top of it.
How we shifted to 3X faster experimentation
Recently, I had been helping a growing product where they were doing 5–8 tests weekly.
We found these tests are not sufficient, and we had a growing backlog of hypothesis to tests.
Additionally, our tests were mainly based on Wireframe / Screenshots reviews by customers. Customers could not see the complete picture of a process and wanted to show full working apps for reliable feedback.
Building up a complete user experience and app is expensive!
We had been listening to “NO CODE” for quite some time and never tried it. So, we thought, let’s give it some try and build few prototype apps using no-code tools.
We used “Glide App” to build our prototype MVP — a true one without writing a single line of code within one day.
We went to customers for reviews and started updating the prototype within hours rather than weeks or days.
We shifted from a maximum of 10 experiments per week to an average of 30 experiments 3X increase in our experimentation process.
Some good, No-Code Tools
Nocode Tools
