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
Has your boss or a client ever asked you to review a user interface for a Web or desktop application? Perhaps the request went something like this: Can you just look over these new screens for us? Oh, and can you check the error messages, too? It won’t take long! And, by the way, we ship next month. Whether you are an interaction designer, usability professional, technical communicator, quality assurance engineer, or developer, reviewing a user interface typically means identifying
usability problems related to the layout, logical flow, and structure of the interface and inconsistencies in the design
non-compliance with standards
ambiguous wording in labels, dialog boxes, error messages, and onscreen user assistance
Until recently, I never saw the value in customer journey maps. In fact, throughout my career, I’ve even struggled with the value of personas and scenarios. Many times, stakeholders would just skim over them after our presentations or use them only to prove we were making progress on a project. Design teams, with the best intentions, made every effort to keep personas alive and breathing, only to succumb to other project pressures that demanded annotation, use cases, and itemized requirements.
So why have I written an article on the value of customer journey maps? How did I manage to reach the conclusion that customer journey maps are not only a worthy and effective tool, but also a crucial element on large, enterprise user experience (UX) projects? Because I saw them have a significant impact on a recent project with The Boeing Company, and I’m now a believer.
In this article, I’ll attempt to illustrate the virtues of customer journey maps, the necessary ingredients that make them an intelligent deliverable that encourages conversation and collaboration, and the role they can play in effecting real change in large organizations. Read More