UXmatters has published 56 articles on the topic Communicating Design.
My last column, “Specifying Behavior,” focused on the importance of interaction designers’ taking full responsibility for designing and clearly communicating the behavior of product user interfaces. At the conclusion of the Design Phase for a product release, interaction designers’ provide key design deliverables that play a crucial role in ensuring their solutions to design problems actually get built. These deliverables might take the form of high-fidelity, interactive prototypes; detailed storyboards that show every state of a user interface in sequence; detailed, comprehensive interaction design specifications; or some combination of these. Whatever form they take, producing these interaction design deliverables is a fundamental part of a successful product design process.
In this installment of On Good Behavior, I’ll provide an overview of a product design process, then discuss some indispensable activities that are part of an effective design process, with a particular focus on those activities that are essential for good interaction design. Although this column focuses primarily on activities that are typically the responsibility of interaction designers, this discussion of the product design process applies to all aspects of UX design. Read More
“To design is to communicate clearly by whatever means you can control or master.”—Milton Glaser
User experience and its associated fields of expertise—such as usability, information architecture, interaction design, and user interface design—have expanded rapidly over the past decade to accommodate what seems like insatiable demand, as the world moves toward an increasingly digital existence.
As UX professionals, we often take technology for granted, accepting the massive complexity and rapid change in our field as the norm—and perhaps even something to embrace and enjoy. With this outlook and because we’re steeped in our daily professional activities, it becomes all too easy for us to forget that ours is not the usual point of view, and the technological change we expect, the expert jargon we speak, and the processes we use are foreign and confusing to other people. So, while we focus our attention on the users of digital products, we can sometimes be remiss in our treatment of another important audience—the stakeholders and clients with whom we collaborate to complete our assignments and projects. Read More
Why is every conversation about wireframes I’ve encountered lately so tense? For instance, at a recent UX Book Club meeting whose topic was a discussion of some articles on wireframes, the conversation moved quickly from the actual articles to the question of what a wireframe even was. What the discussion came down to was this: no one knows the answer, and trying to find it feels like a wild-goose chase—or like wandering off on our own down a yellow brick road to find the all-knowing and powerful Oz to figure the answer out for us.
The Wizard of Oz asks questions like: What is courage or heart or a brain? Who should define them for us? As I see it, UX design suffers from similar definitional issues. We don’t all mean the same thing when we say sketch or wireframe or prototype. So how can we all get on the same page? There are differences between a sketch, a wireframe, and a prototype, but how can we understand the distinctions and the best use of each? And what is their value as communication vehicles? Let’s discuss what separates a sketch from a wireframes from a prototype. Read More