UX 모임 2018-10-29 - Revision history

Admin: /* 린지 */

2018-10-29T10:04:46Z

‎린지

Admin: /* 린지 */

2018-10-29T08:40:32Z

‎린지

Admin: /* 린지 */

2018-10-29T08:31:15Z

‎린지

Admin at 08:16, 29 October 2018

2018-10-29T08:16:43Z

Admin: /* 린지 */

2018-10-29T08:16:00Z

‎린지

Seonae: /* 선애 */

2018-10-29T07:16:42Z

‎선애

Seonae: /* 선애 */

2018-10-29T07:15:57Z

‎선애

Admin at 04:06, 29 October 2018

2018-10-29T04:06:58Z

Pinocchio: /* 선애 */

2018-10-29T01:21:23Z

‎선애

Seonae at 12:36, 28 October 2018

2018-10-28T12:36:09Z

@@ Line 63: / Line 63: @@
 ==린지==
 *The Five Whys - by Toyota
 **Keep asking why until the root cause it discovered

@@ Line 89: / Line 89: @@
 **Distraction
-===Slips===
+====Slips====
 ''A colleague reported that he went to his car to drive to work. As he drove away, he realized he forgot his briefcase, so he turned around and went back. He stopped the car, turned off the engine, and unbuckled his wristwatch. Yes, his wristwatch instead of his seatbelt.''

@@ Line 90: / Line 90: @@
 ===Slips===
-A colleague reported that he went to his car to drive to work. As he drove away, he realized he forgot his briefcase, so he turned around and went back. He stopped the car, turned off the engine, and unbuckled his wristwatch. Yes, his wristwatch instead of his seatbelt.
+''A colleague reported that he went to his car to drive to work. As he drove away, he realized he forgot his briefcase, so he turned around and went back. He stopped the car, turned off the engine, and unbuckled his wristwatch. Yes, his wristwatch instead of his seatbelt.''
 *memory-slip vs action-slip

@@ Line 89: / Line 89: @@
 **Distraction
-==Slips===
+===Slips===
 A colleague reported that he went to his car to drive to work. As he drove away, he realized he forgot his briefcase, so he turned around and went back. He stopped the car, turned off the engine, and unbuckled his wristwatch. Yes, his wristwatch instead of his seatbelt.
@@ Line 108: / Line 108: @@
 **different states in which the same controls have different meanings
-==The Classification of Mistakes==
+===The Classification of Mistakes===
 *Skill-based
 **by experts who are skilled
@@ Line 126: / Line 126: @@
 **Toyota - ''poka-yoke'' 'error proofing'
-==Designing for error==
+===Designing for error===
 *Adding constraints to block errors
 *Undo

← Older revision		Revision as of 08:16, 29 October 2018
Line 63:		Line 63:

	==린지==		==린지==
		+	*The Five Whys - by Toyota
		+	**Keep asking why until the root cause it discovered
		+	**Can be multiple root causes
		+	*When we blame people, it is difficult to convince organizations to restructure the design to eliminate these problems.
		+	*If the system lets you make the error, it is badly designed. If it indices you to make the error, it is really poorly designed.
		+	*Common problems
		+	**Repetitive work
		+	**Time stress
		+	===Deliberate violations (of rules and procedures)===
		+	*Because the rules are inappropriate
		+	*Because they encourage violation because work cannot be done otherwise
		+	*Being rewarded for non-compliance
		+	*A kind of organizational and societal error
		+	===Two kinds of errors===
		+	*Slips
		+	**Action based, memory lapse
		+	**The goal is correct, but the required actions aren't done properly
		+	**Put coffee cup in refrigerator, forget to turn off the stove
		+	*Mistakes
		+	**When the goal/plan is wrong
		+	**Rule based, knowledge based, memory lapse
		+	**Act on erroneous knowledge
		+	**Even if actions are performed correctly, they are part of the error
		+	**Weight of fuel computed in lbs not kilograms.
		+	**Distraction
		+
		+	==Slips===
		+	A colleague reported that he went to his car to drive to work. As he drove away, he realized he forgot his briefcase, so he turned around and went back. He stopped the car, turned off the engine, and unbuckled his wristwatch. Yes, his wristwatch instead of his seatbelt.
		+
		+	*memory-slip vs action-slip
		+	*experts most often do them because actions are automated
		+	*capture slips: a more frequently performed action is performed instead, identical parts
		+	**partial memory lapse)
		+	**designers should avoid identical opening steps which then diverse
		+	*description-similarity slips
		+	**correct action on wrong object
		+	**similar in nature so they get confused
		+	**designers should make controls for different purposes significantly different looking
		+	*memory lapse
		+	**fail to do steps, repeat steps, forget goal
		+	**caused by interruptions
		+	**designers can minimize steps, provide vivid reminders of what needs to be completed, use forcing function
		+	*mode errors
		+	**different states in which the same controls have different meanings
		+
		+	==The Classification of Mistakes==
		+	*Skill-based
		+	**by experts who are skilled
		+	*Rule-based
		+	**wrong rule selected -- mistake
		+	**problem in execution of rule - slip
		+	*Knowledge-based
		+	**Conceptual models
		+
		+	*Ensure that all relevant info is continuously available.
		+	*Assume people will be interrupted
		+	*Take social pressure into consideration
		+	*Checklists (one to read, one to do)
		+	*Reporting error
		+	**Not always easy to detect, social pressure
		+	**Toyota - ''jidoka'' 'automation with a human touch'
		+	**Toyota - ''poka-yoke'' 'error proofing'
		+
		+	==Designing for error==
		+	*Adding constraints to block errors
		+	*Undo
		+	*Confirmation and error messages
		+	*Sensibility checks
		+	*Minimizing slips
		+	*Swiss cheese model of accidents
		+	**Add more slices
		+	**Reduce holes
		+	**Alert human when holes line up

