Photo by Austin Distel on Unsplash

Product validation is a vital aspect in software development. After a long journey of user research, problem and market validation, and most importantly development, you finally have a working product. Validating your product means getting meaningful feedbacks and using them to improve your product in the next iterations. In Agile, this is usually done on the Sprint Review meeting, where the team presents a demo of the product to the stakeholders. That said, there are other techniques you can use to validate your product. They will be explained in this article, along with their strengths and weaknesses.

Product Demo

However, the users don’t get an actual experience of using the product itself, so the feedbacks may be limited. Not to mention that the users’ view of the product may be biased because they’re influenced by how the presenter demonstrates the product.

Direct Observation

The main disadvantage of direct observation is that it takes a long time to observe multiple users. There’s also the possibility of the users acting differently as they’re being watched by someone else, also called the observer effect.

Usability Test

That said, users may act differently since they’re performing tasks in an artificial environment. The observer effect also applies to this technique.

Release

One drawback of this technique is since you don’t observe the users directly, you don’t get to learn about why they use the product or why they don’t. It also takes time because people need to install and use the product for you to be able to gather relevant data.

Spike

On the downside, focusing more on how to build a product can result in an overkill prototype without making real progress on the actual product.

Conclusion

References

CS Student