Share
Embed
tokyo-tech-dtf-2019-define-pov
Masanori Kado
April 16, 2019
Transcript
40 slides
-
RE-GUIDANCE • Syllabus: https://titech-edp.github.io • Today's Slack Channel: #realtime-20190420 •
It's WELCOME to externally publish (ex. Twitter, Blog, Instagram ) #titech-edp • Homework Submission: #homework-20190406 • Be mode descriptive • Encourage to discuss with Slack and see around other teams' channels • Answering to previous reflections 3 -
① Research → Needs → POV 9 Interview Observation Share
Research Needs POV Model -
"Thick Description" by Clifford Geertz 11 Thick description about the
interview is important but it’s costly. -
SHARE Research Data Efficiently • Share visuals. • If you
took pictures, share them with the rest of the group and talk about why it was interesting. • Use your intuition. • If you could only share 5 thoughts/ideas, what would they be? • Ask questions. • To build shared understanding, everyone else should ask questions about the interview. 12 -
IDENTIFY THEMES & PATTERNS 14 43 episodes / 16 hours
Too many data overwhelm and confuse us -
IDENTIFY THEMES & PATTERNS 15 43 episodes / 16 hours
3 movies / 7 hours Too many data overwhelm and confuse us -
MODEL the Data • a. Focus Verbs, not Nouns •
Extract verbs/jobs/actions/events/ experiences from the data • Model it with "Journey Map”. • b. Empathize the user’s perspective • Deep understand feelings of the user • Model it with “Empathy Map” • c. Look for relationships of the data • Find similar/same(-/=) , cause&effect (→) , opposite(>-<) • Model it with “KJ method” (especially affinity diagram) • d. Pay attention to Mood • Visually present the theme of the data using photos you’ve taken. • Model it with “Inspiration Board” 16 -
a. Journey Map 17 Source: Mapping Experiences by James Kalbach
Published by O'Reilly Media, Inc., 2016 -
Mapping Time Series Activity with Journey Map 18 Verbs /
Jobs / Events / Experiences [WHAT] During After Before Feeling / Thinking / Hear / See / Say [WHY] Tools / Stakeholder / Environment [HOW] -
EDP Toolkit 19 https://titech-edp.github.io/toolkit It would be better to draw
vertically, due to the whiteboard size in Design Factory -
c. Affinity Diagram 21 1. (concrete) Yellow → Blue →
Pink → Green (abstract) 2. similar/same(-/=) , cause&effect (→) , opposite(>-<) Source: Contextual Design, 2nd Edition by Hugh Beyer; Karen Holtzblatt Published by Morgan Kaufmann, 2016 -
c. Guideline of Affinity Diagram • Affinity diagram requires a
sense of editing. (Unfortunately, not everyone has that sense ) • Just like deciding folder name on your computer. • If you have, find unexpected relationships with bottom-up approach and build assumption. • If you don't have, just IGNORE this model ;-) • Choose representative (impressive) data and use it as a label of the cluster. 22 -
d. Inspiration Board(a.k.a. Moodboard) 23 Source: Communicating the UX Vision
by Martina Schell; James O'Brien -
What is ZAWA-ZAWA ? • SFX for liveliness, noise, crowd.
• ref. http://thejadednetwork.com/sfx/browse/zawa_zawa/ • In this class, it's the workings of the human mind, rather than SFX. • It's a famous phrase in "KAIJI" (Manga) • ref. https://en.wikipedia.org/wiki/Kaiji_(manga) • The gap between research data and your mind. • interesting, surprising, strange, weird, etc 25 -
Your ZAWA-ZAWA and the Target User 26 Usual Perspective Unique
Perspective Unique User Usual User -
Your ZAWA-ZAWA and the Target User 27 Usual Perspective Unique
Perspective Unique User Usual User -
Your ZAWA-ZAWA and the Target User 28 Usual Perspective Unique
Perspective Unique User Usual User Early Adopter eXtreme User -
Your ZAWA-ZAWA and the Target User 29 Usual Perspective Unique
Perspective Unique User Usual User Creative Mindset Disruptive Mindset -
Your ZAWA-ZAWA and the Target User 30 Usual Perspective Unique
Perspective Unique User Usual User -
State your ZAWA-ZAWA as user needs 31 (user role) needs
a way to because (verb, jobs, activity) (superficial motivation: Functional/Emotional/Social) (his/her situation) Situation and Context matters -
State your ZAWA-ZAWA as user needs 32 (user role) needs
a way to because (verb, jobs, activity) (superficial motivation: Functional/Emotional/Social) (his/her situation) Focus on user’s VERB -
State your ZAWA-ZAWA as user needs 33 (user role) needs
a way to because (verb, jobs, activity) (superficial motivation: Functional/Emotional/Social) (his/her situation) State Tatemae (trivial reason) at first, which is the source of your ZAWA-ZAWA (feeling strange) -
State your ZAWA-ZAWA as user needs 34 (user role) needs
a way to because (verb, jobs, activity) (superficial motivation: Functional/Emotional/Social) (his/her situation) Verbs / Jobs / Events / Experiences [WHAT] Feeling / Thinking / Hear / See / Say [WHY] Tools / Stakeholder / Environment [HOW] It’s easy way to extract from Journey Map. -
Verbalize you ZAWA-ZAWA as “POV” 36 Define your POV (a.k.a.
Insight) on one or more needs It's better to create two or three POVs. There are totally at least 10 needs, and focus one or more needs. -
DEBRIEF • What are some questions you have about POV
creation? 38 -
Design Challenge • 1. Share Research Data • Share visuals
and Ask questions!! • 2. Model the Data • Journey / Empathy / Affinity / Inspiration • 3. State your “ZAWA-ZAWA” as User Needs (at least 10) • 4. Define Your own POVs (2 or 3 per focused needs) , so that Infer Potential Needs • 5. Presentation • What are the Needs and POVs your team came up with? • How did you arrive that? • What is the hardest thing about “Define POV”? 40 〜13:20:Lunch 13:20〜:Presentation