Task Analysis
Task Analysis plays an important part in User Requirements Analysis.
Task Analysis
Task analysis is the procedure to learn the users and abstract frameworks, the patterns used in
workflows, and the chronological implementation of interaction with the GUI. It analyzes the ways in
which the user partitions the tasks and sequence them.
What is a TASK?
Human actions that contributes to a useful objective, aiming at the system, is a task. Task analysis
defines performance of users, not computers.
The concept of task has many meanings - from the overall job definition to single operations on
keyboard. Here we use a three level concept structure
Goals
Tasks
Actions
A Goal can be defined as something the user wished to achieve. Goal can be for example: write a letter -
make an order - deposit money. To reach a goal the user usually needs a plan which involves a set of
tasks to be performed in order to reach the goal.
A Task is the series of activities or actions required to achieve a goal. A task is a structured set of
activities. The task can involve problem solving or selecting between alternative actions (or sub tasks)
An Action is a 'simple task' which requires no problem solving. An action has no structure
The tasks can be described as hierarchies. For example the use of a word processing system can be
described as a hierarchy of subtasks which can be taken alternatively or after each others in order to
reach the overall goal.
Task analysis steps
Goal -> What to do
Select the Device or Method -> Determines the task in concrete terms
Task -> activities to achieve the goals using the device
Subtask - components of a task
Actions - simple tasks
Hierarchical Task Analysis
Hierarchical Task Analysis is the procedure of disintegrating tasks into subtasks that could be analyzed
using the logical sequence for execution. This would help in achieving the goal in the best possible way.
"A hierarchy is an organization of elements that, according to prerequisite relationships, describes the
path of experiences a learner must take to achieve any single behavior that appears higher in the
hierarchy. (Seels & Glasgow, 1990, p. 94)".
Techniques for Analysis
Task decomposition − Splitting tasks into sub-tasks and in sequence.
Knowledge-based techniques − Any instructions that users need to know.
User is always the beginning point for a task.
Ethnography − Observation of users behavior in the use context.
Protocol analysis − Observation and documentation of actions of the user. This is achieved by
authenticating the users thinking. The user is made to think aloud so that the users mental logic can be
understood.
What is Fitts’ Law?
Fitts’ law states that the amount of time required for a person to move a pointer (e.g., mouse cursor) to
a target area is a function of the distance to the target divided by the size of the target. Thus, the longer
the distance and the smaller the target’s size, the longer it takes.
In 1954, a psychologist named Paul Fitts created a predictive model that describes how quickly people
can select a target.
A target is what the user is trying to interact with. It could be a button to tap or a form field that needs
to be clicked into. This model is commonly used in human-computer interaction.
Fitts’s Law establishes that the further away a target is and the smaller the size of the target, the longer
it takes for a user to acquire.
Large targets that are close by have the lowest interaction cost, while small targets that far away have
the highest interaction costs.
But what is an interaction cost?
Interaction costs
The Nielsen Norman Group defines interaction costs as “the sum of efforts—mental and physical—that
the users must deploy in interacting with a site to reach their goals.”
So, if a user can find an answer they’re looking for without needing to scroll, tap, or explore, they’re
experiencing zero interaction cost. If a user has to locate a menu, scroll through over a dozen options,
and click a small button to complete their form, that’s going to be a higher interaction cost.
Ideally, UX and UI designers aim to make these costs as low as possible. The lower the interaction cost,
the better the usability of their app.
Designers can minimize interaction costs by following Fitts’s Law and minimizing reading, scrolling,
clicking, typing, waiting for pages to load, attention switches, memory load, and exploring to find
relevant information.
The Fitts’s Law equation
Fitts’s Law states that the time it takes to acquire a target is a function of the size of the target and the
distance to the target.
Here’s the equation:
MT = a + b * log₂ (2D/W)
Let’s break that down:
MT is the time it takes to select a target
a + b are constants set by the type of device
D is the distance from the starting point to the target
W is the width of the target along the axis of motion
Typical applications of Fitts’s Law
While these applications may seem like common sense, they’re important to point out. Why?
Because Fitts’s Law is one of the most ignored psychological principles of design!
Here are some examples of it being used:
A button to complete an action that is close to the active elements
Important elements that are made larger so that they’re easier to select.
Interactive lists that are as short as possible
The shortest path to the desired CTA
Menus are in the top corners of the screen on desktops and the bottom of the screen on mobile
2. How does Fitts’s Law apply to UI design?
Essentially, this principle can be noticed throughout any interface that involves using a mouse or finger.
It’s used in user interface design to decide the proper sizes of interactive elements, the best location for
them, and to notice potential usability issues.
Fitts’s Law brings safety, convenience, and usability into UI design.
Consider safety measures for heavy machinery: the shutdown button is almost always large, red, and
easier to press than the startup button. Convenience in mobile apps would be those that make their
login buttons fit within the thumb zones.
Fitts’s Law is the reason buttons on websites are large, and menus are usually located in the upper
corners of your screen.
UI designers can tell people what to do by placing significant calls to action close to related forms or
headlines. This is where users expect to see them and can easily click them with low effort.
Fitts’s Law concepts for UI Design
Size: larger targets are usually best. Try large elements, that have clear boundaries, and are entirely
clickable.
Distance: minimize movement. Think about the space between buttons, locating important actions by
the prime pixel and thumb zones, and decrease the distance between elements with a similar function.
This is similar to the Gestalt principle of proximity.
Effort: use prime and magic pixels. Make your interactive elements easy to click and easy to find.
What is the prime pixel?
The prime pixel is where a user’s cursor is located on the screen when they open a website or
application. It’s the point where the user will carry out all of their tasks from.
This is why right-click menus exist—they’re naturally closest to the prime pixel.
On mobile devices, the prime pixel is the area where your thumbs naturally hover. They are also known
as the thumb zones.
You’ll notice that menus on your iPhone are usually at the bottom of the screen where your thumbs are.
Ideally, designers would make all of their desired calls to action as close as possible to that point.
However, the prime pixel isn’t totally predictable because the user’s starting point is usually different
every time.
While it’s nearly impossible to predict the exact prime pixel, it is possible to predict the likely prime pixel
based on the actions taken by the user while using your application. Here are three examples of that:
Google’s search bar is always located in the middle of the screen, with the search button directly next to
it
Logins are usually located in the upper right-hand corner of a website’s navigation
Forms are typically in the direct middle of the page with a large “submit” button at the end of the form
What are magic pixels?
Magic pixels are the four corners of a screen, the top edge, and the bottom edge of a screen. The magic
pixels create boundaries. Your cursor cannot move beyond these points. They are almost always the
furthest away from the prime pixel. Designers use conventions like the center of the screen, the corners,
and the thumb zones on mobile as guides for optimal placement because they can’t predict the prime
[Link] a standardized website that’s easy to navigate is just as important as proximity to CTAs, as
you’ll learn by using tricks such as the Rule of Thirds.
Because they are so far from the prime pixel, magic pixels are typically reserved for standard functions.
You’ll notice that exit, minimize, account controls, log-in, and full-screen buttons are in the top corners
of your screen.
Even though they aren’t usually close to the prime pixel, the corners and edges of the screen are always
in the same place, and you can’t move past them. That makes them easy to reach quickly. Web
designers won’t be able to take advantage of the corners of the screen as efficiently as a native user
interface can.
Thus, they rely on the next-best zone of magic: the center of the screen.
Design rules for interactive systems
Design rules are rules that a designer can follow in order to increase the usability of the system or
product.
We can these rules into three categories. Those are principles, standards and guidelines.
Principles -Abstract and have high generality & low in authority. Widely applicable and enduring. e.g.
interface should be easy to navigate
Guidelines - Can guide or advise on how achieve a principle Narrowly focused. Can be too specific,
incomplete, & hard to apply but they are more general and lower in authority than Standards. e.g. use
this button to save data
Standards- which are very specific & high in authority. e.g. use colour RGB #1010D0 on home links
Usability Principles
Principles of Learnability —
the ease with which new users can begin effective interaction and achieve maximal performance (e.g.
Predictability, Synthesizability, Familiarity, Generalizability, Consistency.)
Predictability: support for the user to determine the effect of future action based on past interaction
history.
Synthesizability: support for the user to assess the effect of past operations on the current state.
Familiarity: the extent to which a user’s knowledge and experience in other real world or computer-
based domains can be applied when interacting with a new system.
Generalizability: support for the user to extend knowledge of specific interaction within and across
applications to other similar situations.
Consistency: likeness in input-output behavior arising from similar situations or similar task objectives.
Principles of Flexibility—the multiplicity of ways the user and system exchange information (e.g.
Dialogue initiative, Multithreading, Task migratability, Substitutivity, Customizability.)
Dialogue initiative: user freedom from artificial constraints on the input dialog imposed by the system.
Multithreading: the ability of the system to support user interaction for more than one task at a time.
Task migratability: the ability to transfer control for execution of tasks between the system and the user
(e.g. spell-checking task).
Substitutivity: the extent to which an application allows equivalent input and output values to be
substituted for each other
Customizability: the ability of the user or the system to modify the user interface.
Principles of Robustness—the level of support provided to the user in determining successful
achievement and assessment of goal-directed behavior (e.g. Observability, Recoverability,
Responsiveness, Task conformance)
Observability: the extent to which the user can evaluate the internal state of the system from the
representation on the user interface.
Recoverability: the extent to which the user can reach the intended goal after recognizing an error in
the previous interaction.
Responsiveness: a measure of the rate of communication between the user and the system.
Task conformance: the extent to which the system services support all the tasks the user would wish to
perform and in the way the user would wish to perform.
Norman’s 7 Principles
1. Use both knowledge in the world and knowledge in the head.
2. Simplify the structure of tasks.
3. Make things visible: bridge the gulfs of Execution and Evaluation.
4. Get the mappings right.
5. Exploit the power of constraints, both natural and artificial.
6. Design for error.
7. When all else fails, standardize.
Ben Shneiderman’s 8 Golden Rules
To improve the usability of an application it is important to have a well designed interface.
Shneiderman’s “Eight Golden Rules of Interface Design” are a guide to good interaction [Link] for
consistency: layout, terminology, command usage, etc.
2. Cater for universal usability: recognize the requirements of diverse users and technology. For instance
add features for novices eg explanations, support expert users eg shortcuts.
3. Offer informative feedback: for every user action, offer relevant feedback and information, keep the
user appropriately informed, human-computer interaction.
4. Design dialogs to yield closure: help the user know when they have completed a task.
5. Offer error prevention and simple error handling: prevention and (clear and informative guidance to)
recovery; error management.
6. Permit easy reversal of actions: to relieve anxiety and encourage exploration, because the user knows
s/he can always go back to previous states.
7. Support internal locus of control: make the user feel that s/he is in control of the system, which
responds to his/her instructions/commands.
8. Reduce short-term memory load: make menus and UI elements/items visible, easily
available/retrievable.
Evaluation techniques for interactive systems
What is evaluation
Evaluation role is to access designs and test systems to ensure that they actually behave as we expect
and meet user requirements. Ideally, evaluation should occur throughout the design life cycle, with the
results of the evaluation feeding back into modifications to the design.
Goals of evaluation
Evaluation has three main goals:
To assess the extent and accessibility of the system’s functionality -
Evaluation at this level may measuring the user’s performance with the system to assess the
effectiveness of the system in supporting the task.
Eg: if a filing clerk is used to retrieving a customer’s file by the postal address, the same capability (at
least) should be provided in the computerized file system.
To assess users’ experience of the interaction -
Important to assess the user’s experience of the interaction and its impact upon user. How easy the
system is to learn, its usability and the user satisfaction with it. It may include his enjoyment and
emotional response, particularly in the case of aim to entertainment.
To identify any specific problems with the system.-
This may aspects of the design which, when used in their intended context, cause unexpected results, or
confusion amongst user. Related to both the functionality and usability of the design
Evaluation through expert analysis
Cognitive walkthrough
Originally proposed by Polson and colleagues as an attempt to introduce psychological theory into the
informal and subjective walkthrough technique. The main focus is to establish how easy a system is to
learn (by hands on, not by training or user’s manual).
To do a walkthrough,
1. A specification or prototype of the system (doesn’t have to be complete, but it should be fairly
detailed. Details such as the location and wording for a menu can make a big difference.)
2.A description of the task the user is to perform on the system. This should be a representative task
that most users will want to do
3.A complete, written list of the actions needed to complete the task with the proposed system
[Link] indication of who the users are and what kind of experience and knowledge the evaluators can
assume about them
For each task walkthrough considers
●what impact will interaction have on user?
● what cognitive processes are required?
●what learning problems may occur?
Heuristic evaluation
Proposed by Nielsen and Molich. Heuristic is a guideline or general principle or rule of thumb that can
guide a design decision or be used to critique a decision that has already been made. Design examined
by experts to see if these are violated (3 to 5 enough).Eg: system behavior is predictable, system
behavior is consistent, feedback is provided
Nielsen’s ten heuristics are:
Visibility of system status- Always keep users informed about what is going on, through appropriate
feedback within reasonable time. Eg: if a system operation will take some time, give an indication of
how long and how much is complete.
2. Match between system and the real world : system should speak the user’s language, with words,
phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world
conventions, making information appear in natural and logical order.
3. User control and freedom : Users often choose system functions by mistake and need a clearly
marked ‘emergency exit’ to leave the unwanted state without having to go through an extended dialog.
b. Support undo and redo
4. Consistency and standards: Users should not have to wonder whether words, situations or actions
mean the same thing in different contexts. Follow platform conventions and accepted standards.
5. Error prevention: Make it difficult to make errors. Even better than good error messages is a careful
design that prevents a problem from occurring in the first place.
6. Recognition rather than recall: Make objects, actions and options visible. The user should not have to
remember information from one part of the dialog to another. Instructions for use of the system should
be visible or easily retrievable whenever appropriate.
7. Flexibility an efficiency of use :Allow users to tailor frequent actions. Accelerators unseen by the
novice user may often speed up the interaction for the expert user to such an extent that the system can
cater to both inexperienced and experienced users.
8. Aesthetic and minimalist design: Dialogs should not contain information that is irrelevant or rarely
needed. Every extra unit of information in a dialog competes with the relevant units of information and
diminishes their relative visibility.
9. Help users recognize, diagnose and recover from errors
Error messages should be expressed in plain language (no codes), precisely indicate the problem, and
constructively suggest a solution.
10. Help and documentation: Any such information should be easy to search, focused on the user’s task,
list concrete steps to be carried out, and not be too large.
Model-based evaluation
Dialog models can be used to evaluate dialog sequences for problems, eg. Unreachable states, circular
dialogs and complexity. Models such as state transition networks are useful for evaluating dialog designs
prior to implementation.
Evaluation through user participation
User participation in evaluation tends to occur in the later stages of development when there is at least
a working prototype of the system in place.
Evaluation through monitoring physiological responses
Eye tracking
Head or desk mounted equipment tracks the position of the eye and movement reflects the amount of
cognitive processing a display requires.
measurements include;
Number of fixations (The more fixations the less efficient the search strategy)
Fixation duration(Indicate level of difficulty with display)
Scan path(moving straight to a target with a short fixation at the target is optimal)
saccades(rapid eye movement from one point of interest to another)
Physiological measurement
Emotional response linked to physical changes. These may help determine a user’s reaction to an
interface.
measurements include:
Heart activity; blood pressure, volume and pulse.
Activity of the sweat glands; galvanic skin response(GSR)
Electrical activity in muscle; electromyogram (EMG)
Electrical activity in the brain; electroencephalogram(EEG)
Universal Design for Interactive Systems
Universal design is the process of designing products so that they can be used by as many people as
possible in as many situations as possible. Universal design is about designing systems so that they can
be used by anyone in any circumstance.
Universal Design Principles
In the late 1990s a group at North Carolina State University in the USA proposed seven general
principles of universal design. These were intended to cover all areas of design and are equally
applicable to the design of interactive systems. These principles give us a framework in which to develop
universal designs.
[Link] use.
The design is useful and marketable to people with diverse abilities. No user is excluded or stigmatized.
Wherever possible, access should be the same for all; where identical use is not possible, equivalent use
should be supported. Where appropriate, security, privacy and safety provision should be available to
all. For example, a website that is designed to be accessible to everyone, including people who are blind
and use screen reader technology, employs this principle.
2. Flexibility in Use.
The design accommodates a wide range of individual preferences and abilities, through choice of
methods of use and adaptivity to the user’s pace, precision and custom. An example is a museum that
allows visitors to choose to read or listen to the description of the contents of a display case.
3. Simple and intuitive.
Use of the design is easy to understand, regardless of the knowledge, experience, language or level of
concentration of the user. The design needs to support the user’s expectations and accommodate
different language and literacy skills. It should not be unnecessarily complex and should be organized to
facilitate access to the most important areas. It should provide prompting and feedback as far as
possible. Science lab equipment with clear and intuitive control buttons is an example of an application
of this principle.
4. Perceptible information.
the design should provide effective communication of information regardless of the environmental
conditions or the user’s abilities. Redundancy of presentation is important: information should be
represented in different forms or modes (e.g. graphic, verbal, text, touch). Essential information should
be emphasized and differentiated clearly from the peripheral content. Presentation should support the
range of devices and techniques used to access televisioninformation by people with different sensory
abilities. An example of this principle is captioned programming projected in a noisy sports bar.
5. Tolerance for error.
Minimizing the impact and damage caused by mistakes or unintended behavior. Potentially dangerous
situations should be removed or made hard to reach. Potential hazards should be shielded by warnings.
Systems should fail safe from the user’s perspective and users should be supported in tasks that require
concentration. An example of a product applying this principle is software applications that provide
guidance when the user makes an inappropriate selection.
6. Low physical effort.
Systems should be designed to be comfortable to use, minimizing physical effort and fatigue. The
physical design of the system should allow the user to maintain a natural posture with reasonable
operating effort. Repetitive or sustained actions should be avoided.
7. Size and space for approach and use.
Appropriate size and space is provided for approach, reach, manipulation, and use regardless of the
user’s body size, posture, or mobility. A flexible work area designed for use by employees who are left-
or right-handed and have a variety of other physical characteristics and abilities is an example of
applying this principle.
These seven principles give us a good starting point in considering universal design.
Multi-modal interaction
Providing access to information through more than one mode of interaction. Situation where the user is
provided with multiple modes for interacting with the system. There are five senses, sight, sound, touch,
taste and smell. A Multi-modal interface acts as a facilitator via these modes of interaction. Used in a
range of applications: particularly good for users with special needs, and virtual reality. e.g. visual and
aural senses: a text processor may speak the words as well as echoing them to the screen.
Sound in the interface
An important multi model interaction to usability. More widespread effective use of sound in the
interface would alleviate the problems faced by visually impaired people. There are two types of sound
that we could use,
Speech - The term speech interface describes a software interface that employs either human speech or
simulated human speech .Complexity of the language makes speech recognition and synthesis by
computer very difficult.
e.g. The phonetic typewriter- The phonetic typewriter is the device which is to convert the human voice
into typed letters. Though amplitudes, timbers, and durations of the speech wave coming into the ear
are various, these speech sounds are changed into a definite letter set when the hands strike the keys of
a typewriter. One reason that the phonetic typewriter was able to achieve acceptable levels of
recognition and transcription is that Finnish is a phonetic language, that is one which is spelt as it
sounds.
The phonetic typewriter
[Link]-speech -Non-speech sounds can offer a number of advantages. As speech is serial, we have to
listen to most of a sentence before we understand what is being said. Non-speech sounds can often be
assimilated much more quickly. Speech is language dependent- a speech-based system requires
translation for it to be used for another language group. The meaning of non-speech sounds can be
learned regardless of language. Speech requires the user’s attention. Non-speech sound can make use of
the phenomenon of auditory adaptation: background sounds are ignored unless they change or cease.
Commonly used for warnings and alarms. It is often used to provide transitory information, such as
indications of network or system changes, or of errors. It can also be used to provide status information
on background processes, since we are able to ignore continuous sounds but still respond to changes in
those sounds. Non-speech sound can also be used to provide a second representation of actions and
objects in the interface to support the visual mode and provide confirmation for the user.
Touch in the interface
Touch interface is where the users can interact with the machine using the sense of touch. Users can use
their hands or a stylus to touch the screen when making selections on the machine. This interface much
relies on graphical user interface(GUI) which allows user to see what they should touch when making a
selections. In some cases of visual impairments, there is a level of interactions based upon tactile or
braille input. Touch sensitive interfaces can be found on many mobile devices such as a smart phone or
a tablet computer.
Handwriting recognition
Handwriting is another communication mechanism which we are used to in day-today life. Handwriting
consists of complex strokes and spaces .Captured by digitizing tablet and strokes transformed to
sequence of dots .Large tablets are suitable for digitizing maps and technical drawings. Smaller devices,
some incorporating thin screens to display the information (PDAs such as Palm Pilot)
Gesture recognition
Gesture recognition is a type of perceptual computing user interface that allows computers to capture
and interpret human gestures as commands. The general definition of gesture recognition is the ability
of a computer to understand gestures and execute commands based on those gestures.
Designing Interfaces for diversity
Human capabilities are different needs and limitations. Normally interface is designed for average users.
People are diverse, thus it is important to consider many factors when we want to apply universal
design. Factors to consider;
Disability
Age
Culture
Disability
visual impairment
These days, the standard interface is graphical. The use of this reduces the possibilities for them. We use
following devices to help them.
Peripherals-screen readers, braille output, Sonic Finder
Sound-speech, earcons, auditory icons
Touch-tactile interaction, force feedback devices
hearing impairment
Less impact on graphical interface compared to visual impairment. Computers enhance communication
opportunities for them.
text communication, gesture, captions physical impairment vary in control and movement abilities.
speech I/O, eyegaze system(track eye movements to control cursors), gesture, predictive systems (e.g.
Reactive keyboard-anticipate the commands to be typed and executed)
speech impairment
speech synthesis, text communication
dyslexia
Difficulty with learning to read fluently
Severe-speech input, output
Non-severe-spelling correction facilities
Consistent navigation structure, clear signposting cues
Color coding information, graphical information
autism
Impaired social interaction and verbal and non-verbal communication
Communication-computer-mediated communication, virtual environments, graphical information
Education-virtual environments, games for social situations and appropriate responses.
age groups
Older people e.g. disability aids, memory aids, communication tools to prevent social isolation.
children e.g. appropriate input/output devices, involvement in design process
cultural differences
influence of nationality, generation, gender, race, sexuality, class, religion, political persuasion etc. on
interpretation of interface features ;
Language-translations, layouts(reading patterns)
Cultural symbols
Gestures-movement of bodies.
Use of colors-red(life- India, happiness-China, royalty-France),green(fertility-Egypt, youth-China, safety-
USA)
Designers and users use their understanding, perspectives and experience in a variety of environments.
The more we learn about people and the choices they may wish as they interact with the environments,
the better we become. Because of this, no one knows it all. We can all learn from each other about how
to better design things for all people.
What is GOMS in Computing? (Goals, Operators, Methods, And Selection Rules)
The GOMS Model: Understanding Goals, Operators, Methods, and Selection Rules in Computing
When it comes to understanding the intricacies of computing, one must delve into the world of human-
computer interaction (HCI). The GOMS model, an acronym for Goals, Operators, Methods, and Selection
Rules, is a framework that provides a systematic approach to studying and analyzing user behavior and
performance in computing systems. By breaking down complex tasks into smaller components, the
GOMS model allows for a deeper understanding of the cognitive processes involved in human-computer
interaction.
The Importance of Goals in Computing
Goals play a vital role in human-computer interaction as they provide a clear direction for users. In
computing, goals can be defined as the desired outcomes or objectives that users aim to achieve
through interacting with a system or software. These goals can vary from simple tasks, such as sending
an email, to more complex ones, like designing a website.
When designing a computing system
When designing a computing system, it is crucial to identify and understand the goals of the users. This
knowledge allows developers to create intuitive interfaces and efficient workflows that align with the
users' objectives. By incorporating user-centered design principles, developers can ensure that the
system supports users in achieving their goals effectively and efficiently.
Operators, Methods, and Selection Rules: The Building Blocks of User Actions
Operators, methods, and selection rules are the building blocks that users employ to accomplish their
goals within a computing system. These elements define the specific actions and strategies that users
utilize to interact with software or hardware.
Operators refer to the basic actions or commands that users perform to interact with a system. These
actions can include clicking a button, typing on a keyboard, or selecting an option from a dropdown
menu. Operators are the lowest-level actions that users can take in a computing environment.
Methods, on the other hand, are sequences of operators that users employ to complete a task or
achieve a goal. Methods provide a higher-level view of user actions by grouping related operators
together. For example, when composing an email, a user may utilize the method of opening a new
message, typing the content, and clicking the send button.
Selection rules guide users in deciding which method or operator to use in a given situation. These rules
are based on the user's knowledge, experience, and understanding of the system. For instance, when
faced with multiple options, a user may rely on selection rules to determine the most appropriate
method or operator to accomplish a specific task.
Applying the GOMS Model in User Interface Design
The GOMS model provides a valuable framework for user interface (UI) designers to create interfaces
that align with users' goals, minimize cognitive load, and enhance overall user experience. By analyzing
the goals, operators, methods, and selection rules, designers can gain insights into how users interact
with a system and identify areas for improvement.
When designing a user interface, it is essential to consider the following key aspects:
Goal Clarity: Clearly define the goals that users aim to achieve through the system. This clarity ensures
that the interface provides the necessary functionality and features to support users in accomplishing
their objectives.
Efficiency: Streamline the user's workflow by minimizing the number of operators and methods required
to achieve a goal. An efficient interface reduces cognitive load and increases user productivity.
Error Prevention: Anticipate potential errors and design the interface to prevent them. By incorporating
clear instructions, feedback mechanisms, and intuitive layouts, designers can reduce the likelihood of
user errors.
Consistency: Maintain consistency in the design elements, terminology, and interaction patterns
throughout the interface. Consistency enhances learnability and reduces the cognitive effort required to
understand and navigate the system.
By following these principles and incorporating insights from the GOMS model, designers can create
user interfaces that are intuitive, efficient, and user-centric.
Understanding the GOMS model and its components is essential for both developers and designers in
the field of HCI. By breaking down complex tasks into manageable components, the GOMS model
provides a systematic approach to analyzing user behavior and optimizing user interfaces. By
considering the goals, operators, methods, and selection rules, developers and designers can create
computing systems that align with users' objectives and enhance their overall experience