1. ⁘  ⁘  ⁘
  2. ⁘  ⁘  ⁘
  3. Abo, Akinori 9
  4. aesthetics 19
  5. agile 30
  6. Albers, Josef 17
  7. Alexander, Christopher 135
  8. Alexander, Scott 5
  9. Allsopp, John 4
  10. Ammer, Ralph 6
  11. Anderson, Gretchen 7
  12. anxiety 9
  13. Appleton, Maggie 5
  14. Aptekar-Cassels, Wesley 5
  15. Arango, Jorge 4
  16. architecture 110
  17. art 86
  18. Asimov, Isaac 5
  19. attention 17
  20. Auping, Michael 6
  21. Aurelius, Marcus 14
  22. Bachelard, Gaston 12
  23. Baker, Nicholson 10
  24. beauty 58
  25. Behrensmeyer, Anna K. 7
  26. Bjarnason, Baldur 8
  27. Blake, William 5
  28. blogging 22
  29. body 11
  30. Boeing, Geoff 7
  31. boredom 9
  32. Botton, Alain de 38
  33. Brand, Stewart 4
  34. Bringhurst, Robert 16
  35. Brooks, Frederick P. 22
  36. Broskoski, Charles 6
  37. brutalism 7
  38. building 16
  39. bureaucracy 12
  40. Burnham, Bo 9
  41. business 15
  42. Byron, Lord 14
  43. Cagan, Marty 8
  44. Calvino, Italo 21
  45. Camus, Albert 13
  46. care 6
  47. Carruth, Shane 15
  48. Cegłowski, Maciej 6
  49. Cervantes, Miguel de 7
  50. chance 11
  51. change 16
  52. Chiang, Ted 4
  53. childhood 6
  54. Chimero, Frank 17
  55. choice 8
  56. cities 51
  57. Clark, Robin 3
  58. Cleary, Thomas 8
  59. Cleary, J.C. 8
  60. code 20
  61. collaboration 18
  62. collections 31
  63. color 23
  64. commonplace 11
  65. communication 31
  66. community 7
  67. complexity 11
  68. connection 24
  69. constraints 25
  70. construction 9
  71. content 9
  72. Corbusier, Le 13
  73. Coyier, Chris 4
  74. craft 66
  75. creativity 59
  76. crime 9
  77. Critchlow, Tom 5
  78. critique 10
  79. Cross, Nigel 12
  80. Cross, Anita Clayburn 10
  81. css 11
  82. culture 13
  83. curiosity 11
  84. cycles 7
  85. Danielewski, Mark Z. 4
  86. darkness 28
  87. Darwin, Will 10
  88. data 8
  89. death 38
  90. Debord, Guy 6
  91. decisions 10
  92. design 131
  93. details 31
  94. Dickinson, Emily 9
  95. Dieste, Eladio 4
  96. discovery 9
  97. doors 7
  98. Dorn, Brandon 11
  99. drawing 23
  100. Drucker, Peter F. 15
  101. Duany, Andres 18
  102. Eatock, Daniel 4
  103. economics 13
  104. efficiency 7
  105. Eisenman, Peter 8
  106. Eliot, T.S. 14
  107. emotion 8
  108. ending 14
  109. engineering 11
  110. Eno, Brian 4
  111. ethics 14
  112. euphony 38
  113. Evans, Benedict 4
  114. evolution 9
  115. experience 14
  116. farming 8
  117. fashion 11
  118. features 25
  119. feedback 6
  120. flaws 10
  121. Flexner, Abraham 8
  122. food 16
  123. form 19
  124. Fowler, Martin 4
  125. Franklin, Ursula M. 30
  126. friendship 6
  127. fun 7
  128. function 31
  129. games 13
  130. gardens 26
  131. Garfield, Emily 4
  132. Garfunkel, Art 6
  133. geography 8
  134. geometry 18
  135. goals 9
  136. Gombrich, E. H. 4
  137. goodness 12
  138. Graham, Paul 37
  139. graphics 13
  140. Greene, Erick 6
  141. Hamming, Richard 45
  142. happiness 17
  143. Harford, Tim 4
  144. Harper, Thomas J. 15
  145. Hayes, Brian 28
  146. heat 7
  147. Heinrich, Bernd 7
  148. Herbert, Frank 4
  149. Heschong, Lisa 27
  150. Hesse, Herman 6
  151. history 13
  152. Hoffman, Yoel 10
  153. Hofstadter, Douglas 6
  154. home 15
  155. Hoy, Amy 4
  156. Hoyt, Ben 5
  157. html 11
  158. Hudlow, Gandalf 4
  159. humanity 16
  160. humor 6
  161. Huxley, Aldous 7
  162. hypermedia 22
  163. i 18
  164. ideas 21
  165. identity 33
  166. images 10
  167. industry 9
  168. information 42
  169. infrastructure 17
  170. innovation 15
  171. interaction 10
  172. interest 10
  173. interfaces 37
  174. intuition 8
  175. invention 10
  176. Irwin, Robert 65
  177. Isaacson, Walter 28
  178. Ishikawa, Sara 33
  179. iteration 13
  180. Ive, Jonathan 6
  181. Jackson, Steven J. 14
  182. Jacobs, Jane 54
  183. Jacobs, Alan 5
  184. Jobs, Steve 20
  185. Jones, Nick 5
  186. Kahn, Louis 4
  187. Kakuzō, Okakura 23
  188. Kaufman, Kenn 4
  189. Keith, Jeremy 6
  190. Keller, Jenny 10
  191. Keqin, Yuanwu 8
  192. Ketheswaran, Pirijan 6
  193. Kingdon, Jonathan 5
  194. Kitching, Roger 7
  195. Klein, Laura 4
  196. Kleon, Austin 13
  197. Klinkenborg, Verlyn 24
  198. Klyn, Dan 20
  199. knowledge 29
  200. Kohlstedt, Kurt 12
  201. Kramer, Karen L. 10
  202. Krishna, Golden 10
  203. Kuma, Kengo 18
  204. language 20
  205. learning 30
  206. life 59
  207. light 31
  208. loneliness 12
  209. love 26
  210. Lovell, Sophie 16
  211. Lupton, Ellen 11
  212. Luu, Dan 8
  213. Lynch, Kevin 12
  214. MacIver, David R. 8
  215. MacWright, Tom 5
  216. Magnus, Margaret 12
  217. making 77
  218. management 14
  219. Manaugh, Geoff 27
  220. Markson, David 16
  221. Mars, Roman 13
  222. material 39
  223. math 16
  224. McCarter, Robert 21
  225. meaning 33
  226. media 16
  227. melancholy 52
  228. memory 29
  229. metaphor 10
  230. metrics 19
  231. microsites 49
  232. Miller, J. Abbott 10
  233. Mills, C. Wright 9
  234. minimalism 10
  235. Miyazaki, Hayao 30
  236. Mod, Craig 15
  237. modularity 6
  238. Mollison, Bill 31
  239. morality 8
  240. Murakami, Haruki 21
  241. music 16
  242. Müller, Boris 7
  243. Naka, Toshiharu 8
  244. names 11
  245. Naskrecki, Piotr 5
  246. nature 51
  247. networks 15
  248. Neustadter, Scott 3
  249. Noessel, Christopher 7
  250. notetaking 35
  251. novelty 11
  252. objects 16
  253. order 10
  254. ornament 9
  255. Orwell, George 7
  256. Ott, Matthias 4
  257. ownership 6
  258. Pallasmaa, Juhani 41
  259. Palmer, John 8
  260. patterns 11
  261. Patton, James L. 9
  262. Pawson, John 21
  263. perception 22
  264. perfection 7
  265. performance 17
  266. Perrine, John D. 9
  267. Petroski, Henry 24
  268. philosophy 6
  269. photography 20
  270. physics 6
  271. Pinker, Steven 8
  272. place 14
  273. planning 15
  274. Plater-Zyberk, Elizabeth 18
  275. poetry 13
  276. politics 9
  277. Pollan, Michael 6
  278. practice 10
  279. problems 31
  280. process 22
  281. production 7
  282. productivity 12
  283. products 21
  284. programming 9
  285. progress 16
  286. Pye, David 42
  287. quality 26
  288. questions 8
  289. Radić, Smiljan 20
  290. Rams, Dieter 16
  291. Rao, Venkatesh 14
  292. reading 16
  293. reality 13
  294. Reichenstein, Oliver 5
  295. religion 11
  296. Rendle, Robin 12
  297. repair 28
  298. research 17
  299. Reveal, James L. 4
  300. Richards, Melanie 3
  301. Richie, Donald 10
  302. Rougeux, Nicholas 4
  303. Rowe, Peter G. 10
  304. Rupert, Dave 4
  305. Ruskin, John 5
  306. Satyal, Parimal 9
  307. Saval, Nikil 13
  308. Sayers, Dorothy 32
  309. Schaller, George B. 7
  310. Schwulst, Laurel 5
  311. science 17
  312. seeing 36
  313. Sennett, Richard 45
  314. senses 11
  315. Seuss, Dr. 14
  316. Shakespeare, William 4
  317. Shorin, Toby 8
  318. silence 9
  319. Silverstein, Murray 33
  320. Simms, Matthew 19
  321. Simon, Paul 6
  322. simplicity 14
  323. Singer, Ryan 12
  324. skill 17
  325. Sloan, Robin 5
  326. Smith, Cyril Stanley 29
  327. Smith, Justin E. H. 6
  328. Smith, Rach 4
  329. socializing 7
  330. society 23
  331. software 68
  332. solitude 12
  333. Somers, James 8
  334. Sorkin, Michael 56
  335. sound 14
  336. space 20
  337. Speck, Jeff 18
  338. spirit 10
  339. streets 10
  340. structure 13
  341. Strunk, William 15
  342. Ström, Matthew 13
  343. style 30
  344. Sun, Chuánqí 15
  345. symbols 12
  346. systems 18
  347. Sōetsu, Yanagi 34
  348. Sōseki, Natsume 8
  349. Tanaka, Tomoyuki 9
  350. Tanizaki, Jun'ichirō 15
  351. taste 10
  352. Taylor, Dorian 16
  353. teaching 21
  354. teamwork 17
  355. technology 41
  356. texture 7
  357. thinking 31
  358. Thoreau, Henry David 8
  359. time 54
  360. Tolkien, J.R.R. 6
  361. tools 32
  362. touch 8
  363. transportation 16
  364. Trombley, Nick 44
  365. truth 15
  366. Tufte, Edward 31
  367. Turrell, James 6
  368. typography 25
  369. understanding 32
  370. urbanism 68
  371. ux 100
  372. Victor, Bret 9
  373. Viollet-le-Duc, Eugène 4
  374. vision 7
  375. visualization 34
  376. Voltaire 4
  377. wabi-sabi 8
  378. walking 23
  379. Wallace, David Foster 33
  380. Wang, Shawn 6
  381. war 7
  382. waste 12
  383. Watterson, Bill 4
  384. Webb, Matt 14
  385. Webb, Marc 3
  386. Weber, Michael H. 3
  387. Wechler, Lawrence 37
  388. whimsy 11
  389. White, E.B. 15
  390. Wirth, Niklaus 6
  391. wisdom 20
  392. Wittgenstein, Ludwig 7
  393. Woolf, Virginia 11
  394. words 35
  395. work 81
  396. writing 55
  397. Wurman, Richard Saul 18
  398. www 88
  399. Yamada, Kōun 5
  400. Yamashita, Yuhki 4
  401. Yudkowsky, Eliezer 17
  402. zen 38
  403. ⁘  ⁘  ⁘
  404. About
  405. RSS Feed
  406. Source

