ORCA Framework

UX & Product Architecture • Product Strategy & Growth

The ORCA framework is Sophia Prater’s process for applying Object-Oriented UX (OOUX). ORCA stands for Objects, Relationships, Calls to action (CTAs), and Attributes. Teams use it to turn user research into a model of a product’s objects, their connections, available actions, and information.

Object-Oriented UX provides the design principles. ORCA provides activities for defining the model and using it to design and test interfaces.

What does ORCA stand for?

Consider one illustrative object in a support tool, Ticket #1042 about a missing invoice.

ORCA element Ticket example
Object Ticket is the object type. Ticket #1042 is one instance.
Relationships Linked customer — Acme Studio. Assigned agent — none.
Calls to action A supervisor can reopen the ticket after selecting an agent.
Attributes Subject — Missing invoice. Status — Closed. Priority — Normal.

Customer and Agent are objects with their own records. The ticket links to those records through relationships. Status and priority describe the ticket as attributes.

How does the ORCA process work?

Prater’s full ORCA process has 15 steps across four iterative rounds. The four elements are revisited and refined throughout the process.

  1. Discovery. Identify objects from research through Noun Foraging. Map their relationships with a Nested Object Matrix, record actions by object and role in a CTA Matrix, and build an initial object map. Capture questions for further research.
  2. Requirements. Define relationship rules using ORCA Relationship Requirements (MCSFD), permissions, and required fields. Document object definitions in an Object Guide and expand the CTA matrix into user stories with conditions for each action.
  3. Prioritization. Object Prioritization decides what belongs in the release and which information and actions deserve prominence in the interface.
  4. Representation. Turn the model into cards, lists, detail views, and a connected prototype. Test whether users recognize the objects, find their connections, and understand the available actions.

This sequence provides a starting point. The rounds can be adapted to the project. Prater describes moving Prioritization ahead of detailed Requirements when time is limited. Prioritizing Prioritization for Product Designers, Sophia Prater

An ORCA example in practice

For Ticket #1042, the reopening rule connects a user role, the ticket’s status, and its relationship to an agent. These requirements guide who sees the action, when it is available, and what information is needed to complete it.

The team can prototype the ticket view to test whether supervisors can find the action and understand why they need to assign an agent.

When should you use ORCA?

Use ORCA when a team needs to agree on connected objects, role permissions, or business rules before designing screens. It helps prevent fragmented systems and common pitfalls like the Four UX Fails in OOUX. Start with one object and a real task. Check the model with users and domain experts, and return to research wherever important questions remain unanswered.

Sources