Stop handoff friction. Build a shared system model before wireframing or coding begins.
| Stage | Activity | Outcome |
|---|---|---|
| 0. Discovery | JTBD Interviews | A validated "Job Statement" |
| 1. Mining | Noun Foraging | Candidate Object list |
| 2. Logic | Relationship Mapping | Technical System Architecture |
| 3. Action | CTA Matrix | System capability map |
| 4. Specs | Attribute Force Ranking | The Data Contract (API Spec) |
Do not open Figma until the Object Glossary is signed off. UX designs for the data that exists; Devs build for the user that struggles.
Run these four collaborative sessions to bridge the alignment gap.
Identify why the user is "hiring" the product and extract every noun to find objects.
Draw lines between objects. Devs define if relationships are 1:1 or 1:Many.
Define what actions (CTAs) can be performed on each object and who has permission.
List and rank attributes. Finalize exactly what data fields the API needs to return.
Object, Relationship, Call-to-Action, Attribute.
Traditional UX often focuses on "task flows"—how a user moves from A to B. But complex systems fail when the "things" (Objects) at those steps aren't well defined. ORCA ensures the system skeleton is solid first.
Upgrade the user, not the product.
Users don't buy products; they hire them to make progress. To get someone to use your new system, they have to "fire" their old habit. Understanding the "Push" of the current struggle is essential for the Roadmap.