Ryan Singer

Close
  • Framing vs. Shaping

    An Article by Ryan Singer
    world.hey.com
    Image from world.hey.com on 2022-05-21 at 2.00.58 PM.png

    Framing is all about the problem and the business value. It's the work we do to challenge a problem, to narrow it down, and to find out if the business has interest and urgency to solve it.

    The framing session is where a feature request or complaint gets evaluated to judge what it really means, who's really affected, and whether now is the time to try and shape a solution.

    • products
    • problems
  • Two kinds of usability

    An Article by Ryan Singer
    world.hey.com

    I divide usability problems into two kinds:

    1. Perceptual: "They couldn't figure out what to do next", "they couldn't find the feature", "they didn't know they could click that button..." etc.
    2. Domain-specific: "We need a way to jump back here because in their workflow this happens..."

    In general, usability testing only catches type 1 perceptual problems. Because in those tests you take people out of the real world and assign them tasks. Usability testing doesn't catch domain-specific problems because they only come up in real life use.

    • ux
    • ethnography
  • How I Wrote Shape Up

    An Article by Ryan Singer
    m.signalvnoise.com

    Here’s a little behind-the-scenes look at the development of our newest book, Shape Up: Stop Running in Circles and Ship Work that Matters.

    1. ​​To Make a Book, Walk on a Book​​

    A very different process from Craig Mod, but I always enjoy reading case studies about how information artifacts are made.

  • Keep digging

    An Article by Ryan Singer
    m.signalvnoise.com

    The hardest thing about customer interviews is knowing where to dig. An effective interview is more like a friendly interrogation. We don’t want to learn what customers think about the product, or what they like or dislike — we want to know what happened and how they chose... To get those answers we can’t just ask surface questions, we have to keep digging back behind the answers to find out what really happened.

    • questions
    • research
    • understanding

    I asked one of my favorite questions: What was happening that showed you the way you were doing things wasn’t working anymore?

    This question is extremely targeted and causal. It’s a very simple question that invites her to describe the problem in a way that is hard, factual, time-bound, contextual, and specific — without any analysis, interpretation, speculation or rationalization. Just: What happened. What did you see. What was wrong.

  • Domain-specific vs. Domain-independent UX

    An Article by Ryan Singer
    m.signalvnoise.com

    Domain specific UX means understanding how the supply should fit the demand considering a specific situation and use case.

    On the other hand, many aspects of UX don’t require knowledge about a particular situation. They‘re based on the common constraints of human sense faculties, memory and cognition or the net of ergonomic factors around the device and the setting where it’s used. These domain independent elements of the UX are important too.

    Domain independent UX should absolutely pervade the organization. It belongs to the general skill and knowledge of each supplier at their link in the chain. It’s part of learning to be a good designer, programmer, marketer, salesperson etc.

    • ux
    • design
    • context
  • The Fidelity Curve

    An Article by Ryan Singer
    m.signalvnoise.com

    How do we choose which level of fidelity is appropriate for a project?

    I think about it like this: The purpose of making sketches and mockups before coding is to gain confidence in what we plan to do. I’m trying to remove risk from the decision to build something by somehow “previewing” it in a cheaper form. There’s a trade-off here. The higher the fidelity of the mockup, the more confidence it gives me. But the longer it takes to create that mockup, the more time I’ve wasted on an intermediate step before building the real thing.

    I like to look at that trade-off economically. Each method reduces risk by letting me preview the outcome at lower fidelity, at the cost of time spent on it. The cost/benefit of each type of mockup is going to vary depending on the fidelity of the simulation and the work involved in building the real thing.

    1. ​​Four levels of fidelity​​
    2. ​​Time to build versus confidence gained​​
    • prototypes
    • interfaces
  • Time-based analytics

    An Article by Ryan Singer
    feltpresence.com
    Image from feltpresence.com on 2021-09-05 at 2.07.11 PM.jpeg

    Analytics apps don't tell you much about usage behavior. You might be able to see how many users performed an event, or how many times they did it. But none of the analytics packages out there are good at showing you how often people do things. Are they using to-dos once a week? Every day? Only signing into the app once a month but happily paying for years?

    Time matters. You can't understand usage without time.

    • analytics
    • metrics
    • features
    • visualization
  • UI and Capability

    An Article by Ryan Singer
    rjs.medium.com
    Screenshot of rjs.medium.com on 2021-09-05 at 1.39.21 PM.png

    I’m very conscious of whether I am affording a feature or styling it. It’s important to distinguish because they look the same from a distance.

    ...Affording a capability and styling it are both important. But it’s essential to know which one you are doing at a given time. Style is a matter of taste. Capability and clarity are not. They are more objective. That person standing at the edge of the chasm cares more about accomplishing their task than the details of the decor.

    • function
    • style
    • design
  • What happens to user experience in a minimum viable product?

    An Article by Ryan Singer
    signalvnoise.com
    Screenshot of signalvnoise.com on 2021-09-05 at 1.22.31 PM.png

    "Feature complexity is like surface area and quality of execution is like height. I want a base level of quality execution across all features. Whenever I commit to building or expanding a feature, I'm committing to a baseline of effort on the user experience."

    There’s a distinction to make: The set of features you choose to build is one thing. The level you choose to execute at is another. You can decide whether or not to include a feature like ‘reset password’. But if you decide to do it, you should live up to a basic standard of execution on the experience side.

    Features can be different sizes with more or less complexity, but quality of experience should be constant across all features. That constant quality of experience is what gives your customers trust. It demonstrates to them that whatever you build, you build well.

    1. ​​Minimum Awesome Product​​
    • quality
    • products
    • features
    • ux
  • What UI really is (and how UX confuses matters)

    An Article by Ryan Singer
    rjs.medium.com

    People mix the terms UI and UX together. UX is tricky because it doesn’t refer to any one thing. Interface design, visual styling, code performance, uptime, and feature set all contribute to the user’s “experience.” Books on UX further complicate matters by including research methods and development methodologies. All of this makes the field confusing for people who want to understand the fundamentals.

    That’s why I avoid teaching the term ’UX.’ It means too many things to too many different people. Instead I focus on individual skills. Once you understand the individual skills, you can assemble them into a composite system without blurring them together. For software design, the core skill among all user-facing concerns is user interface design.

    • ux
    • interfaces

See also:
  1. ux
  2. interfaces
  3. products
  4. features
  5. design
  6. quality
  7. function
  8. style
  9. prototypes
  10. analytics
  11. metrics
  12. visualization
  13. context
  14. questions
  15. research
  16. understanding
  17. ethnography
  18. problems