
Jagadeesh P argues designers should design to learn, not to prove. Rapid prototyping tests real user and product responses. Common mistakes: over-polishing early work, skipping testing, testing the wrong users, and unclear success metrics.

Jagadeesh P argues designers should design to learn, not to prove. Rapid prototyping tests real user and product responses. Common mistakes: over-polishing early work, skipping testing, testing the wrong users, and unclear success metrics.
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.

Comment “ME” if you want to join the next upcoming hackathon — we’ll send you the registration link.

Comment “ME” if you want to join the next upcoming hackathon — we’ll send you the registration link.