The match targets users’ world, not the designer’s or the engineering implementation’s world
Aliases: user frame of reference · real-world match · domain language
What it is
The reference point for a match between system and real world is not team structure, service boundaries, data models, or metaphors familiar to designers; it is the objects, order, units, responsibility, and risk in the target users’ task. The same interface belongs to different realities for a clinician, driver, accountant, and student.
Why it happens
Users interpret words, order, and symbols through domain experience. If the interface exposes database tables, internal modules, engineering abstractions, or misleading analogies, they must learn a second world and map answers back to the task; mapping errors become wrong object selection, misunderstood permission, or missed risk. The designer’s world is borrowable only where it overlaps with the user’s.
Studying it
Use contextual interviews, task observation, support text, and card sorting to extract user language, task order, and key objects; compare them layer by layer with the information architecture and API model. Ask target users to explain elements, predict results, and find objects, measuring explanation agreement, misclassification, and help seeking. Do not interview only internal experts.
Where it stops holding
The user’s world is not singular. Novices, experts, managers, and cross-department roles use different languages, and organizational practice varies within one market. Interfaces need a primary task frame plus controlled translation, not every colloquial variant. Engineering detail is sometimes necessary but belongs in diagnostics or advanced layers.
Applying it
- For each core role, write the task vocabulary, event chain, units, responsibility, and risk, then map it to interface structure.
- Replace service names, table names, status codes, and internal project jargon with task objects; move technical detail to diagnostics.
- Invite real roles to interpretation and findability tasks, and record elements they cannot paraphrase.
Related
- Same group: B3.14.2 Metaphors necessarily break where they exceed the original object’s properties; define their boundary in advance · B3.14.3 Terminology consistency outranks terminology accuracy; synonym rotation is read as different concepts · B3.14.4 Numbers, dates, and units should follow users’ local conventions
- Nearby: B3.02 Match with the Real World · T1 Interface Copy and Content
- Search terms:
user mental model·domain language·conceptual fit