frameworkExperience & interface

Object-Oriented UX

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

Download Markdown (.md)

01What 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.[1][2][3]

Design the recognizable domain objects before task flows Attributes, relationships, actions, and states make each object predictable
Recognizable domain object
Identity
Name and cues that distinguish one instance
Attributes
Essential information people need about it
Relationships
Direction, cardinality, ownership, and context
Calls to action
What people can do with or to it
States
Lifecycle and status changes over time
Representation
Consistent appearance across navigation and flows

OOUX complements journey and service design; not every noun is an object, and the user-facing model need not mirror a technical database.

02Why 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.

03When 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.

04How 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.

05A practical example

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.

06Where 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.

07Sources

  1. Object Oriented UXOOUX · Original method siteObject Oriented UX
  2. Object-Oriented UXA List Apart · Original-author articleObject-Oriented UX
  3. Sophia V. PraterOOUX · Author profileSophia V. Prater
View saved topics

Start typing to search titles, definitions, categories, and frameworks.