Object-Oriented UX (OOUX) is a design approach that structures digital products around objects in users’ mental models—the things they recognize and expect to work with, such as trips, travelers, and bookings. Teams define these objects, their relationships, attributes, and available actions before designing screens and flows.
What does OOUX look like in practice?
Consider a travel operations tool with trips, travelers, and bookings. Modeling the relationship between a trip and its bookings helps the team decide what agents can navigate to from a trip.
The trip page can list its bookings, with each one opening its details and available actions. An authorized agent can select a booking and cancel it. Its status then updates wherever that booking appears, including the trip page and search results. The object model gives the team a shared basis for navigation, content, and actions.
How does ORCA relate to OOUX?
OOUX provides the design principles. ORCA is Sophia Prater’s process for applying them through Objects, Relationships, Calls to action, and Attributes. Teams revisit these four elements as they discover requirements and refine the model. Introducing ORCA, Sophia Prater
| ORCA element | Design question | Travel operations example |
|---|---|---|
| Objects | What things do people work with? | Trip, Traveler, Booking |
| Relationships | How are those things connected? | A trip includes travelers and bookings. |
| Calls to action | What can each user role do? | An authorized agent can cancel a booking. |
| Attributes | What information describes each object? | A booking has a confirmation number and status. |
An object map records these decisions so the team can use the same model when designing screens, navigation, and flows.
When is OOUX useful?
OOUX is particularly useful when the same objects appear across multiple workflows or when different roles need different actions on an object. For example, a travel agent and an accountant may both work with the same booking, while needing different information and permissions.
Start by examining the things people name in interviews and existing workflows. Use their language to identify candidate objects. Then walk through a task such as “find and cancel a booking.” Check that the model identifies the booking, its connection to the trip, its status, and which roles can cancel it. Teams also use OOUX to diagnose and prevent common interface anti-patterns, described as the Four UX Fails in OOUX—masked, shape-shifting, broken, and isolated objects.