storymapping the user experience

113
STORYMAPPING THE USER EXPERIENCE DONNA LICHAW DONNALICHAW.COM @DLICHAW

Upload: donna-lichaw

Post on 21-Apr-2017

26.114 views

Category:

Design


4 download

TRANSCRIPT

Page 1: Storymapping The User Experience

STORYMAPPINGTHE USER EXPERIENCE

DONNA LICHAW DONNALICHAW.COM

@DLICHAW

Page 2: Storymapping The User Experience

TODAY’S AGENDA

Why story? How stories work Developing your stories Applying stories Rules of thumb

Page 3: Storymapping The User Experience

INTRODUCTIONSWho you are What you do Why you are here today

Page 4: Storymapping The User Experience

THE WAY THINGS WERE

Page 5: Storymapping The User Experience

Framew

ork

456

Designing for the Digital Age: Creating Human-Centered Products and Services

Table 16.8. Sketching from a scenario.

Scenario step Sketch Comments

1. Laura takes a call from Mr. Cowell, who needs to make an appointment for his cat to have a tumor removed. Laura finds him in the client list and opens his record to see detail in the client over-view display area, which shows that Mr. Cowell has three cats, one of whom is flagged for follow-up.

cowell,bobcowell,tom

findcowell

client list workspace

fluffy xenaclient

2

13

This first sketch draws upon the organizer/workspace pattern and the data model, which indicates that pets are parts of the client record. The “find” field is understood as a placeholder for some way or ways to locate clients.

2. She looks at the pet overview display area, sees that Xena needs surgery, and confirms with Mr. Cowell that the pro-cedure is for Xena. She clicks to create a new ap-pointment.

cowell,bobcowell,tom

find

includes history, current visit,last visit, prior by date

fluffy xenaclientcat born 7/1/2001gray tabbylast visit

new appt Whoops, better add a toolbar for that “new appointment” button. Notice there’s a little bit of detail about what may be on the screen. The inter-action designer captures an idea for navigating visits, but quickly moves on.

3. She chooses the procedure type in the appointment parameters area. In the best appoint-ment display, the system shows the next several non-urgent appointments for Dr. Harvey, Xena’s usual vet, when the sur-gery and hospital space required for the procedure are also available. She suggests the first couple of dates to Mr. Cowell,

appt forxenatypesurgerywithharvey

tabs within tabs

calendarbest

apptsclients

best

other

Uh-oh … what should happen when that button is clicked? Does it make sense for a cal-endar to live as a tab inside the client record? It seems more like a global tool, so the team decides to have a client screen and calendar screen, with top-level tabs to switch between them. Tabs within tabs are unfortunate, but the team recognizes this as an issue they can solve later and keeps going. Perhaps the client

Page 6: Storymapping The User Experience

Hinman, Rachel. 2012. The Mobile Frontier. New York: Rosenfeld Media. www.rosenfeldmedia.com/books/mobile-design/

Page 7: Storymapping The User Experience
Page 8: Storymapping The User Experience

FLAT FLOWS High bounce rates Low conversion Low activation Low engagement High funnel drop-off

Page 9: Storymapping The User Experience

STORYTELLING

Page 10: Storymapping The User Experience

STORYTELLINGthere’s A Formula For That

Page 11: Storymapping The User Experience

STORYTELLINGMAPPING

Page 12: Storymapping The User Experience

http://www.denofgeek.com/tv/breaking-bad/27141/see-inside-the-breaking-bad-writers-room

Page 13: Storymapping The User Experience

http://www.sundance.tv/series/the-writers-room/photos/the-writers-room-breaking-bad#/9

Page 14: Storymapping The User Experience

Not to be confused with…

Page 15: Storymapping The User Experience

http://www.agileproductdesign.com/blog/the_new_backlog.html

Page 16: Storymapping The User Experience

It’s more like…

Page 17: Storymapping The User Experience
Page 18: Storymapping The User Experience

MAKE THINGS GO

BOOM

Page 19: Storymapping The User Experience

HOW STORY WORKS

Page 20: Storymapping The User Experience

Beginning Middle End

Page 21: Storymapping The User Experience

Hero Goal

Exposition

Page 22: Storymapping The User Experience

Inciting Incident or Problem

Hero Goal

Exposition

Page 23: Storymapping The User Experience

Rising A

ction

Inciting Incident or Problem

