Discover published sets by community

Procedure: Break down tasks into subtasks, forming a hierarchy. When to Use It: When you need to understand the structure of a task and its components.

Procedure: Analyze tasks that require significant cognitive activity from users, such as decision-making and problem-solving. When to Use It: When tasks require expert knowledge that is often not explicit.

Procedure: Identify Goals, Operators, Methods, and Selection rules for tasks to model user behavior. When to Use It: When you want to predict human performance times and errors.

Procedure: Assess the time required for an expert user to perform tasks by counting keystrokes and other actions. When to Use It: When you need to evaluate efficiency of interfaces at a micro-level.

Procedure: Analyze the constraints and affordances of a work domain rather than the task specifics. When to Use It: When you need an overview of the system's purpose and potential user goals.

Procedure: Explore the complex interplay between human action and context in a sociocultural framework. When to Use It: When examining tasks within a cultural or social context.

Procedure: Observe and interview users in their natural work environment. When to Use It: When direct context-based user data is required for design.

Procedure: Immerse in the users' environment to observe interactions and behavior over time. When to Use It: When studying users in their natural settings over extended periods.

Procedure: Users verbalize their thoughts while performing tasks. When to Use It: When wanting to understand the user's thought process during task execution.

Procedure: Collect and analyze accounts of significant events (critical incidents) from users. When to Use It: When identifying factors that contribute to the success or failure of task performance.

Procedure: Measure the time and movements involved in task completion to optimize performance. When to Use It: When improving efficiency and productivity by reducing wasted movement and time is the goal.

Procedure: Break down tasks into their fundamental parts to understand the task structure. When to Use It: When designing or analyzing systems by understanding their functional requirements.

Procedure: Step through tasks and evaluate ease of use and discoverability for new users. When to Use It: When assessing a system's usability without extensive user testing.

Procedure: Participants keep a diary of their activities and context over time. When to Use It: When you need longitudinal data on how users interact with a system in daily life.

Procedure: Identify and analyze errors made during task performance to improve system design. When to Use It: When looking to enhance system safety and reliability by understanding error causes.

Procedure: Analyze the frequency and sequence of transitions between task elements. When to Use It: When optimizing the layout of controls or information display for task efficiency.

Procedure: Evaluate how well users perceive, understand, and project situational information. When to Use It: When you want to improve user performance by enhancing their awareness of the situation.

Procedure: Assess the amount and complexity of work assigned to a person or system. When to Use It: When determining if a user or system is overburdened and to balance work distribution.

Procedure: Rank tasks based on perceived time pressure, effort, and psychological stress. When to Use It: When subjective measures of workload are required to complement objective measures.