Hierarchical Task Analysis (HTA)

Hierarchical Task Analysis is a systematic way of describing how work is arranged in order to fulfill the job’s general aim. It involves identifying in a top down manner the overall aim of the job, then the various sub-jobs as well as the conditions under which they need to be completed to reach that goal. For example, you may have 5 basic duties numbered 1 through 5. Duty 3 might have 3 main tasks which would be numbered 3.1, 3.2, and 3.3. Each main task might have subtasks which would be numbered 3.1.1, 3.1.2, and 3.1.3.

Watch a video about how to do HTA

Design Curriculum (DACUM)

When doing an HTA for the purpose of defining training needs, the DACUM method helps to prioritize tasks and assign them to audience needs such as new hires or veteran employees. One of the differences over traditional HTA is that this method utilizes people who are proficient incumbents within a job and is a rapid 2 day workshop. It is usually limited to 12 main duties, that are each broken into tasks, and tasks are broken into steps.

Both of these basic approaches require more validation steps such as card sorting and scenario testing.

Learn more about DACUM

This method can be used for a lot of different purposes. The main idea is that you have multiple people generating cards and then you group the cards into categories or themes.

A couple of the tools I have used online are Optimal Workshop and Fun Retro

Optimal Workshop offers open card sorting, closed card sorting, and will help create dendrograms.

FunRetro now called EasyRetro is great for creating themes such as during an Agile sprint retrospective or as part of a hierarchical task analysis.

Learn more about EasyRetro

I primarily used this tool to create heatmaps or gaze plots for websites and mobile responsive sites. They have a LOT of new tools used with augmented reality and virtual reality that look very promising.

Learn more about Tobii

Visio is one of those tools that is useful to visualize many things. I have mostly used it for the following:

• Scenarios
• System flows
• Workflows
• Intake processes
• Roles and Responsibilities
• Escalations

Here is a blurred out example for a support flow that shows the type of swimlane document I would commonly use/see when communicating with our business analysts, system architects, and business owners.

Learn more about Visio

These are more conceptual approaches. Generally, each project may employ multiple approaches.

User-centered design

• User is best source for needs
• User is the measurement guide to the designer
• Designer’s role is to translate the users’ needs and goals into a design solution

Activity-centered design

• Focuses on behavior surrounding tasks
• User play a significant role but it is their behavior rather than their goals and needs that are most important

Systems design

• Holistic view
• Focuses on context
• The system is the center of attention
• The users’ role is to set the goals of the system

Genius design

• Relies on the creativity of the designer
• Users’ role is to validate ideas generated by the designer
• Users are not involved in design process

Agile done with dedicated teams, leadership buy-in, and the ability to iterate is a magnificent thing. Agile done without the ability to empower teams is a tough ride. I have even experienced role teams doing agile but then handing off work in a waterfall method to the next role team (such as designers off to programmers). This hybrid “AgileFall” has worked well in some of my experiences as well.

Learn more about Agile and Waterfall

Where does SDLC fit in?

The software development lifecycle (SDLC) is an example of a waterfall method geared towards software deployment. ADDIE is a waterfall method geared towards delivery of training.

Learn more about Agile and SDLC

Ah, where would we be without the foundational work of Don Norman. I originally read this as a recommendation from a Psychology professor when I was an undergraduate. It is rare that some of these principles are not included in one of my project reviews in some shape or form. For example, I was reviewing an Articulate module and said “For items to address, there is a need for constraint on the path choices on the opening slide, the review button has low visibility, and the feedback is inconsistent on the quiz slides” to not only indicate where an issue existed but also why.

Check out the Design of Everyday Things

Learn more about Don Norman at jnd.org

This is also known as the 5 Es. These translate well from training, teaching, interface design, and human factors.

Learn more about Usability Qualities.

When working with a new team, this is one of the first presentations I go over. It seems basic but I find it is a good foundation to then move on to heuristics, design thinking, usability, and user experience.

This is sorta a bridge between user-centered design and agile. There are the principles of empowering the team by making sure everyone understands the problem being solved and doing quick iterations. There is also a strong component of involving the user throughout the process. My favorite part is the ongoing brainstorming sessions. This is why one of my most important office components is a rolling dry erase board.

Learn more about Design Thinking