An Object Guide is a structured glossary of the objects in an Object-Oriented UX (OOUX) model. It records what each object means, how people recognize it, and which distinctions the team needs to preserve in product language and requirements. In ORCA, teams develop the guide during the Requirements round.
What should an Object Guide include?
Start with a short definition and a recognizable example. Add the distinctions that affect the work. The fields below are a lightweight starting point for a travel operations product.
| Field | Example entry for Booking |
|---|---|
| Preferred name | Booking |
| Definition | A record used to arrange travel services with a supplier. It tracks the request from draft through the supplier’s response and any later changes. |
| Instance | Booking B-52 for the outbound flight on Trip T-104. |
| Why it matters | Agents use the booking to track the supplier response, check fare rules, and request changes when eligible. |
| Boundary | An Offer contains proposed travel and pricing. A Booking tracks the supplier request. Accepting the offer and confirming the booking are separate events. |
| Key relationship | Each booking belongs to one trip. A trip may exist before it has any bookings. |
| Open question | Do agents use “reservation” as a synonym for Booking, or only after a supplier has confirmed it? |
Use the definition to decide which record owns each status. The Offer can show Accepted while the Booking shows Awaiting confirmation. That tells an agent the traveler has agreed to the offer and the supplier’s response is still outstanding.
How does the guide work with other ORCA artifacts?
Use the guide to agree on what an object represents. The nested object matrix records its relationships across the model. The CTA Matrix records actions by role, and the object map organizes the information each object needs. Link to those artifacts when an entry needs more detail.
How do you keep an Object Guide useful?
Ask sales and ticketing to classify two records: an offer the traveler accepted and a booking the supplier has yet to confirm. If they disagree on the names or statuses, record the difference and agree on what appears at the handoff.
Review the entry when a change affects its definition, labels, or rules. Link to the decision or research note so the next person can see why the definition changed.