# Object-Oriented UX

Object-oriented UX models a product around the meaningful objects users recognize, their attributes, relationships, and available actions.

- Type: framework
- Domain: Experience & interface
- Level: Advanced
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/object-oriented-ux/>)

## What it means

Object-oriented UX \(OOUX\) is an approach associated with Sophia Prater that begins by identifying the objects in a domain before designing task flows. An object might be a property, event, patient, project, or playlist. Teams define each object’s attributes, relationships, calls to action, and recognizable visual representation so the product behaves as a coherent system.

## Why it matters

Flows change as features and policies evolve, but core domain objects are often more stable. Modeling them explicitly can reveal missing relationships, duplicated concepts, and inconsistent actions before screens multiply. It also helps cross-functional teams connect interface components, content models, permissions, and backend entities around shared language.

## When to use it

Use OOUX for products with many interrelated entities, repeated object views, or several ways to reach the same item. It is useful in marketplaces, social products, enterprise tools, healthcare, and knowledge systems. A simple linear transaction may not need the additional modeling ceremony.

## How it works

1. Collect nouns from research, requirements, and domain language, then distinguish true objects from attributes, roles, and interface containers.
2. Prioritize the objects users must recognize and define their essential attributes and identity cues.
3. Map relationships, including direction, cardinality, ownership, and the context in which related objects should appear.
4. Define calls to action, permissions, lifecycle states, and consistent representations for each object.
5. Prototype object-based navigation and flows, then test whether users can recognize objects and predict available actions.

## A practical example

A property-management platform models Property, Unit, Tenant, Lease, Payment, and Maintenance Request as connected objects. Every property view shows stable identity cues and related units; a tenant links to an active lease and payments. Actions such as “Record payment” appear only where the relationship and permissions make sense.

## Where it breaks

Not every noun deserves to become an object, and premature modeling can harden assumptions before research. OOUX does not replace journey design, service design, or attention to emotional context; users still arrive with goals and constraints. Existing technical data models may also conflict with the user-facing conceptual model.

## Common mistakes

- Treating every noun in requirements as an equally important object.
- Designing object cards without defining relationships, states, and permissions.
- Assuming an object model eliminates the need to test end-to-end tasks and journeys.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/object-oriented-ux/#visualization-object-oriented-ux>)

## Sources

1. [Object Oriented UX](<https://ooux.com/>) — OOUX · Original method site
2. [Object-Oriented UX](<https://alistapart.com/article/object-oriented-ux/>) — A List Apart · Original-author article
3. [Sophia V. Prater](<https://ooux.com/people/sophiavprater>) — OOUX · Author profile

## Related topics

- [Ontology](<https://wiki.soroush.uk/topic/ontology/>)
- [Information Architecture](<https://wiki.soroush.uk/topic/information-architecture/>)
- [Navigation Design](<https://wiki.soroush.uk/topic/navigation-design/>)
