Quick & Dirty Prototyping - Singapore Lean Startup Circle June Meetup

"If a picture is worth a thousand words, a prototype is worth a thousand meetings". Some practical tips and tools for building a prototype that will help gather invaluable insights from your users and stakeholders.

Transcript

1. QUICK & DIRTY PROTOTYPING FAST AND EFFECTIVE WAY TO GAIN VALUABLE USER INSIGHTS
2. WHO IS THIS GUY? Lee Jun Lin Co-founder, Designer at Minitheory jun@minitheory.com @leejunlin WE CRAFT KICKASS EXPERIENCES
3. WHAT IS HE DOING HERE? §  How we work §  How you can apply some of the techniques we use §  Nothing revolutionary
4. LET'S SAY... §  You've done your initial customer development and idea validations §  You've narrowed down the features in your MVP §  You've decided on what new feature(s) to introduce in your product or service
5. AWESOME! TIME TO BUILD!
6. BUT HOLD ON A SEC... Design and development costs time and money, the two things most startups/entrepreneurs are really short on... Heck! Even big companies have limited budgets sometimes!
7. SO... How do we further test our assumptions? BECAUSE… the sooner we find out which features are worth investing in, the sooner we can focus limited resources on the best solutions to our business problems
8. ENTER THE PROTOTYPE Quick and easy way to get something tangible into the hands of your users/customers
9. ALL PART OF THE CYCLE Prototype!
10. and many more... THERE IS AN ABUNDANCE OF TOOLS
11. YOU WANT TO MAKE YOUR IDEAS REAL… REALLY FAST! And the fastest tools:
12. GETS MESSY REAL FAST!
13. COMPLEMENTARY TOOLS
14. TEMPLATES! http://bit.ly/smtemplates
15. DEMO TIME!
19. PUT IT IN THE HANDS OF YOUR USERS! §  Best results come from testing no more than 5 users and running as many small tests as you can afford §  Testing with 5 users finds 80% of the usability problems - Jakob Neilsen http://www.nngroup.com/articles/why-you-only-need-to-test- with-5-users/
20. KEEP IN MIND WHAT YOU ARE TRYING TO LEARN WITH YOUR PROTOTYPE §  Is there a need for the solution I'm designing? §  Is there value in the solution and features I'm offering? §  Is my solution usable?
21. THERE IS NO RIGHT OR WRONG METHOD DEFINE: §  What you are trying to learn §  What are the main signals you need from your users/customers to validate your hypothesis? §  Are there any other signals you can test for? §  What's the fastest way for you to find this information?
22. THERE IS NO RIGHT OR WRONG METHOD §  Use your prototype as a tool to complement your customer development & research §  See if you can gain new insights from feedback and interactions
23. IMPROVE AND ITERATE!
24. THANK YOU