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
About six months ago, I left Facebook cold turkey. I had tried leaving it before, but always ended up going back. It wasn’t the not‑so‑subtle hints or wanting to see the pictures of all my friends—or at least people with whom I’d connected on Facebook—that drove me back, but fear of missing out (FOMO). What if something happened to someone, and I wasn’t aware of it? What if I thought of a witty one-liner and couldn’t share it immediately with a group of people, then bask in the adulation they would inevitably provide in response to my genius? What about that important political opinion about Trump or Brexit that I’d need to share among my fellow right‑thinking people?
You know what happened? Nothing. Nothing bad, at any rate.
Breaking Free of Addictive User Experiences
I had decided that the price I was paying for being on Facebook was too high. I’d get drawn into arguments and find myself getting annoyed and frustrated. Something is wrong on the Internet! I’d find myself checking my account far too frequently. There’s nothing inherently wrong with either of those things—except that they took time away from other, more important things that I felt I should be doing. I’d read an excellent piece about why one person left World of Warcraft. 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