week 06 analyzing contextual data

Lecture 6

Analyzing Contextual Data

UX Prototyping / IID 2015 Spring Class hours : Tuesday 2 pm – 6 pm Lecture room : International Campus Veritas Hall B320 7th April

The Last Week’s Homework

Lecture #6 IID_UX Prototyping 2

Complete Probe Toolkits

Execute Cultural Probe Research &

Report the Results

Readings And Critiques

(Assign

Presenters for Each Paper)

1 2 3

Your Blog Post #9 - Complete your

Cultural Package Toolkit Design

- Upload the images

Your Blog Post #11 - Recruit 5 participants for

each group.

- Collect responses and get returns from the Participants.

- After the team discussion over the package returns, summarize, analyze, and interpret the results.

- Set a contextmapping session plan.

Your Blog Post #12 - Summarize the papers - Add your critiques for each

papers

Reading List

• Week 06 Reading

– Mark A. Blythe, & Peter C. Wright (2006) "Pastiche scenarios: Fiction as a

resource for user centred design," Interacting with Computers, Volume 18,

Issue 5, pp. 1139–1164.

– Pam Briggs, et. al. (2012) "Invisible Design: Exploring Insights and Ideas

through Ambiguous Film Scenarios," Proceedings of DIS 2012, June 11-15,

2012, Newcastle, UK.

– Mark Blythe (2014) "Research Through Design Fiction: Narrative in Real

and Imaginary Abstracts," Proceedings of CHI 2014, April 26 - May 01 2014,

Toronto.


To Do List for Today

• Seminar

– Core Research Ideas : Bring out some keywords or related technological

trends, backgrounds, and concerns

– Research Questions : What they investigated

– Key theories : Some they referred and some they developed by their own

– Method : How they proved

– Results & Findings : What they learned from the study



• Present your system concept statements (10 Minutes of Warm-up discussion, and Be Ready)

– Collected Pinterest Images/Make Group Pinboards

• Users

• Objects

• Interactions

– Overview

• Team Title

• The Revised System Concept Statement (especially the team that changed its project)

– 5 components of a system concept statement

• Project Title

• Users

• Critical Functions

• System Goals

• Target UX (emotional/social/cultural)



• Today’s Team Presentation

– Introduce 5 participants

– Summarize responses and get returns from the Participants.

– Learnings from the results

• Any changes on your system concepts?

• Any changes on your persona?

– Present your team’s contextmapping session plan.


USER STORY MAPPING Workshop #3 Analyzing Contextual Data


Jeff Patton (2014) User Story Mapping, Cambridge : O’Reilly.

Change-the-World


The truth is, your job is to change the world.

Change-the-World Model


Now and Later

• The model starts by looking at the world as it is now.

– When you look at the world as it is now, you’re going to find people who

are unhappy, mad, confused, or frustrated.

– Now, the world’s a big place, so we’ll focus mostly on the people who use

the software we make, or the people we hope will use it.

– When you take a look at what they’re doing—and the tools they use and

how they’re doing things—you’re going to come up with ideas, and the

ideas might be for:

• Entirely new products you can build

• Features to add to an existing product

• Enhancements to products that you’ve built


Now and Later

• Later,

– they’re not happy because they saw the pretty box it came in—software

doesn’t usually come in boxes these days anyway.

– They’re not happy because they read the release notes, or downloaded

the app to their mobile device.

– They’re happy because when they use the software, or the website, or the

mobile app, or whatever you’ve built, they do things differently— and

that’s what makes them happy.


Software Isn’t the Point

• Impact

– It’s that longer-term stuff that happens as a consequence of good

outcomes that’s I’ll label impact. Outcomes are often something you can

observe right away after delivery. But impact takes longer.


Build Less


There’s always more to build than we have time or resources to build—always.

Minimize output, and maximize outcome and impact.

Let’s get started


Think — Write — Explain — Place

• Get in the habit of writing down a little about your idea before

explaining it.

