Nested Object Matrix

UX & Product Architecture • Design Systems & Engineering

A Nested Object Matrix (NOM) is an ORCA grid that lists the same object types across its columns and down its rows. Each intersection describes how instances of one type relate to instances of the other. Teams use it to investigate relationships and identify where users may need access to related records.

How do you read a Nested Object Matrix?

In Sophia Prater’s convention, the top row contains the host objects. Read a cell by starting with the column heading and describing how that host relates to the object type on the left. Use verbs and counts where you know them. To check the reverse direction, swap the row and column. Trip → Booking answers which bookings are on a trip. Booking → Trip answers which trip owns the booking.

A Nested Object Matrix for travel operations

In this example, a trip can exist before it has a booking. Each booking belongs to exactly one trip. Travelers may appear on multiple trips.

Related object ↓ / Host object → Trip Booking Traveler
Trip — Belongs to exactly one trip Can be linked to multiple trips
Booking Has zero or more bookings — —
Traveler Can include multiple travelers — —

A dash marks a cell with no direct relationship in this example. In a working matrix, mark an untested relationship as “To verify” so the team can distinguish it from an empty cell. For example, a booking can lead to travelers through its trip. If the product needs to identify which travelers are covered by a particular booking, investigate that as a separate relationship.

How do you build the matrix?

  1. List the same object types on both axes. Start with the shortlist from noun foraging.
  2. Describe each relevant relationship in plain language. Put distinct relationships in the same cell when the same object types connect in several ways.
  3. Check minimums and maximums in both directions. “Has bookings” leaves open whether the first booking is required. Write the cardinality explicitly when a rule is known. Teams use ORCA Relationship Requirements (MCSFD) to detail mechanics, sorting, and filtering, and introduce a Junction Object when the connection itself carries data.
  4. Decide what users need to reach. Test whether an agent who opens a booking from search can find its trip. Check that the trip is visible to that agent before adding the link.

The matrix focuses on relationships. The object map builds on those findings to organize the information that describes each object. A CTA Matrix records what different roles can do with them.

Sources