Interview frequency: …
Short answer
It is an iterative process: build a quick prototype with minimal effort, test it with real users immediately, and learn from the results to improve the idea in short successive rounds.
Explanation
The goal is not to make a perfect prototype, but to answer a specific question or validate a hypothesis as quickly as possible (fail fast and cheap). Instead of spending two months preparing theoretical specifications, the team creates a prototype in two days, tests it with five users on the third day, and analyzes the results on the fourth to decide whether to pivot or continue developing the idea.
Common mistakes
- Treating the prototype as final, shippable code, slowing down iteration and experimentation.
- Ignoring test results and keeping a design only because the team invested a lot of time in it.