The functional view bakes in causality. Customers make decisions in situations to achieve outcomes, rather than purely based on likes and dislikes. This framework forces you to think about what happens before and after they use the product.
I get the feeling that the median vocabulary of interactions with computers is shrinking. I see so many people who’s entire computing experience is laboriously moving the mouse, clicking on buttons, and maybe poking ⌘C and ⌘V. For knowledge workers who spend half their waking hours using a computer, that’s akin to being a professional athlete who... See more
ITEs are probably a subset of notes apps, just like IDEs are a subset of text editors. Every IDE is fundamentally a text editor. Every ITE is fundamentally a notes app. That’s because—at least for now—the best way we have of working with our thoughts is to instantiate them as notes.
You might think the fiddly detailiness of things is limited to human centric domains, and that physics itself is simple and elegant. That’s true in some sense – the physical laws themselves tend to be quite simple – but the manifestation of those laws is often complex and counterintuitive.
“The bigger part of it is just in finding the right ways of thinking, finding the right representations of abstractions, so people can think thoughts that they couldn’t think before.“The example I like to give is back in the days of Roman numerals, basic multiplication was considered this incredibly technical concept that only official... See more
Most designers set requirements for f() by describing what f() should be, which is a circularity. To be useful, requirements should be defined independent of f() as tests for fitness.
Again, we're imposing order on the mess we observe, and it's taking the same patterns, and when something is in the form of a story, often we remember it when we shouldn't.