How do you test a new feature idea (hypothesis) in MVP stage?

This would depend on what the hypothesis is and what the risk is... I like to think about the 4 types of risk: - Value risk - is the feature valuable (i.e. will customers use it) - Viability risk - (i.e. does the feature/product can be supported by the support team, are there legal risks, do we have the right business model to sustain it etc?) - Feasibility risk - can we build it fast enough and will it work as we imagine it? - Usability risk - can users use it? do they understand it? In most cases for an early days MVP the biggest risk are: Value and Usability. For value risk common testing approaches I have done: landing page tests (create a landing page for the feature / product and send traffic to the page and measure conversion), user interviews and wizard of oz testing. For usability risk - both moderated and unmoderated prototype testing always works If you don't have users or your users are non responsive the biggest challenge is to get hold of user: - I have recruited users by reaching out on social media - I have used user recruitment agencies - I have done guerilla testing: going to where potential users are and approaching them in real life - stressful but fun!

We set up a targeted landing page that outlines the proposed feature's benefits and uses Google Ads to drive relevant traffic to it. Additionally, we conduct outreach to gather direct feedback from potential users, which helps validate the interest and viability of the feature

The MVP stage is like the laboratory of your startup, where you can get pretty creative with testing new feature ideas. At JetSoftPro, a software development service, we release the feature to a small, enthusiastic group of users who are open to experimentation. Their feedback can be a goldmine for refining your hypothesis before scaling up. Here is the article that might be valuable for you: https://jetsoftpro.com/blog/supe...