Hero Goal

Exposition

Page 24: Storymapping The User Experience

Rising A

ction

Inciting Incident or Problem

Hero Goal

Exposition

Crisis

Page 25: Storymapping The User Experience

Climax or Resolution

Rising A

ction

Inciting Incident or Problem

Hero Goal

Exposition

Crisis

Page 26: Storymapping The User Experience

Falling Action

Climax or Resolution

Rising A

ction

Inciting Incident or Problem

Hero Goal

Exposition

Crisis

Denouement

Page 27: Storymapping The User Experience

End

Climax or Resolution

Rising A

ction

Inciting Incident or Problem

Hero Goal

Exposition

CrisisFalling ActionDenouement

Page 28: Storymapping The User Experience

End

Falling Action

Climax or Resolution

Rising A

ction

Inciting Incident or Problem

Hero Goal

Exposition

Crisis

Denouement

Page 29: Storymapping The User Experience
Page 30: Storymapping The User Experience

EXERCISE

End

Falling Action

Climax or Resolution

Rising A

ction

Inciting Incident or Problem

Hero Goal

Exposition

Crisis

Denouement

Page 31: Storymapping The User Experience

3 STORIES

Page 32: Storymapping The User Experience

CONCEPT STORIES ORIGIN STORIES USAGE STORIES

Page 33: Storymapping The User Experience

CONCEPT STORIES ORIGIN STORIES USAGE STORIES

Page 34: Storymapping The User Experience

Goal MetWho Goal

Value & Competitive advantage

Problem

Product

Name

Market

Catego

ry

TakeawayCompetition

Page 35: Storymapping The User Experience

CONCEPT STORIES Who a product is for Why someone would use it What a product is How it’s better than the competition

ORIGIN STORIES USAGE STORIES

Page 36: Storymapping The User Experience

EXERCISE

Goal MetWho / Goal

Value & Competitive advantage

Problem

Product

Name

Market

Catego

ry

TakeawayCompetition

} Concept Story

Page 37: Storymapping The User Experience

CONCEPT STORIES ORIGIN STORIES USAGE STORIES

Page 38: Storymapping The User Experience
Page 39: Storymapping The User Experience

Collect & ShareCollect imagesShare images

Visual collecting & sharing!

It’s a pain

Discover P

interest

Sign upHomepage Landing page App store Email Ad

Eh

Page 40: Storymapping The User Experience
Page 41: Storymapping The User Experience

Goal metWho Goal

Why they should careproblem solved

ProblemTriggerPainpoint

Discover p

roduct

Action

Word of mouth Paid advertising Google search App store Other channels/touchpoints

Acquisition Activation Conversion Awareness

Measureable

Homepage Landing page App store Email Ad

}

Resistance

Page 42: Storymapping The User Experience

CONCEPT STORIES ORIGIN STORIESWho a product is for Why someone would want to use it How they will discover the product What value/affordances someone should see What action(s) they should take

Page 43: Storymapping The User Experience

CONCEPT STORIES ORIGIN STORIESWho a product is for Why someone would want to use it How they will discover the product What value/affordances someone should see What action(s) they should take

}Target market Problem space Acquisition funnels, Mktg, SEO Requirements, Copy, Assets CTA(s)

Page 44: Storymapping The User Experience

EXERCISE } Origin Story

Goal metWho Goal

Why they should careproblem solved

ProblemTriggerPainpoint

Discover p

roduct

Action

Word of mouth Paid advertising Google search App store Other channels/touchpoints

Homepage Landing page App store Email Ad

Resistance

Page 45: Storymapping The User Experience

Sign up

Collect and share something

Page 46: Storymapping The User Experience

Sign up

Collect and share something

Page 47: Storymapping The User Experience

CONCEPT STORIES ORIGIN STORIES USAGE STORIES

Page 48: Storymapping The User Experience

Goal MetWho Goal

Solve ProblemExperience Value

ProblemIncentiveCTA

FlowFinishFlow

Impediment

Sign up Payment Funnel drop-off (metrics) Mental hurdles Boredom Lack of value Usability

Page 49: Storymapping The User Experience

Inciting Incident

Page 50: Storymapping The User Experience

Rising Action

Page 51: Storymapping The User Experience

Rising Action

Page 52: Storymapping The User Experience

Rising Action

Page 53: Storymapping The User Experience

Crisis

