Presenter Jagadeesh P argues designers should "design to learn" rather than to prove, framing prototyping as a product’s "nervous signal" that reveals real user and system responses. He lists common mistakes—over-polishing early prototypes, skipping testing or iterations, testing wrong user segments, and lacking clear success metrics—and promises to explain what testing is, how to improve it, and various testing types.
Don't design to prove, design to learn. Prototyping is your product's nervous signal. Testing how the fast really responds, how the customer really responds to an interaction, what you've designed, how a product is very well synchronizing to the human need. If you're someone who is not knowing how to make the prototypes in rapid way, let me tell you, this is a big, big skill which a designer needs to learn. But the problem is over. Polishing early prototypes, making it very perfect, ignoring the testing part, skipping the iteration after the feedback, testing with the wrong user segment, not knowing what success metrics to really test it out. These are all the big problems designers face in this video I'm going to be telling about. What is this testing, how we can able to improve this, what are all the types of testing and how we can do it perfectly with that. Let's jump into the stuff.