listi.net

Listi.net

             


 Book Notes - blog notes [bn] >

Don't Make me Think

1. http://www.sensible.com/downloads-dmmt.html
2. Web Application Design Handbook - Susan Fowler
3. If something is hard to use you don''t use it that much
4. Dont make me think
5. Get rid of question mark in people''s minds
6. Make language obvious - Job vs. Employment Opportunities
7. Is it clickable.
8. Visitors shouldn''t spend time
9. * Where am I?
10. * Where should I begin?
11. * Where did they put ....?
12. * Where are the most important things on pg.?
13. * Why did they call it that?
14. @pg shud b self evident or self-explanatory
15. Designer things gr8 brochure, user thinks "billboard @ 60mph"
16. 3 facts
17. 1. We don''t read pgs. We scan them Useit.com
18. ..a. We''re in a hurry
19. ..b. We don''t need to read everything
20. ..c. We''re good at it
21. 2. We dont mk optimal choice. We satifice (satisfy and sufficing)
22. ..We choose the 1st reasonble option
23. ..Why
24. ...a. in a hurry
25. ...b. no penalty for guessing wrong
26. ...c. weighing options may not improve odds
27. ...d. guessing is > fun
28. 3. We dont figure out how things work. We muddle thru.
29. ...Few people read instructions
30.
31. If ur audience acts like u r designing billboards then design gr8 billboards
32. Billboard Design 101
33. ..Design page for scanning not reading
34. Create Visual Hierarchy
35. The > important something is the > prominent it is
36. Things related logically r related visually
37. Nest 2 show what''s part of what
38. No visual hierarchy and everything is equally important
39. Use conventions
40. Break up page into clearly defined areas
41. Make it obvious 2 what''s clickable
42. Keep noise down
43. * busyness
44. * background noise
45. * everything is noise until proven otherwise
46. Users like mindless choices
47. Mindless clicks = 1 that requires thought
48. Omit needless words
49. Remove 1/2 of the words then
50. remove 1/2 of what''s left
51. Eliminate happy talk
52. ..If you''re saying blah, blah, blah it''s happy talk
53. ..Conveys no useful info
54. ..saying how gr8 we r not why w''re gr8
55. Instructions must die
56. ..No on will read them
57. ..mk it self-explanatory
58. When someone comes to ur site what are they looking for?
59. Fu cant find wht ur looking 4 ull leave
60. ==> need search on my site
61. Utilities
62. Information Architecture for the WWW - Louis Rosenfeld
63. Search [ ] [go] or [_________] [Search]
64. Make sure link and page name match ???
65. Breadcrumbs Home>Hobbies>Book Collecting>welcom
66. User-experience.org
67. Use tabs
68. Look at amazon
69. @Page
70. ..Site id
71. ..Page name
72. ..Sections
73. ..local nav
74. ..u r here
75. ..search
76. Home Page
77. ..Site Id and Mission
78. ....What site is
79. ....Whats it for
80. ....Why be here and not other site
81. ..Site Hierarchy
82. ..What site has 2 offer
83. ....Content
84. ....Features
85. ..Teases
86. ....Entice w/hint of good stuff
87. ....Top Stories
88. ....Hot deals
89. Timely Content
90. Deals
91. Shortcuts
92. Registration
93. Show me
94. ..What I''m looking 4
95. ..What I''m not looking 4
96. ..Where to start
97. ..Credibility and trust
98. Convey the big picture
99. Answer 4 q''s
100. ..What is this?
101. ..What do they have here?
102. ..What can I do here?
103. ..Why should I be here and not somewhere else
104. Getting msg accross
105. ..Tagline
106. ..Welcome blurb
107. ..Main point
108. Taglines
109. ..Clear
110. ..informative
111. ..bad ones are vague
112. ..6 - 8 words
113. ..Clear benefit
114. ..differentiation
115. ..Personable
116. ..Lively
117. ..Sometimes clever if convey benefit
118. Where do I start?
119. Step by step website should leap out
120. User interfaces must b tested by real users
121. Determine what works and what doesn''t
122. Not who''s right and who''s wrong
123. Who is ur sites audience?
124. What do they want?
125. F u want a great site uv got 2 test
126. Testing 1 user is 100% better than testing none
127. Testing 1 users early in project is better than testing 50 near the end
128. recruiting representative users is overrated
129. Testing is an iterative process
130. Nothing beats a live audience reaction
131. Watch some people while they try 2 use ur pos & note where thy run into trouble
132. Fixit then test again
133. Testing Cheaply
134. ..3 - 4 people
135. ..Anybody who uses web will do.
136. ..run small tests continually throughout dev process 50 - 100 4 @ user
137. ..debrief over lunch same day
138. ..1 hr test session $50 for every user
139. Invitation
140. ..We need 2 have a few people look at our website and gv us feedback
141. ..It''s very easy and wud tk abt 45 mins to 1hr
142. ..and ull be paid $xx for your time
143. ..dont discuss site or org b4 hand
144. ..dont b embarrassed to ask friends and neighbors
145. Where to test
146. ..2 chares, pc, camcorder, tripod. Allow team to watch and hear in another room
147. Use screen recorder
148. Test another comparable site first 2 get the thick skin ull need
149. Get it testing
150. ..Show site
151. ..see if they get it
152. ..Do they understand
153. ....Purpose of site
154. ....value proposition
155. ....how organized
156. ....how it works
157. Key task testing
158. ..Ask user to do something and watch how they do it
159. ...."find a book u want to buy " is better than "find a cookbook for under $4"
160. ..Whn people r doing madeup tasks thy hv no emotionaly investment in it
161. ..they cant use as much of thr personal knowledge
162. ..Cubicle test - ask person in next cubicle
163. Usability script at Sensible.com
164. Review results right away
165. Do 3 - 4 tests in am and debrief over lunch
166. at lunch
167. triage - review probs & decide which ones need 2b fixed
168. problem solving - figure out how 2 fix them
169. Typical problem
170. ..users r unclear on the concept
171. ..words they''re looking 4 arent thr
172. ..thrs 2 much going on
173. Triage guidelines
174. ..Resist impulse 2 add things
175. ..its usually bttr 2 tk something away rather than adding explanation or instructions
176. ..Tk new feature requests w/grain of salt
177. ..b suspicious fo request 4 new features
178. ..f u probe deeper it often turns out that thy already hv a fine source of x n wudnt chg. thr just telling u what thy like
179. ..Grab low hanging fruit
180. ..look 4 big/cheap wins
181. ..head slappers
182. ..cheap hits
183. ....require almost no effort
184. ....little effort highly visible
185. Fixing problems w/o breaking what works
186. ..Mking something > prominent will de-emphasize something
187. 1 morning @ month doing UT (usablity testing)
188. sensible.com/secondedition
189. Is it clear
190. Do they get it
191. Reservoir of Goodwill
192. Things that decrease goodwill
193. ..Hiding information I want
194. ....CS phone #
195. ....Shipping rates
196. ....prices
197. ..Punishing me 4 not doing things ur way
198. ....format my phone # ur way
199. ..Asking 4 infor u dont really need
200. ..Fake sincerity
201. ...."ur call is important to us"
202. ..Flash intos or bloated pages
203. ..Amateurish looking site
204. ..Uninvited popups
205. ....unless u cn get 10% > biz
206. Increase Goodwill
207. ..convince me u hv my interests @heart
208. ..know the main things that people want 2 do on ur site & make them obvious and easy
209. ..What are the 3 main things ur users want to do
210. ..Tell me what I want to know
211. ....shipping cost
212. ....service outages
213. ..Save me steps whenever you can
214. ..Put effort into it, see hp.com
215. ..Know what q''s i''m likely to have and answer them
216. ....They really r FAQs not marketing
217. ..5 top FAQs this week
218. ..B candid
219. ..Provide me with creature comforts
220. ....Printer friendly pages
221. ..Mk it easy to recover from errors
222. ..Whn in doubt apologize
223. ....apologize if u know ur wrong
224. Accessibility
225. ..redish.net/context/papers/interactions.html
226. ..Building accessible websites - Joe clark
227. ..Use Cascading style sheets
228. ..csszengarden.com
229. ..Books by Eric Meyer
230. Low Hanging Fruit
231. ..Add alt tags 2 @image
232. ..mk forms work w/ screen reader
233. ..Figure intention behind a bad request
Top