Page 54: Storymapping The User Experience

Climax

Page 55: Storymapping The User Experience

Falling Action

Page 56: Storymapping The User Experience

End

Page 57: Storymapping The User Experience

Home In the KnowWant To Be In the Know

Access + MembershipFriends Are Here?

Sign up

Onboard

ing Flow Finish

FlowBoredom Lack of value

Page 58: Storymapping The User Experience

Inciting Incident

Page 59: Storymapping The User Experience

Rising Action

Page 60: Storymapping The User Experience

Rising Action

Page 61: Storymapping The User Experience

Rising Action

Page 62: Storymapping The User Experience

Crisis

Page 63: Storymapping The User Experience

Climax Falling Action

Page 64: Storymapping The User Experience

End

Page 65: Storymapping The User Experience

MICRO-STORIES AND HABIT LOOPS

Page 66: Storymapping The User Experience

Hours 1 2 3 4 5 6 ∞ Days Months Years

LONG-TERM ENGAGEMENT

Page 67: Storymapping The User Experience
Page 68: Storymapping The User Experience
Page 69: Storymapping The User Experience
Page 70: Storymapping The User Experience
Page 71: Storymapping The User Experience
Page 72: Storymapping The User Experience
Page 73: Storymapping The User Experience

Goal MetWho Goal

Solve ProblemExperience Value

ProblemIncentiveCTA

FlowFinishFlow

Impediment

Sign up Payment Funnel drop-off (metrics) Mental hurdles Boredom Lack of value Usability

Page 74: Storymapping The User Experience

EXERCISE } Usage Story

Goal MetWho Goal

Solve ProblemExperience Value

ProblemIncentiveCTA

FlowFinishFlow

Impediment

Sign up Payment Funnel drop-off (metrics) Mental hurdles Boredom Lack of value Usability

Page 75: Storymapping The User Experience

CASE STUDIES

Page 76: Storymapping The User Experience

DAFFODILS

Page 77: Storymapping The User Experience

RESEARCH & STRATEGY PERSONA 3: The Dutiful Citizen CENTRAL PARK CONSERVANCY

Ben, The Dutiful Citizen NARRATIVE ARCCPC donors tend to fit this profile.

SEVENHEADSDESIGN.COM PAGE OF 36 47

Actio

n &

Exci

tem

ent

Timeline

Gives: “I use the park and should contribute.”

Lives or works near the park.

Loves spending time outdoors.

Asked to donate • Broadcast media • Social media • Mail (paper, email)

Deterrents: • Trust • Intangible ROI • Digital usability • Geographical relevance

Sees: “I can see where my money is going when I’m at the park. I don’t get that with cancer research. I can’t see cells in a microscope.”

Feels ownership and sees utility in Central Park

Goals met: • To be a part of something bigger • To contribute to society by doing their duty

Page 78: Storymapping The User Experience
Page 79: Storymapping The User Experience

RESEARCH & STRATEGY CENTRAL PARK CONSERVANCY

Ben, The Dutiful Citizen CONTENT & FUNCTIONALITYThis content & functionality will help Ben stay informed and remind him to donate.

SEVENHEADSDESIGN.COM PAGE OF 42 47

Actio

n &

Exci

tem

ent

Timeline

Reminders • Signage about

donations in strategic locations throughout park

• Acquisition of e-mail address at time of previous gift, “Remind me to give in the future?”

• Social reminders, e.g. Twitter, Facebook tied to park improvements

• Simplified mobile sign-up for gift reminders (outside of a gift interaction)

Making a Donation • Detailed needs and

associated costs in giving menu

• Focus on what gifts are supporting now in the blog, including recent projects and the Year in Review (beyond the annual report)

• Information about the number and impact of smaller gifts (daffodils)

• Information about where your money goes and where project support comes from

After the Donation • E-mail campaign tied

to specific deadlines • Tangible outcomes,

such as a tote, water bottle, or lunch box

• Deadlines with “blunt language” for donation categories, which explain why the deadline exists

Page 80: Storymapping The User Experience

COMMUNITY ACCESS GIVING

Page 81: Storymapping The User Experience

The Seton Hill University Student Story

Goals met:

• Educated• Job-ready• Community

New student goals:

• To learn• To be job-ready• To be a part of a community

Timeline

Actio

n / E

xcite

men

t / A

wes

omen

ess

Admissions Graduation

