User analysis¶
A systems-design investigation that characterizes intended users, their goals, capabilities, contexts and workflows to constrain product and documentation decisions.
Core Idea¶
User analysis differs from task analysis though they interact, sampled users must not be mistaken for all users and demographic description without design-relevant behavior and context is insufficient. Researchers gather and triangulate observations, interviews, artifacts and usage evidence, segment users by relevant characteristics and translate recurring needs and constraints into requirements, scenarios and design tests. 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.
Scope of Application¶
User analysis belongs to human centered design and is useful where the analyst can specify the typed human centered design carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets, then evaluate the product and decision scope, intended and excluded user populations, recruitment and sampling, goals and workflows, knowledge skills accessibility and constraints, physical social and technical context, evidence methods, segmentation and uncertainty, derived requirements or personas and traceability to design choices are explicit.
Clarity¶
The abstraction clarifies a crowded vocabulary by making the product and decision scope, intended and excluded user populations, recruitment and sampling, goals and workflows, knowledge skills accessibility and constraints, physical social and technical context, evidence methods, segmentation and uncertainty, derived requirements or personas and traceability to design choices 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.
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 User analysis. User analysis 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 centered design carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets. Reject examples whose alleged carrier belongs to a different problem. 2. Lock the constitutive rule. Express the product and decision scope, intended and excluded user populations, recruitment and sampling, goals and workflows, knowledge skills accessibility and constraints, physical social and technical context, evidence methods, segmentation and uncertainty, derived requirements or personas and traceability to design choices are explicit independently of one notation or implementation.
Knowledge Transfer¶
Knowledge transfers strongly among subfields of human centered design because they reuse the typed human centered design carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets, Researchers gather and triangulate observations, interviews, artifacts and usage evidence, segment users by relevant characteristics and translate recurring needs and constraints into requirements, scenarios and design tests., and type the carrier, state every parameter and convention in the definition, test that the product and decision scope, intended and excluded user populations, recruitment and sampling, goals and workflows, knowledge skills accessibility and constraints, physical social and technical context, evidence methods, segmentation and uncertainty, derived requirements or personas and traceability to design choices are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.
Relationships to Other Abstractions¶
Current abstraction User analysis Domain-specific
Parents (1) — more general patterns this builds on
-
User analysis is a kind of Evaluation Prime
The proposed strict upward parent is
prime:evaluation.
Hierarchy path (1) — routes to 1 parentless root
- User analysis → Evaluation → Comparison → Self Checking
Neighborhood in Abstraction Space¶
User analysis sits in a crowded region of the domain-specific corpus (20th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.
Family — Human–Computer Interaction & Interface Design (24 abstractions)
Nearest neighbors
- Activity-centered design — 0.92
- User interface design — 0.91
- Natural user interface — 0.91
- Usage-centered design — 0.91
- User interface plasticity — 0.91
Computed from structural-signature embeddings · 2026-09-08