The document discusses the top 5 most common mistakes teams make when conducting rapid prototyping. These include: 1) equating prototype testing with usability testing, 2) prototyping the entire solution which can be overwhelming, 3) gathering unreliable feedback through vague questions, 4) testing designs at the last minute which puts "lipstick on a pig", and 5) testing one idea at a time rather than comparing multiple ideas. The presentation provides tips to avoid these mistakes such as focusing prototype testing on specific questions, breaking problems into smaller pieces, asking targeted questions, iterating early and often, and comparing alternative solutions.
Stop Guessing, Start Knowing: The Top 5 Most Common Rapid Prototyping Mistakes
1. The Top 5 Most Common Rapid Prototyping
Mistakes
Teresa Torres Hannah Flynn
With: Moderated by:
TO USE YOUR COMPUTER'S AUDIO:
When the webinar begins, you will be connected to audio
using your computer's microphone and speakers (VoIP). A
headset is recommended.
Webinar will begin:
1:30 pm, PDT
TO USE YOUR TELEPHONE:
If you prefer to use your phone, you must select "Use Telephone"
after joining the webinar and call in using the numbers below.
United States: +1 (562) 247-8422
Access Code: 792-362-232
Audio PIN: Shown after joining the webinar
--OR--
2. Revulytics gives any software producers deep and actionable insight into
who is using their software products and how they are being used, and the
out-of-box analytics that enable them to grow incremental revenue, convert
and retain customers, and make decisions about licensing and cloud
transformation strategies.
3. Click on the Questions panel to
interact with the presenters
www.productmanagementtoday.com/webinar-series/stop-guessing-comma--start-knowing
www.projectmanagementupdate.com/webinar-series/stop-guessing-comma--start-knowing
www.businessinnovationbrief.com/webinar-series/stop-guessing-comma--start-knowing
4. About The Speaker
Teresa is a product discovery coach who helps teams gain valuable insights from their customer interviews, run
effective product experiments, and drive product outcomes that create value for their customers and their
businesses. She teaches teams how to connect the dots between their research activities and their product
decisions, inspiring confidence that they are on the right track. Recent clients include Allstate, Capital One, The
Guardian, and Snagajob.
About The Moderator
Hannah went to The University of Chicago, where she majored in Environmental Studies with a concentration in
Economics and Policy. She now works with Aggregage on social media strategy and webinar production on sites such
as Product Management Today, B2B Marketing Zone, and Customer Experience Update.
5. 5
Placeholder: Your Content Here
• This is the area where you will add your own
slides and content, with provision for Q and A at
the end.
• On the right hand side of screen, there will be a
chat option where you can invite audience
members to pose questions as we go along.
The Top 5 Most Common Rapid Prototyping Mistakes
6. 6
How often do you or your teams prototype?
Photo credit: Rosenfeld Media under CC 2.0
7. 7
How often do you or your teams prototype?
Photo credit: Rosenfeld Media under CC 2.0
Mistake #1:
Equating prototype testing with
usability testing.
8. 8
How often do you or your teams prototype?
Photo credit: Rosenfeld Media under CC 2.0
Mistake #1:
Equating prototype testing with
usability testing.
Viable
Feasible
Desirable
Does
anyone
want it?
Can we
build it?
Should we
build it?
9. 9
How often do you or your teams prototype?
Photo credit: Rosenfeld Media under CC 2.0
Mistake #1:
Equating prototype testing with
usability testing.
Viable
Feasible
Desirable
Does
anyone
want it?
Can we
build it?
Should we
build it?
Mistake #2:
Prototyping the entire solution.
10. 10
How often do you or your teams prototype?
Photo credit: Rosenfeld Media under CC 2.0
Mistake #1:
Equating prototype testing with
usability testing.
Viable
Feasible
Desirable
Does
anyone
want it?
Can we
build it?
Should we
build it?
Mistake #2:
Prototyping the entire solution.
It’s overwhelming.
11. 11
How often do you or your teams prototype?
Photo credit: Rosenfeld Media under CC 2.0
Mistake #1:
Equating prototype testing with
usability testing.
Viable
Feasible
Desirable
Does
anyone
want it?
Can we
build it?
Should we
build it?
Mistake #2:
Prototyping the entire solution.
It’s overwhelming.
Mistake #3:
Gathering unreliable feedback.
12. 12
How often do you or your teams prototype?
Photo credit: Rosenfeld Media under CC 2.0
Mistake #1:
Equating prototype testing with
usability testing.
Viable
Feasible
Desirable
Does
anyone
want it?
Can we
build it?
Should we
build it?
Mistake #2:
Prototyping the entire solution.
It’s overwhelming.
Mistake #3:
Gathering unreliable feedback.
Would you
use this?
What do you
think?
Imagine this
scenario …
13. 13
How often do you or your teams prototype?
Photo credit: Rosenfeld Media under CC 2.0
Mistake #1:
Equating prototype testing with
usability testing.
Viable
Feasible
Desirable
Does
anyone
want it?
Can we
build it?
Should we
build it?
Mistake #2:
Prototyping the entire solution.
It’s overwhelming.
Mistake #3:
Gathering unreliable feedback.
Would you
use this?
What do you
think?
Imagine this
scenario …
Mistake #4:
Testing at the last minute.
14. 14
How often do you or your teams prototype?
Photo credit: Rosenfeld Media under CC 2.0
Mistake #1:
Equating prototype testing with
usability testing.
Viable
Feasible
Desirable
Does
anyone
want it?
Can we
build it?
Should we
build it?
Mistake #2:
Prototyping the entire solution.
It’s overwhelming.
Mistake #3:
Gathering unreliable feedback.
Would you
use this?
What do you
think?
Imagine this
scenario …
Mistake #4:
Testing at the last minute.
Putting lipstick on a pig.
15. 15
How often do you or your teams prototype?
Photo credit: Rosenfeld Media under CC 2.0
Mistake #1:
Equating prototype testing with
usability testing.
Viable
Feasible
Desirable
Does
anyone
want it?
Can we
build it?
Should we
build it?
Mistake #2:
Prototyping the entire solution.
It’s overwhelming.
Mistake #3:
Gathering unreliable feedback.
Would you
use this?
What do you
think?
Imagine this
scenario …
Mistake #4:
Testing at the last minute.
Putting lipstick on a pig.
Mistake #5:
Testing one idea at a time.
16. 16
How often do you or your teams prototype?
Photo credit: Rosenfeld Media under CC 2.0
Mistake #1:
Equating prototype testing with
usability testing.
Viable
Feasible
Desirable
Does
anyone
want it?
Can we
build it?
Should we
build it?
Mistake #2:
Prototyping the entire solution.
It’s overwhelming.
Mistake #3:
Gathering unreliable feedback.
Would you
use this?
What do you
think?
Imagine this
scenario …
Mistake #4:
Testing at the last minute.
Putting lipstick on a pig.
Mistake #5:
Testing one idea at a time.
Avoid “Whether or Not” decisions.
17. 17
How often do you or your teams prototype?
Photo credit: Rosenfeld Media under CC 2.0
Mistake #1:
Equating prototype testing with
usability testing.
Viable
Feasible
Desirable
Does
anyone
want it?
Can we
build it?
Should we
build it?
Mistake #2:
Prototyping the entire solution.
It’s overwhelming.
Mistake #3:
Gathering unreliable feedback.
Would you
use this?
What do you
think?
Imagine this
scenario …
Mistake #4:
Testing at the last minute.
Putting lipstick on a pig.
Mistake #5:
Testing one idea at a time.
Avoid “Whether or Not” decisions.
18. 18
How often do you or your teams prototype?
Photo credit: Rosenfeld Media under CC 2.0
Mistake #1:
Equating prototype testing with
usability testing.
Viable
Feasible
Desirable
Does
anyone
want it?
Can we
build it?
Should we
build it?
Mistake #2:
Prototyping the entire solution.
It’s overwhelming.
Mistake #3:
Gathering unreliable feedback.
Would you
use this?
What do you
think?
Imagine this
scenario …
Mistake #4:
Testing at the last minute.
Putting lipstick on a pig.
Mistake #5:
Testing one idea at a time.
Avoid “Whether or Not” decisions.
Set up “Compare and Contrast”
decisions.
19. 19
How often do you or your teams prototype?
Photo credit: Rosenfeld Media under CC 2.0
Mistake #1:
Equating prototype testing with
usability testing.
Viable
Feasible
Desirable
Does
anyone
want it?
Can we
build it?
Should we
build it?
Mistake #2:
Prototyping the entire solution.
It’s overwhelming.
Mistake #3:
Gathering unreliable feedback.
Would you
use this?
What do you
think?
Imagine this
scenario …
Mistake #4:
Testing at the last minute.
Putting lipstick on a pig.
Mistake #5:
Testing one idea at a time.
Avoid “Whether or Not” decisions.
Set up “Compare and Contrast”
decisions.
20. 20
How often do you or your teams prototype?
Photo credit: Rosenfeld Media under CC 2.0
Mistake #1:
Equating prototype testing with
usability testing.
Viable
Feasible
Desirable
Does
anyone
want it?
Can we
build it?
Should we
build it?
Mistake #2:
Prototyping the entire solution.
It’s overwhelming.
Mistake #3:
Gathering unreliable feedback.
Would you
use this?
What do you
think?
Imagine this
scenario …
Mistake #4:
Testing at the last minute.
Putting lipstick on a pig.
Mistake #5:
Testing one idea at a time.
Avoid “Whether or Not” decisions.
Set up “Compare and Contrast”
decisions.
Let’s Review:
1. Don’t equate prototype testing with usability
testing.
2. Don’t prototype your whole idea.
3. Don’t gather unreliable feedback.
4. Don’t test at the last minute.
5. Don’t test one idea at a time.
21. 21
How often do you or your teams prototype?
Photo credit: Rosenfeld Media under CC 2.0
Mistake #1:
Equating prototype testing with
usability testing.
Viable
Feasible
Desirable
Does
anyone
want it?
Can we
build it?
Should we
build it?
Mistake #2:
Prototyping the entire solution.
It’s overwhelming.
Mistake #3:
Gathering unreliable feedback.
Would you
use this?
What do you
think?
Imagine this
scenario …
Mistake #4:
Testing at the last minute.
Putting lipstick on a pig.
Mistake #5:
Testing one idea at a time.
Avoid “Whether or Not” decisions.
Set up “Compare and Contrast”
decisions.
Let’s Review:
1. Don’t equate prototype testing with usability
testing.
2. Don’t prototype your whole idea.
3. Don’t gather unreliable feedback.
4. Don’t test at the last minute.
5. Don’t test one idea at a time.
Learn.ProductTalk.org
22. 22
How often do you or your teams prototype?
Photo credit: Rosenfeld Media under CC 2.0
Mistake #1:
Equating prototype testing with
usability testing.
Viable
Feasible
Desirable
Does
anyone
want it?
Can we
build it?
Should we
build it?
Mistake #2:
Prototyping the entire solution.
It’s overwhelming.
Mistake #3:
Gathering unreliable feedback.
Would you
use this?
What do you
think?
Imagine this
scenario …
Mistake #4:
Testing at the last minute.
Putting lipstick on a pig.
Mistake #5:
Testing one idea at a time.
Avoid “Whether or Not” decisions.
Set up “Compare and Contrast”
decisions.
Let’s Review:
1. Don’t equate prototype testing with usability
testing.
2. Don’t prototype your whole idea.
3. Don’t gather unreliable feedback.
4. Don’t test at the last minute.
5. Don’t test one idea at a time.
Here’s what students have to say about Product Talk
courses:
• “Was good, actionable content. I was able to utilize
these methods immediately in my real life.”
• “I feel much more confident to try this with real
customers than if I'd just read some blog posts. As you
said in the initial pitch—deliberate practice is how you
learn!”
• “Extremely satisfied with the quality and time length of
the course. Optional reading was great idea. It fits in
neatly with work and is achievable.”
23. 23
How often do you or your teams prototype?
Photo credit: Rosenfeld Media under CC 2.0
Mistake #1:
Equating prototype testing with
usability testing.
Viable
Feasible
Desirable
Does
anyone
want it?
Can we
build it?
Should we
build it?
Mistake #2:
Prototyping the entire solution.
It’s overwhelming.
Mistake #3:
Gathering unreliable feedback.
Would you
use this?
What do you
think?
Imagine this
scenario …
Mistake #4:
Testing at the last minute.
Putting lipstick on a pig.
Mistake #5:
Testing one idea at a time.
Avoid “Whether or Not” decisions.
Set up “Compare and Contrast”
decisions.
Let’s Review:
1. Don’t equate prototype testing with usability
testing.
2. Don’t prototype your whole idea.
3. Don’t gather unreliable feedback.
4. Don’t test at the last minute.
5. Don’t test one idea at a time.
Here’s what students have to say about Product Talk
courses:
• “Was good, actionable content. I was able to utilize
these methods immediately in my real life.”
• “I feel much more confident to try this with real
customers than if I'd just read some blog posts. As you
said in the initial pitch—deliberate practice is how you
learn!”
• “Extremely satisfied with the quality and time length of
the course. Optional reading was great idea. It fits in
neatly with work and is achievable.”
Q&A
24. Don't Miss the Next Session!
Hooked - How to Build Habit-Forming
Products
With Nir Eyal
July 11, 2018
www.productmanagementtoday.com/webinar-series/stop-guessing-comma--start-knowing
www.projectmanagementupdate.com/webinar-series/stop-guessing-comma--start-knowing
www.businessinnovationbrief.com/webinar-series/stop-guessing-comma--start-knowing