GOMS¶

A human–computer interaction modeling family representing skilled task performance through goals, operators, methods and selection rules.

Version: v2 · 2026-09-19 · History
Domain-specific #: 4752
Domain group: Professional & Organizational Practice
Origin domain: Human-Computer Interaction (HCI)

Core Idea¶

KLM, CMN-GOMS, NGOMSL and CPM-GOMS make different assumptions about cognition, learning and parallel activity; models best predict routine expert behavior rather than discovery or error-rich work. An analyst decomposes a user goal into alternative methods, primitive perceptual, cognitive and motor operators and rules selecting a method, then derives qualitative structure or predicted execution time. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.

How would you explain it like I'm…

Tiny Steps Stopwatch

Imagine timing how long it takes a grown-up who is really good at a game to finish one level. GOMS breaks the job into tiny steps like look, think and press, and adds up how long each step takes. That lets people guess how fast an expert will be before anyone tries it. It works best for jobs people already know well, not when they are still figuring things out.

Goals-and-Steps Time Guess

GOMS is a way for people who design computer screens to predict how a skilled user will do a task. You start with the user's Goal, list the Methods they could use, break each method into small Operators like reading, deciding, clicking or typing, and write Selection rules for picking a method. If you know roughly how long each small step takes, you can add them up to predict the total time. GOMS is good at predicting smooth, practiced work. It is not good at predicting what happens when someone is exploring or making lots of mistakes.

Expert Task Timing Model

GOMS stands for Goals, Operators, Methods and Selection rules. An analyst breaks a user's goal into possible methods, breaks those methods into basic perceptual, mental and motor operators, and writes selection rules saying when each method is chosen. From this you can predict execution time or compare how two interfaces are structured. Versions such as KLM, CMN-GOMS, NGOMSL and CPM-GOMS make different assumptions, for example about learning or about doing things in parallel. GOMS is good at predicting routine expert behavior, not discovery or error-heavy work. A model only counts as a real GOMS analysis if the users, task, operators, timings and assumptions are spelled out.

GOMS is a task-analytic modeling framework in HCI. A user goal is decomposed into alternative methods. Each method is a sequence of primitive perceptual, cognitive and motor operators, and selection rules determine which method applies in a given context. The model yields either qualitative structure, such as method complexity or consistency, or quantitative predictions such as execution time. The variants embody different assumptions. KLM sums operator times at the keystroke level. CMN-GOMS and NGOMSL add hierarchical goal structure and, in NGOMSL's case, learning estimates. CPM-GOMS models overlapping parallel activity with critical-path scheduling. All of them predict routine, skilled, essentially error-free behavior best and generalize poorly to exploratory or error-rich use. A legitimate GOMS claim must make explicit the user population and expertise, the interface and task, goals, operator definitions and timings, methods, selection rules, parallelism and error assumptions, and the validation data and prediction metric. Without these, it is merely a loose task description wearing the label.

Scope of Application¶

GOMS belongs to human computer interaction and is useful where the analyst can specify the typed human computer interaction carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, then evaluate the user population and expertise, interface and task, goals, operator definitions and timing, methods, selection rules, parallelism and error assumptions, validation observations and prediction metric are explicit. The scope is broad within that domain but bounded by the need for the user population and expertise, interface and task, goals, operator definitions and timing, methods, selection rules, parallelism and error assumptions, validation observations and prediction metric are explicit. The entry records a descriptive analytical identity; practical use requires the governing domain's evidence, standards, and safety obligations.

Clarity¶

The abstraction clarifies a crowded vocabulary by making the user population and expertise, interface and task, goals, operator definitions and timing, methods, selection rules, parallelism and error assumptions, validation observations and prediction metric are explicit the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test. A bare label is insufficient because the name GOMS can be used for a formal identity, an implementation, or a neighboring result unless carrier and convention are stated.

Manages Complexity¶

Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to GOMS. GOMS compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.

Abstract Reasoning¶

Identify the carrier. State what the elements, states, objects, or observations are: the typed human computer interaction carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets. Reject examples whose alleged carrier belongs to a different problem.
Lock the constitutive rule. Express the user population and expertise, interface and task, goals, operator definitions and timing, methods, selection rules, parallelism and error assumptions, validation observations and prediction metric are explicit independently of one notation or implementation.

Knowledge Transfer¶

Knowledge transfers strongly among subfields of human computer interaction because they reuse the typed human computer interaction carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, An analyst decomposes a user goal into alternative methods, primitive perceptual, cognitive and motor operators and rules selecting a method, then derives qualitative structure or predicted execution time., and type the carrier, state every parameter and convention in the definition, test that the user population and expertise, interface and task, goals, operator definitions and timing, methods, selection rules, parallelism and error assumptions, validation observations and prediction metric are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.

Relationships to Other Abstractions¶

Current abstraction GOMS Domain-specific

Parents (1) — outgoing typed relations

GOMS is a kind of Decomposition Prime

It remains its own entry because its identity is fixed by the user population and expertise, interface and task, goals, operator definitions and timing, methods, selection rules, parallelism and error assumptions, validation observations and prediction metric.

Hierarchy path (1) — routes to 1 parentless root

GOMS → is a kind of Decomposition

Neighborhood in Abstraction Space¶

GOMS sits in a crowded region of the domain-specific corpus (8^th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Interface & Interaction Design Methods (20 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-25