@@ Line 1: / Line 1: @@
 [[UX 모임]]
 ==선애==
-*웹페이지 : [[https://allinpdf.com/intro# allinpdf]]
+*웹페이지 : [https://allinpdf.com/intro# allinpdf]
 ===RULE6. 사용자의 생각을 디자인하라===
 *대다수의 제품은 특정 목적을 위한 기능들로 구성되어 있고, 제품의 가치도 그 목적을 얼마나 빠르고 정확하게 만족시키느냐에 달림

← Older revision		Revision as of 04:06, 29 October 2018
Line 60:		Line 60:
	*링크에 글머리 기호를 이용할 때는 이 기호도 클릭되게 하라		*링크에 글머리 기호를 이용할 때는 이 기호도 클릭되게 하라
	*방문하지 않은 링크와 방문한 링크 모두 명확히 보이게 하라		*방문하지 않은 링크와 방문한 링크 모두 명확히 보이게 하라
		+
		+	==린지==

← Older revision		Revision as of 01:21, 29 October 2018
Line 39:		Line 39:
	**사용자 경험의 가치를 공유하라 : 공통된 관심과 욕구를 가진 사람들과 공유하여 사회적 관계를 강화. ex) [https://vimeo.com/ko/ Vimeo]		**사용자 경험의 가치를 공유하라 : 공통된 관심과 욕구를 가진 사람들과 공유하여 사회적 관계를 강화. ex) [https://vimeo.com/ko/ Vimeo]
	*창의적인 사용자는 호기심있고 자신의 욕구에 충실한 사용자. 다양한 관경에서 여러가지 조합을 실험하고 거기서 얻는 경험을 하나의 가치로 여김. ex) [https://minecraft.net/ko-kr/ 마인크래프트(Minecraft)], [https://itunes.apple.com/us/app/id742625884 Blek], [https://terms.naver.com/entry.nhn?docId=3577235&cid=58773&categoryId=58777 GTA]		*창의적인 사용자는 호기심있고 자신의 욕구에 충실한 사용자. 다양한 관경에서 여러가지 조합을 실험하고 거기서 얻는 경험을 하나의 가치로 여김. ex) [https://minecraft.net/ko-kr/ 마인크래프트(Minecraft)], [https://itunes.apple.com/us/app/id742625884 Blek], [https://terms.naver.com/entry.nhn?docId=3577235&cid=58773&categoryId=58777 GTA]
		+
		+	==현규==
		+	===의미있는 링크 만들기===
		+	*링크 이름으로 새로운 프로그램이나 제품의 이름을 이용하지 마라
		+	*문서 제목이나 제목을 링크로 이용하겠다는 생각을 재고하라
		+	**링크의 의미가 제대로 전달되지 않을 수 있기 때문이다
		+	*한발 앞서 생각하라 링크와 페이지 제목을 맞춰라
		+	**링크와 페이지 제목이 일치하면 방문자는 제대로 된 길을 가고 있다고 생각한다.
		+	*허락된 공간에서 최대한 명시적으로 써라. 필요한 자리를 만들어라.
		+	*행위 링크에는 행위 절을 이용하라
		+	**동사로 시작하는 링크가 더 쉽게 이해된다(한국말에서는 다르다)
		+	*명사 단독 사용을 아껴라. 길게 설명하는 링크가 더 좋다
		+	**이상적인 링크의 단어수는 7개에서 12개.
		+	*사람들이 필요로 하면 짧은 설명을 덧붙여라. 아니면 링크를 다시 써라.
		+	**링크를 의미 있기 만들어라. Click here나 More을 피하라.
		+	*비슷한 링크가 여러 개 있다면 정리하라.
		+	*사람들이 여러분의 정보에 머무르기를 원한다면 링크를 임베드하지 마라.
		+	**사람들이 대강 읽으면 임베드링크도 괜찮다 (위키피디아 처럼)
		+	**하지만 사람들이 중간에 배회하기를 원하지 않는다면 링크를 제일 밑이나 본문 옆에 둬라
		+	*링크에 글머리 기호를 이용할 때는 이 기호도 클릭되게 하라
		+	*방문하지 않은 링크와 방문한 링크 모두 명확히 보이게 하라

@@ Line 1: / Line 1: @@
 ==선애==
 ===RULE6. 사용자의 생각을 디자인하라===
@@ Line 28: / Line 29: @@
 *유연성과 사용성의 관계 : 사용자에게 더 많은 자유를 줄수록 사용성은 그에 비례하여 낮아짐.
 *개러지 밴드(Garage Band) vs. 로직 프로(Logic Pro) X
 **개러지 밴드 : 애플의 무료 음악 저작 소프트웨어. 연주와 창작의 즐거움을 남겨 타인과 공유하는 경험이 제품의 콘셉트
 **로직프로X : 전문 음악가와 스튜디오를 위한 애플의 프로그램. 다양하고 복잡한 기능을 통해 풍부한 표현과 높은 품질을 만들어 낼 수 있음.