Behaviors/dynamics can be discussed and analyzed as discrete "objects" under your control. Design discussions should often be taking place at the level of the dynamic rather than the level of the functionality. Identify what behavior you want to change first, then piece together the necessary functionality that you believe will enable that... See more
fascinating insights on designing products from the previous head of design at Quora. think of the dynamic, not the functionality, then piece together the necessary functionality.
Atomic is doing an MDR Dasher Keyboard. I’m not going to order one, but daaaaamn.
Like the technium itself — our values are continually going through an evolution. This is why when viral tweets about the founding father’s misdeeds circle about, it doesn’t change my opinion about the Constitution. If their acted values were the exact same as ours, it would for me to question us , not them!
Another major source of needless words is instructions. The main thing you need to know about instructions is that no one is going to read them —at least not until after repeated attempts at “muddling through” have failed.
So many good examples of flows/products that become way more usable by removing steps. E.g. OCRing a photo you took using some 3rd party app vs. just selecting the text inside Apple's photos. I use the latter now multiple times a week and “all it did” was reduce steps. [1/3]
Your success as a designer depends equally on your relationships as it does on your design talent . The powerful people you need as allies will likely know little about design and you will have to teach and persuade them. Your amazing ideas and concepts can’t help the world if they are never built by your organization. Your ability to explain your... See more