• Save
User's journey v0.1 i phone
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

User's journey v0.1 i phone

on

  • 2,524 views

 

Statistics

Views

Total Views
2,524
Views on SlideShare
675
Embed Views
1,849

Actions

Likes
3
Downloads
0
Comments
0

25 Embeds 1,849

http://www.adamdsigel.com 1489
http://finchclasses.blogspot.tw 160
http://finchclasses.blogspot.com 112
http://finchclasses.blogspot.hk 19
http://finchclasses.blogspot.ca 18
http://finchclasses.blogspot.co.uk 11
http://cloud.feedly.com 6
http://finchclasses.blogspot.fr 5
http://finchclasses.blogspot.sg 4
http://finchclasses.blogspot.nl 3
http://finchclasses.blogspot.ru 3
http://finchclasses.blogspot.mx 3
http://finchclasses.blogspot.in 2
http://finchclasses.blogspot.com.au 2
http://finchclasses.blogspot.co.nz 2
http://finchclasses.blogspot.kr 1
http://translate.googleusercontent.com 1
http://www.linkedin.com 1
http://finchclasses.blogspot.be 1
http://finchclasses.blogspot.it 1
http://finchclasses.blogspot.se 1
http://finchclasses.blogspot.ch 1
http://finchclasses.blogspot.jp 1
http://finchclasses.blogspot.de 1
http://feedly.com 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

User's journey v0.1 i phone Presentation Transcript

  • 1. Storyboard
  • 2. “Shot List” 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. Persona: a first name for your target user Target: the intended users of your app, i.e. your market segment Pain: the source of the user’s struggles Goal: the desired outcome for the user as a member of the target Qualifier: in one word, what your app delivers better than any other Proof: some form of validation (usually market- or technology-based) for the qualifier Screenshot 1: homepage or splash screen Screenshot 2: in-app shot that conveys user interaction Screenshot 3: in-app shot that conveys user interaction Competitors: 2 to 5 other products that help define your market Partners: 3 to 5 supported services, customers, or partners Name: the names of your team members that are relevant to the user Role: what Name does relative for the user or organization (not always title) Challenge: a misconception about your app (i.e. expensive, hard to learn) and your response Temptation: an alternative perceived as easier (i.e. take no action, go with incumbent) and your response Anxiety: a circumstantial fear (i.e. “boss won’t let me” or “new hardware required”) and your response
  • 3. Your Story
  • 4. Meet <Persona>. <Pain> is keeping <Persona> from <goal>.
  • 5. What if <user goal> for <target> was <qualifier>?
  • 6. Finally, there’s a <qualifier> way to <user goal>. Screenshot 1
  • 7. Your trusted guides Name Team role Name Team role Name Team role
  • 8. For <target> that want to <goal>, <your app> provides <qualifier> <goal> because of <proof>.
  • 9. Apps like us We work with... Screenshot 2
  • 10. ! It’s too <challenge> ! Isn’t it easier to <temptation>? ! But I might <anxiety>
  • 11. Acknowledge <challenge> Refute <temptation> Relieve <anxiety>
  • 12. Screenshot 3 Feature 1 Feature 2 Feature 3 Feature 4 Feature 5 ! Pricing/Availability
  • 13. Are you ready to <goal> without <pain>? Call to Action
  • 14. Now <Persona> is the hero because (s)he can <goal> <qualifier>.
  • 15. (Finally) There’s a <qualifier> way to <goal>. Contact info Screenshot 1