5. STORY BOARD
A panel or series of panels of rough sketches
outlining the sequence of events
a customer will experience
before, during, and after using our product.
15. PROBLEM
• I am trying to: ____________
BUT ____________________
• Prior to use
• CAREFUL: Don’t insert your
solutions as the problem
Problem Problem
16. PROBLEM
Problem Problem
• I am trying to: ____________
BUT ____________________
• Prior to use
• CAREFUL: Don’t insert your
solutions as the problem
17. PROBLEM
Problem Problem
• I am trying to: ____________
BUT ____________________
• Prior to use
• CAREFUL: Don’t insert your
solutions as the problem
3
min
I’m trying to offer credit card payments,
but I can’t afford monthly payments for traditional CC service
18. SOLUTION
• What are the important
moments that need to occur
for the solution to execute
• “Trigger Moments”
Solution Solution
19. SOLUTION
• What are the important
moments that need to occur
for the solution to execute
• “Trigger Moments”
4
min
Solution Solution
Smartphone app & reader device to accept POS transactions
and online service for transaction ledger & reports
20. BENEFIT
• What would a customer say is
great about your solution.
• Do not regurgitate the feature
list.
Benefit
21. BENEFIT
• What would a customer say is
great about your solution.
• Do not regurgitate the feature
list.
3
min
Benefit
Customers are now happy they can pay by credit card.
Café owner finds the app easy to use and increased productivity.
22. LEARNING
• Goal:
Gather as much new
feedback as possible
Customer
Problem
Do you understand the problem?
Is it an important problem?
Solution
Does your solution solve the
problem completely?
Customer
Benefit
What is good about your idea
from the user’s perspective?
23. LEARNING
• Goal:
Gather as much new
feedback as possible
What is the familiarity of the Café Owner & employees with
Smartphone applications?
Customer
Problem
Do you understand the problem?
Is it an important problem?
Solution
Does your solution solve the
problem completely?
Customer
Benefit
What is good about your idea
from the user’s perspective?
36. My Example Storyboard
Handheld device, credit card processing
Café Owner & Employees
Cash
Only
?
Easy Set-up & Configuration
Process
Frustrated Customers b/c
can only pay with cash
Limited budget to afford
traditional CC processing
Employees use reader device
& smartphone for transactions
Café Owner can see ledger
& generate reports online
Café Owner’s & employee familiarity with smartphone apps?
Customers can pay with
credit cards, revenue increase
Start with an hypothesis and use wireframes through storyboards to explore the story.Try to get more honest feedbackGo broad to go narrow – a funnelRapid experimentation with customers
For this presentation, we will refer to a storyboard as a panel or series of panels of rough sketches outlining the sequence of events a customer will experience before, during, and after using our product.
Our basic structure for the storyboard to tell the end-users’ storyFocus on the idea / concept, not the artwork3-4 bullet points will go into each cell block
What actually is the end-users’ problem, prior to use?Do you understand the problem?Is it an important problem?
Mad Lib: I’m trying to (insert end-users’ goal), but (insert end-users’ problem)
Mad Lib: I’m trying to (insert end-users’ goal), but (insert end-users’ problem)
Does the solution solve the problem completely?What are the important, “trigger” moments that need to occur for the solution to execute?
Does the solution solve the problem completely?What are the important, “trigger” moments that need to occur for the solution to execute?
What is good about your idea from the users’ perspective?What would a user say is great about your solution? (Do not repeat the feature list)If they are currently using something else, would they switch to your solution? Would they never go back to their previous solution?
What is good about your idea from the users’ perspective?What would a user say is great about your solution? (Do not repeat the feature list)If they are currently using something else, would they switch to your solution? Would they never go back to their previous solution?
What do you want to learn about this?Which components are you concerned about?Which components do you feel need further exploration?
What do you want to learn about this?Which components are you concerned about?Which components do you feel need further exploration?