This document discusses lean prototyping for startups. It defines a prototype as an early version of an idea that is testable. Prototyping is recommended to answer questions, validate assumptions, compare alternatives, visualize ideas, and fail early. Good prototypes are quick to create, cheap, minimal, testable, and measurable. The document outlines a process for rapid and cheap prototyping without coding using tools like Keynote, including planning, building screens and interactions, testing with users, refining, and sharing. It promotes not getting attached to early ideas, prioritizing experiments over fantasies, continuous improvement over perfection, and using prototypes to tell stories.

1. Lean
Prototyping
For Startups
Original iPod Prototype

2. What this talk
is about

3. Who am I?

4. 2 short stories
about
prototyping

5. A picture
is worth a
thousand
words
A prototype
is worth a
thousand
pictures

6. What's a
prototype?

8. Early version
of an idea

9. Te s t a ble
Early version
of an idea

10. This is not
a prototype

11. This is not
a prototype

12. This is

14. Why Prototype?

15. To answer
questions
and generate new ones

16. Validate your
assumptions

17. compare
alternatives

18. Fail
early d
an y
ea pl
ch

19. To Visualize
your ideas

20. To Visualize
your ideas
and share them
with others

21. To Visualize
your ideas
and share them
with others
Team users
investors clients

22. So you till you
Fake it make it

23. What makes
a good
Prototype?

24. Quick
You can create multiple versions fast
and iterate even faster!

25. Cheap
You wouldn't mind throwing it away and
starting all over again

26. Favorites Check-in
Chat
Pictures
Minimal
Contains only
core features

27. Testable
You can put it in front of people and have them
try it out
(instead of just telling them about it)

28. Measurable
You can get the numbers behind
what's working and what's not.

29. And hopefully fun to create and use

30. How I Do
Rapi d + Cheap
Prototyping*
*Without writing code

31. 1
Plan

32. Define stories,
and identify tasks

33. Create a user
flow diagram

34. Sketch rough
interface screens
Photo courtesy of StevenVanwel on Flickr

35. 2
Build
Photo courtesy of Mr. T in DC on Flickr

36. Decide what you
want to prototype
Which questions do you want to answer?

37. Main screen
Login screen
Design main screens

38. Create UI states
Update Status
Profile pop-up highlight update

39. Add user interaction

40. 3
Test

41. Test several
prototypes
To get objective feedback

42. Decide what
to measure
To get accurate feedback

43. Choose the
right users
To get relevant feedback

44. Ask them to
think aloud
To get constant feedback

45. Interview them
at the end
To get even more feedback

46. 4
Refine

47. Discuss results
with your team

48. Integrate findings

49. Test again
with users

50. 5
Share

51. Have your
team play
with the
prototype,
instead of
writing long
specification
documents

52. Wh yIp roto type
wi th Ke ynote

53. Design tool
without
feature creep

54. clickable
Fast Slow
Low fidelity High fidelity
Proto types

55. Basic
shapes
The ones you need, without the distraction of
the ones you don't need

56. Alignment
and
Snapping

57. Copy Style
Visual K L
styles K L
Quickly share styles across shapes

58. Master
slides
- Less copy/paste
- Update multiple pages with a
single change

59. Hyperlinks
Add user interaction without writing code

60. Slide
Transitions

61. Export
Hyperlinks are preser ved!

62. Test on
Device
Without doing any extra work

64. Works with
Adobe suite
Copy
Paste

65. Embed product
demos within
your presentations

66. And it costs
less than $20

67. Fi reho se D emo

68. lden Rule s for
5 Go
Pro toty ping
Lean

69. Don't fall in love with
your early ideas

70. If you can't play with
it, it's still a fantasy

71. EVERYTHING
is an experiment

72. Favor kaizen over
perfection

73. Be a good
storyteller

74. Tha nk y ou!
Questions