Human centered design process

958 views
787 views

Published on

This is the human-centered design process lectured by drhhtang. The process is designed for 4 days workshop.

Published in: Education, Technology
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
958
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

Human centered design process

  1. 1. HUMAN-CENTERED DESIGN PROCESS drhhtang ditldesign.sqsp.com DITL@NTUST
  2. 2. MULTIDISCIPLINARY COLLABORATION • 2002~Now Scenario DK Workshop、台灣創意中⼼心、⽣生產⼒力中⼼心 ⻑⾧長庚養⽣生⽂文化村、研華科技、⻑⾧長庚資⼯工、台⼤大⼟土⽉⽊木、北科光電、新光醫院睡眠 中⼼心、駟⾺馬科技、宏正科技、賽微科技、台⼤大資⼯工、⼼心路基⾦金會、全⼈人基⾦金 會、⻑⾧長庚兒童⼼心理、⼯工研院網通所、⼯工研院服科中⼼心、台科⼤大電機、友達光 電、台⼤大職能治療 >30 Scenario Workshop at school and in industry
  3. 3. HCD • Human-Centered Design • Best Practices for Innovation promoted by IDEO • Learner, Practitioner,Advocator
  4. 4. MULTIDISCIPLINARY • Very Important Issue for future education • As a person • DaVinci -Type of person (Dyson) • T - Shaped person (IDEO)
  5. 5. ATTITUDES • Friendly & Kinds / the best partners you can get inTaiwan • Communicate • 溫柔的說出你的想法與⽴立場 • 分⼯工+合作 才能完成這堂課多樣的作業要求。
  6. 6. 如何讓自己成為 一位善於合作的members? Na#onal  Taiwan  University  of  Science  and  Technology Department  of  Commercial  Design  &  Industrial  Design
  7. 7. 首先,你需要一個題目。 以自己的設計為開端 以團隊合作為開端 &
  8. 8. 這是一個十分難得的機會, 可以實際的運作與練習如何 跨領域合作。 以團隊合作為開端...
  9. 9. 每一個組員, 都是設計師。
  10. 10. 共同傾聽 與創作。
  11. 11. 善用工具, 作為彼此溝通的方式。
  12. 12. 各有所長, 能力互補。
  13. 13. 最重要的是, 當一個好人。
  14. 14. 設計師或許會找到一個有趣 的題目,可以天馬行空的發 想與設計。 以自己設計為開端...
  15. 15. 不要停下你的創造力。
  16. 16. 讓點子實現, 尋找你的工程夥伴。
  17. 17. 介紹你的點子, 讓他們產生興趣。
  18. 18. 善用工具 呈現你的概念。
  19. 19. 你要記住兩個字... 不管是單打獨鬥或是團隊合作,
  20. 20. 效率 不要讓你的組員陪你熬夜, 出席與開會的狀態都要專注。
  21. 21. UOID COURSE SETTING
  22. 22. GROUPING & UNGROUPING • 3~8 members are suggested by experts • A 5 members group is the best based on our experience • designers with different backgrounds • IT students with similar developing experience
  23. 23. IDEAS SPEAK • Group Discussion, 2, 4, 5 • Leaders are those who have the best ideas • The members of a groups that does not have good ideas yet will be ungrouped. • from 20 to less than 8 groups
  24. 24. HEAR CREATE DELIVER PROCESS
  25. 25. HEARING
  26. 26. HCD QUALITATIVE HEARING • Develop deep empathy for people we are designing for • Propose assumptions as design objectives • Inspiring new solutions • Examining design quality and verify assumptions • Generative to evaluative
  27. 27. REASONS FOR HEARING • Because we cannot assure the team know the universe of the participants • Unveil people’s behavioral, mental, political, economic, social, cultural opportunities and barriers in their own words • Map the relational dynamics between people, events, time, places, objects • Deep understanding not broad coverage, ex. extreme users
  28. 28. USINGVERB AND HOW CAN • How can we get children with autism to adopt digital learning environment ? • How can we create an APP that help children with autism to learn digitally ? • Create the design challenge for your team in the first month • Observing users / Recognizing existing knowledge and documenting inTumblr • Desirability, Feasibility,Viability • Social, Economic,Technological
  29. 29. CONTENT OF HEARING • People’s stories • Observation of the reality • Deep understanding of needs, barriers, and constraints
  30. 30. TARGET USER
  31. 31. TARGET USER II 。
  32. 32. TARGET USER • Think about the representative users of the target product • Using 5W1H to render the target users, the character, problem, and needs will be more clear • Include CRITICAL ISSUES and KEY IDEAS
  33. 33. Who needs what-sentence because reason-sentence 使⽤用者需要可以選擇⼀一起出遊的夥伴,因為家⼈人朋友有不同的規劃。 UXR Results ---- UXD ideas MAIN STRUCTURE
  34. 34. DESIGN CHALLENGE Creating assisting or supportive APPS that are needed and appropriate for underprivileged people inTaiwan
  35. 35. IDENTIFYYOUR DESIGN CHALLENGE • Framed in human terms instead of object terms • 幫助誰做什麼事的APP • Broad enough to allow you discover the areas of unexpected values • 筆記本 • Narrow enough to make the topic manageable • 愛⼼心⽶米其林
  36. 36. KEY IDEA GENERATION • Using the 30 issues to develop 8 product ideas • Discuss and vote for the best from the 8 product ideas • TOP 8 Product Ideas should include 5 positive + 3 negative • Some details could be added to the ideas. • Please mark the relationships to the original macro FORCES • Text and graphics are both fine 11Scenario Design Process
  37. 37. DECIDEYOUR DESIGN BRIEF
  38. 38. BASIC FUNCTION AND NEEDS • Brainstorm the functions and needs of the primary idea of your company • Who might be the users • brainstorming again the details with your imagination 12
  39. 39. RECOGNIZE EXISTING KNOWLEDGE
  40. 40. USING TUMBLRTO RECORDTHE DETAILS OFTHE DESIGN PROCESS
  41. 41. IDENTIFY PEOPLETO SPEAK WITH • Brainstorming abut the characters • Average users and extreme users • Group
  42. 42. HEAR AGAIN / UXR •顧客洞察者的⽥田野⼿手冊,經濟部技術處 •IAN 遊⽯石演講 下星期⼆二下午1:30~4:30 RB309
  43. 43. CHOOSE RESEARCH METHODS • IDEO Method Cards • Individual Interview • no more than two interviewers • without an audience • interviewer, note taker and photographer
  44. 44. CHARACTER MAPPING • Except the representative user, please generate other target users to think about the range of user characters • Group work/ one user per participants
  45. 45. SCENARIO BRAINSTORMING I • Choose one representative for the team • Using scenario brainstorming sketches (情境腦⼒力激盪圖) to develop details about the relationships between user and product and additional functions • Example: the shopping process and related CI & KI ofTAO(陶美惠)
  46. 46. SCENARIO BRAINSTORMING II
  47. 47. EVENT FLOW • Using 5W1H to thank about Event Situation & Flow Chart • Try to generate a serial process of an event • Group work/ one user per participants 37
  48. 48. time time time time time event event event event event WHO Design
  49. 49. PERSONA
  50. 50. Copyright © 2007 Molecular, Inc. | www.molecular.com | Linked by Isobar 58 Persona Document
  51. 51. Copyright © 2007 Molecular, Inc. | www.molecular.com | Linked by Isobar 59 Persona Cards
  52. 52. STORYBOARD
  53. 53. STORYBOARD I Each slot of flow chart could be a storyboard Please generate 10 storyboards where we can see event sketches, and related CI & KI PLEASE USE PHOTOS OF REAL PEOPLE 41Scenario Design Process
  54. 54. STORYBOARD II • All the storyboards of the targets users together could help us to think about the details and different dimensions of the idea • Different storyboards verify the necessary of the idea as well.
  55. 55. P.O.I.N.T NARROWING • Problem • Obstacles • Insights • Needs: thinking about users’ needs by character mapping, situation brainstorming, event flow, storyboards, • Themes
  56. 56. MID-TERM PRESENTATION • 20 minutes • Team Name and Members • Design Theme • Problems, based on real users • Character Mapping • Personas • Real users / Patterns, based on the insights of your observation and interviews • 10 Most important Problems and 10 most important solutions from 50~60 storyboards, including problems and solutions A4 storyboards + poster • 10 MINS PLAY + PROTOTYPE

×