Process: Design Process

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

The ability to take a broad view of the world and incorporate lessons learned from other disciplines distinguishes the best practitioners in any field. As UX professionals, there is much we can learn from good software engineering practice, which maps a team’s understanding of a problem at a human level onto the implementation of a technical solution. The essence of good software engineering practice is effective user experience—from developing the high-level design documentation that describes how the main elements of a system interact to its implementation in clearly written code. Though the relationship between software engineering and user experience is not always an easy one, software engineers and UX professionals share some common goals. Both have a vested interest in producing systems that are useful and usable.

This column, Innovating UX Practice, will explore how we can apply software engineering concepts and practices in the context of user experience design and, hopefully, build greater understanding between the two disciplines. Read More

I’m sitting in a conference room with a coworker and two clients. It’s chaotic, hot, and a challenge just to walk around without tripping on the mess surrounding us. We are in the midst of designing and are buried in paper and sharpies and flipcharts. The walls around us are covered with consolidated data from requirements gathering and flipchart pages we’ve filled with our thought processes. Every few minutes, we need to retape some piece of paper that’s in danger of falling into a crumpled heap on the floor. Then, suddenly, I’m gripped with the feeling of déjà vu. It seems like I’m working on the same design I’ve worked on a thousand times before—and I’m getting bogged down in the details to boot! It’s at once disheartening and terrifying. But I’m the lead on this project, so I need to drive the team forward—which presents a challenge at this particular moment.

In that moment, I realized I had to step back and take a new perspective on both my role and the goal of our design. Read More