This week, we’re reading about UX in context, be that context an unfamiliar application, the mobile environment, or the enterprise.
What are you reading?
The author of this post (Dan Birman of Digital Telepathy) acknowledges that “certain patterns that we (designers) want users to execute require learned behaviors.” Teaching users these behaviors, however, can be complicated and lead to visual clutter. As an alternative, he recommends “Progressive Reduction (PR) – the idea that interfaces should be adapted over time as users become more acquainted with applications.” Have you tried that?
Giving users what they want through easy to understand design is the holy grail of any digital strategy. The author (Chris Bank of UXPin) of this post presents a wide variety of examples (18 distinct design patterns) demonstrating how code and design work together on some of the most highly-trafficked and engaging sites.
While the title of this post refers to responsive images, the post itself is actually about the importance of considering context when developing websites. Specifically, the author (Mat Marquis of Bocoup) reminds web developers that the context in which they are developing sites—characterized by high-bandwidth and stable networks—is not the context of most mobile users. Within that context, image-heavy sites create bad user experiences and responsive images matter more than you think.
According to Blue Rooster's Kevin Conroy, “Each of us can chronicle bad experiences with the technology tools we use every day — and if you’re in the enterprise, your pain may be even more excruciating than consumers. Not only are the experiences worse for you, but they are often ones that you do repetitively, so that pain piles up into long-term frustration and general dread.” Given this familiar reality, why does UX for enterprise software lag so far behind UX in the consumer sphere? This post tries to answer that question and chart a path towards better user experiences inside the enterprise.