Object prioritization is the ORCA activity of deciding which objects a release needs and how prominently people should encounter them. It helps teams narrow the scope of an object model and choose how users enter it before designing menus and screens.
What are you prioritizing?
Release scope and navigation prominence are separate decisions. A Booking may be essential to the first release while agents can reach it through a Trip and search. The team can give Bookings a main navigation entry later if agents regularly need to work across trips.
Consider what people need to complete the release’s main tasks, how often they need to find the object on its own, and what other objects or actions depend on it. Use work observations and examples from the object map to make the decision concrete.
Example of prioritizing objects for a first release
Suppose a travel operations team starts with one goal: let agents find a trip and manage its bookings.
| Candidate | Release decision | How people reach it |
|---|---|---|
| Trip | Include it as the starting point for managing travel. | Main navigation and search. |
| Booking | Include it so agents can track supplier responses and request cancellation. | Trip details and search by booking reference. |
| Traveler | Keep it as a shared record so agents can recognize the person across trips. | From a trip’s traveler list. |
| Supplier | Show the supplier name as booking information. Defer separate supplier profiles until agents need to manage them. | In booking details. |
The supplier decision reduces the release scope to the information agents use to identify a booking. If agents later need to update supplier contacts or see all bookings for a supplier, revisit the model.
How do you check your decisions?
Walk through a routine task and an exception. In this example, an agent may receive a supplier message with only a booking reference. Check that search gets them to the booking and that the booking links back to the right trip when they have access.
When you combine, defer, or simplify an object, review its relationships, actions, and attributes. Decide which information or behavior the release still needs and where it belongs. Record the evidence that would change your decision, such as agents repeatedly needing a queue of bookings across trips.