1. If you’re using cards or sticky notes, write down a few words about your

idea immediately after thinking it.

2. Explain your idea to others as you point to the sticky note or card. Use big

gestures. Draw more pictures. Tell stories.

3. Place the card or sticky into a shared workspace where everyone can

see, point to, add to, and move it around. Hopefully, there will be lots of

other ideas from you and others in this growing pile.


Frame Your Idea


Describe Your Customers and Users


Mapping your story helps you find holes in your thinking.


Reorganizing cards together allows you to communicate without saying a word.

Explore Details and Options


The Backbone


The Map Loaded with Ideas


Talking Through Each Activity


Prioritizing


Plan to Build Less


Narrative Flow


Slice Out a Minimum Viable Product Release


Slice Out a Release Roadmap


Finding a Smaller Viable Release

• After the story map was constructed, SEP guided the FORUM

stakeholders through a simple prioritization model:

– Differentiator

• A feature that set them apart from their competition

– Spoiler

• A feature that is moving in on someone else’s differentiator

– Cost reducer

• A feature that reduces the organization costs

– Table stakes

• A feature necessary to compete in the marketplace


Don’t Prioritize Features —Prioritize Outcomes


How to Prototype


OK, LET’S TRY STEP BY STEP


1. Write Out Your Story a Step at a Time


2. Organize Your Story


3. Explore Alternative Stories


4. Distill Your Map to Make a Backbone


5. Slice Out Tasks That Help You Reach a Specific Outcome


That’s It! You’ve Learned All the Important Concepts

• As you built this map you learned that:

– Tasks are short verb phrases that describe what people do.

– Tasks have different goal levels.

– Tasks in a map are arranged in a left-to-right narrative flow.

– The depth of a map contains variations and alternative tasks.

– Tasks are organized by activities across the top of the map.

– Activities form the backbone of the map.

– You can slice the map to identify the tasks you’ll need to reach a specific

outcome.


It’s a Now Map, Not a Later Map


It’s a Now Map, Not a Later Map

• One of the cool things about "now story maps" is that you can build them to better

understand how people work today.

– You just did this to learn how you got ready this morning. You can learn even more if you go

back and add other things to the map. The easy things to add are:

• Pains

– Things that don’t work, parts people hate

• Joys or rewards

– The fun things, the things that make it worth doing

• Questions

– Why do people do this? What’s going on when they do?

• Ideas

– Things people could do, or that we could build that would take away pain, or make the joys even better

• Lots of people in the user experience community have been building these for years to

better understand their users.

– Sometimes they’re called journey maps, but they’re the same basic idea.


Customer Journey Map Canvas


http://files.thisisservicedesignthinking.com/tisdt_cujoca.pdf



Journey Map Example


Next Week Reading List

• Download From YSCEC > User Experience Prototyping > Books &

Papers > Week 07 Reading

– Jeffrey Heer & Peter Khooshabeh (2004) "Seeing the Invisible" in

Workshop on Invisible & Transparent Interfaces, Advanced Visual

Interfaces.

– Kasim Rehman, Frank Stajano, & George Coulouris (2002) "Interfacing with

the Invisible Computer," Proceedings of NordiCHI, October 19-23, 2002,

Arhus, Denmark.


Homework


Complete Your Contextmapping

Phase, and Report the results

Readings And Critiques

(Assign

Presenters for Each Paper)

Midterm Presentation

1 2 3

Your Blog Post #13 - Complete your

Contextmapping session.

- Organize the session outputs

- Make the user stories

Your Blog Post #14 - Summarize the papers - Add your critiques for each

papers

Your Blog Post #15 - (1) System Concetp Statement - (2) Persona Design - (3) Cultural Probe - (4) Contextmapping - (5) User Story Map

Submission Due : 11: 59 pm Sun. 12th April

week 06 analyzing contextual data

Education

world lecture

world model lecture

study lecture

contextual data lecture

pm lecture room

weeks homework lecture

system concept statements

system concepts