Object Mapping

UX & Product Architecture • Design Systems & Engineering

Object mapping is the practice of organizing the things users work with into a shared model of object types, relationships, attributes, and available actions. In Object-Oriented UX (OOUX), an object map helps teams decide what information and actions belong together before designing screens.

How do you create an object map?

  1. Find candidate objects. Look for nouns in interviews, workflows, and support requests through Noun Foraging. Check which things users recognize, refer to repeatedly, and need to distinguish from one another in an Object Guide. Check which things users recognize, refer to repeatedly, and need to distinguish from one another.
  2. Describe each object. Capture the information users need to identify it and make decisions about it. For a booking, that might be its confirmation number and status.
  3. Map relationships and actions. Ask what each object connects to, what users need to do with it, and which roles can act. Keep uncertain rules visible for follow-up.
  4. Walk through a real task. Try a routine case and an exception. Revise the map when either case exposes missing information, a connection, or an action.

An object type describes a class of things, such as Booking. Booking B-52 is one instance. Booking status describes the booking. Traveler is a separate object in this example because agents look up travelers, update their details, and view their other trips.

Object map example for travel operations

Object type Useful attributes Relationships Example action
Trip Reference, travel dates Bookings and travelers Add a booking
Booking Reference, status, supplier confirmation number when available One trip Request cancellation if eligible
Traveler Name, contact details Trips they are associated with Update contact details

For an agent handling a cancellation, the map suggests a path from Trip to Booking. A booking summary can show the reference and status so the agent can pick the right record. The state transition matrix specifies what happens after an eligible agent requests cancellation.

How does the object map fit into ORCA?

ORCA gives teams several ways to investigate an object model. A Nested Object Matrix records relationships between object types. A CTA Matrix records what each role needs to do with each object. Deciding what belongs in the release relies on Object Prioritization, while interface audits watch out for the Four UX Fails in OOUX. The object map organizes attributes by object and builds on the relationships already identified. The example above shows actions alongside those findings for easy reference.

Use the map to decide what belongs in each view. A search result might show the booking reference and status. The detail view can add fare rules and cancellation options while keeping the same reference and status labels.

Sources