Difference between revisions of "UX 모임 2018-08-06"
From Lyndsey Twining
(→린지) |
(→Understanding user needs 사용자의 필요에 대한 이해) |
||
(2 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
+ | * [[UX 모임]] | ||
+ | |||
==자료 리뷰== | ==자료 리뷰== | ||
− | ===린지 : EdX 코스=== | + | ===린지 : EdX 코스 - Design Thinking: UX and Advanced Topics (Microsoft)=== |
+ | *[https://courses.edx.org/courses/course-v1:Microsoft+DEV318x+1T2018/course/ Link] | ||
+ | |||
+ | ====Understanding user needs 사용자 요구 이해==== | ||
+ | |||
+ | *Interviews | ||
+ | *Organizing Data | ||
+ | **Affinity diagrams | ||
+ | **Word clouds | ||
+ | **Task modeling | ||
+ | **Customer journey maps | ||
+ | **Personas/market segments | ||
+ | *Metrics and Telemetry | ||
+ | **Sankey diagrams | ||
+ | *Other inputs | ||
+ | *BXT model | ||
+ | **Business, experience, technology - is there a viable market? Will the tech serve? | ||
+ | *Measurable design goals | ||
+ | **Formulating | ||
+ | ***Based in user research and market research data | ||
+ | ***Realistically achievable | ||
+ | ***Measurable in terms of user behavior and attitude | ||
+ | **Scenarios/jobs to be done | ||
+ | **Emotions | ||
+ | ***Donald Norman: Useful, usable, desireable | ||
+ | |||
+ | ====Exploring solutions 해결책 담구==== | ||
+ | |||
+ | *Brainstorming techniques | ||
+ | **HMWs - How Might We? | ||
+ | ***[http://crowdresearch.stanford.edu/w/img_auth.php/f/ff/How_might_we.pdf How Might We?] | ||
+ | **Inclusive design | ||
+ | ***Storyboarding | ||
+ | *Information architecture | ||
+ | **Sketching UI | ||
+ | ***Card sorting | ||
+ | ***Site map | ||
+ | ***Navigation controls | ||
+ | *Layout | ||
+ | **Layout | ||
+ | **Sample grid | ||
+ | ***Visual hierarchy | ||
+ | ***Typography | ||
+ | ***Type ramp | ||
+ | *Wireframing | ||
+ | **Wireframing | ||
+ | ***Stay away from color, focus on info and visual hierarchy | ||
+ | **Flow charting | ||
+ | **Prototyping | ||
+ | |||
+ | ====Calibrating the design 디자인 수정==== | ||
+ | *User testing protocols | ||
+ | **Collaborative design | ||
+ | ***Paper prototypes are useful - testers can rearrange things | ||
+ | **In person moderated testing | ||
+ | **Focus groups | ||
+ | **Remote moderated/unmoderated | ||
+ | *Assessing the data you've collected | ||
+ | **Issues matrix - what problems did each tester encounter | ||
+ | *Update wireframes and prototypes | ||
+ | **[https://www.justinmind.com/blog/whats-the-difference-between-wireframes-and-prototypes/ Difference between wireframes and prototype] | ||
+ | |||
+ | ====Finishing the design 디자인 완료==== | ||
+ | 실제적인 앱 디자인에 대한 팁 / Engineer 팀이 따로 있다는 관점으로 설명함 | ||
+ | |||
+ | *Branding | ||
+ | *Color | ||
+ | *Images | ||
+ | *Motion | ||
+ | *Whitespace/content balance/clarity | ||
+ | *Visual hierarchy and how the eye accepts information | ||
+ | *Common "visual affordances'' | ||
+ | **[https://developer.mozilla.org/en-US/docs/Learn/HTML/Forms/The_native_form_widgets]] | ||
+ | *UX design trends and best practices | ||
+ | *Validating the finished design | ||
+ | *Documenting the finished design | ||
+ | *Testing the design throughout development | ||
+ | *Collecting and analyzing telemetry on the released design | ||
===현규 : 콘텐츠 UX 디자인=== | ===현규 : 콘텐츠 UX 디자인=== | ||
Line 27: | Line 106: | ||
===선애=== | ===선애=== | ||
+ | |||
+ | ==과제== | ||
+ | *이론 정리하는 방법에 대한 이야기 |
Latest revision as of 18:15, 6 August 2018
Contents
자료 리뷰
린지 : EdX 코스 - Design Thinking: UX and Advanced Topics (Microsoft)
Understanding user needs 사용자 요구 이해
- Interviews
- Organizing Data
- Affinity diagrams
- Word clouds
- Task modeling
- Customer journey maps
- Personas/market segments
- Metrics and Telemetry
- Sankey diagrams
- Other inputs
- BXT model
- Business, experience, technology - is there a viable market? Will the tech serve?
- Measurable design goals
- Formulating
- Based in user research and market research data
- Realistically achievable
- Measurable in terms of user behavior and attitude
- Scenarios/jobs to be done
- Emotions
- Donald Norman: Useful, usable, desireable
- Formulating
Exploring solutions 해결책 담구
- Brainstorming techniques
- HMWs - How Might We?
- Inclusive design
- Storyboarding
- Information architecture
- Sketching UI
- Card sorting
- Site map
- Navigation controls
- Sketching UI
- Layout
- Layout
- Sample grid
- Visual hierarchy
- Typography
- Type ramp
- Wireframing
- Wireframing
- Stay away from color, focus on info and visual hierarchy
- Flow charting
- Prototyping
- Wireframing
Calibrating the design 디자인 수정
- User testing protocols
- Collaborative design
- Paper prototypes are useful - testers can rearrange things
- In person moderated testing
- Focus groups
- Remote moderated/unmoderated
- Collaborative design
- Assessing the data you've collected
- Issues matrix - what problems did each tester encounter
- Update wireframes and prototypes
Finishing the design 디자인 완료
실제적인 앱 디자인에 대한 팁 / Engineer 팀이 따로 있다는 관점으로 설명함
- Branding
- Color
- Images
- Motion
- Whitespace/content balance/clarity
- Visual hierarchy and how the eye accepts information
- Common "visual affordances
- [1]]
- UX design trends and best practices
- Validating the finished design
- Documenting the finished design
- Testing the design throughout development
- Collecting and analyzing telemetry on the released design
현규 : 콘텐츠 UX 디자인
선애 : 좋아보이는 것들의 비밀
Semantic Cocktail 평가
린지
- 실제적인 사용자가 바텐더 시험 보려고 하는 사람, 칵테일 만들고자 하는 사람이다.
- 뒤로 갈 수 없다
- 메인 페이지는 칵테일 IBA 카테고리로 시작하는데 칵테일 만드는 사람에게 별 의미 없고 이 3가지 카테고리에 대한 설명이 없다.
- 재료, 맛, 색깔, 등으로 시작하는 것이 사용자에게 더 펼리하겠다.
- 비슷한 칵테일 검색, 맛, 분위기, 색깔, 어려움 레벨, 언제 마시면 좋은지, 어떤 음식하고 어울리는지 등이 없어서 아는 사람만 정보를 찾을 수 있다.
- 관계 라벨은 한국어나 일반 영어로 되어 있었으면 좋겠는데 id처럼 되어 있어서 불편하다.
다른 예시
현규
선애
과제
- 이론 정리하는 방법에 대한 이야기