Thinks that attending SHU is the

best way to meet her or his goal

Attends SHU

Finds and feels:

Strong sense of communityAccess to faculty/staffSpirit and ethos of giving

Extremely happy with SHU

Feels like a part of SHU

THE STUDENT STORY

Page 82: Storymapping The User Experience

The Seton Hill University Engaged Alumna/us Story

Goals met

NetworkedCommunity

Alumna goals:

• To get a job or extend professional network• To stay connected to her community

Timeline

Actio

n / E

xcite

men

t / A

wes

omen

ess

Graduation ∞

Is asked to volunteer on the board

Participates on the board

Finds and feels:

• Strong sense of community• Access to faculty/staff• Spirit and ethos of giving

Extremely happy with SHU

Feels like a part of SHUStruggles:

• Registering for events online• Finding out news about campus• Accessing faculty/staff• Finding other alumni• Knowing about job opportunities• FB is easier way to meet goals

THE ENGAGED ALUMNI STORY

Page 83: Storymapping The User Experience

Alumna Goals:

• To get a job or extend professional network• To stay connected to her community

The Seton Hill University Differently-Engaged Alumna/us Story

Goals met

NetworkedCommunity

Seeks community of alumni through informal channels: • In-person meetups, meals, coffee• Facebook newsfeed, alumni groups

Timeline

Actio

n / E

xcite

men

t / A

wes

omen

ess

Graduation

Misses SHU community

THE DISENGAGED DIGITAL ALUMNI STORY

Page 84: Storymapping The User Experience

Alumna Goals:• To get a job or extend professional network• To stay connected to her community

Visits website and participatesin digital services

Finds and feels:• Strong sense of community• Access to faculty/staff• Spirit and ethos of giving

Extremely happy with SHUFeels like a part of SHU

The Seton Hill University Future-State Engaged Alumna/us Story

Goals metNetworkedCommunity

Timeline

Actio

n / E

xcite

men

t / A

wes

omen

ess

Supp

ortin

g Th

e St

ory

Graduation

Misses SHU communityBecomes aware of alumni website

Service and EventsPromote opportunities for giving and participation.

Imagery Surface photos of people, places promi-nently throughout.

News Surface achievements and news about people, places.

Virtual Open Door Provide easy access to office staff.

Alumni Database: Provide access to find and update alumni info and job notices.

GAPS & OPPORTUNITIES

Page 85: Storymapping The User Experience
Page 86: Storymapping The User Experience

SPREADSHEETS

Page 87: Storymapping The User Experience
Page 88: Storymapping The User Experience
Page 89: Storymapping The User Experience
Page 90: Storymapping The User Experience

FINDING YOUR STORY

Page 91: Storymapping The User Experience

LOOK

Page 92: Storymapping The User Experience

LOOK

Page 93: Storymapping The User Experience
Page 94: Storymapping The User Experience

AGENDA

‣ INSERT CHAPTER TITLES

94

Page 95: Storymapping The User Experience

LISTEN

Page 96: Storymapping The User Experience
Page 97: Storymapping The User Experience
Page 98: Storymapping The User Experience

USING YOUR STORY

Page 99: Storymapping The User Experience

COMMUNICATE

Page 100: Storymapping The User Experience

WRITE

Page 101: Storymapping The User Experience

ILLUSTRATED

Cheng, Kevin. 2012. See What I Mean. New York: Rosenfeld Media. rosenfeldmedia.com/books/comics/

VISUALIZE

Page 102: Storymapping The User Experience
Page 103: Storymapping The User Experience

VISUALIZE

Page 104: Storymapping The User Experience

VISUALIZE

Page 105: Storymapping The User Experience

ACT IT OUT

Page 106: Storymapping The User Experience

Gap analysis

SWOT analysis

Requirements gathering

Needs assessment

SUPPORT

Page 107: Storymapping The User Experience

STRATEGIZE

Page 108: Storymapping The User Experience

STRATEGIZE

Page 109: Storymapping The User Experience

RULES OF THUMBStories are character-driven

Characters are goal-driven

Conflict is key

Goals are measurable

Goals can change

Page 110: Storymapping The User Experience

WHAT IS THE STORY?

Page 111: Storymapping The User Experience
Page 112: Storymapping The User Experience
Page 113: Storymapping The User Experience

DONNALICHAW.COM | @DLICHAW

THE USER’S JOURNEY