Column: Innovating UX Practice

As UX professionals, we have a great many analytical and descriptive tools available to us. In fact, there are so many that it can sometimes be difficult to decide which tool is most appropriate for a given task! Hierarchical task analysis (HTA) is an underused approach in user experience, but one you can easily apply when either modifying an existing design or creating a new design.

This technique has applications across a range of different problem domains, including time-and-motion studies, personnel selection, or training, and provides a broad and deep understanding of task performance. While there are core principles that guide a hierarchical task analysis, it’s possible to adapt the basic approach in a huge number of ways to support the needs of any domain under consideration. In this column, I’ll examine one approach to hierarchical task analysis that enables UX designers to quickly understand both what a system does and how its capabilities translate into the system’s user experience. You can also use this approach to support the UX development process. Read More

“These are my principles; if you don’t like them, I have others.”—Groucho Marx

For a long time, I’ve been an advocate of creating standards, guidelines, and patterns as a way of achieving design consistency within a large organization. While these do offer significant benefits, they also introduce a number of problems into the design process.

Some Problems with Design Standards

First, standards can provide a false sense of expertise in design. Calling something a standard, by its very nature, seems to imply that a great deal of research, thought, and experimentation has gone into its creation. It is likely that the proper stakeholders and experts have approved it. So designing something in a way that differs from a standard sets the designer against the people who set the standard and the weight of the work that they have done. No mean feat. Particularly for people who are new to an organization or junior designers, it can be easier to keep their head down and avoid challenging a safe option. In some organizations, particularly those that outsource a lot of design work, a reliance on standards can also lead to stakeholders using the standards to design solutions themselves, bypassing the UX design team. Read More

“Many people tend to look at programming styles and languages like religions: if you belong to one, you cannot belong to others. But this analogy is another fallacy.”—Niklaus Wirth

Software Engineering is typically much more formal than User Experience in they way they model an application before development begins. After pseudo code, the Unified Modeling Language (UML) is probably the most widely used modeling language among software engineers. It has developed from other object?based analysis and design languages over a period of many years and provides software engineers with a visual language that describes the design of a system at multiple levels.

Comparable UX design artifacts such as user journeys and personas can take a wide variety of forms. While this diversity can enable us to tailor our design artifacts to different circumstances, drawing features from modeling languages such as UML could promote better cross?functional work practices, increase a design’s reusability, and reduce the overall effort of developing software systems.

This article looks at how User Experience can use UML modeling techniques to enhance user journeys and promote better cross?disciplinary collaboration. Read More