7 Things You Need to Know to Sell UX Research with Object-Oriented Thinking

You know the scenario: you're designing screens with only a vague sense of how they connect to the broader system. Stakeholder meetings leave you with contradictory directives, and you're convinced that direct user contact would clear things up. But time and budget are tight, and asking for research feels like Oliver Twist begging for more. The secret? Get stakeholders to identify their own high-risk assumptions and hidden complexity. When they realize how much they don't know, they'll become your biggest advocates for research. The ORCA method—focusing on two simple questions about objects and their relationships—turns this into a collaborative discovery process. Here are seven things you need to know to make it work.

1. Recognize the Pain of Guesswork

Most design teams operate with a silent acceptance of ambiguity. They build features based on assumptions that are never validated, leading to rework and missed deadlines. The first step to selling research is making this pain tangible. In a workshop, ask your team to recall a project where unclear requirements caused major delays. List those experiences on a whiteboard. The emotional weight of wasted effort becomes a powerful motivator. When stakeholders see the cost of guesswork—in hours, budget, and morale—they become open to alternatives. This shared acknowledgment creates fertile ground for introducing a structured approach like ORCA, which promises to reduce uncertainty from the start. The key is to frame research not as an added expense, but as an investment that eliminates expensive guesswork later.

2. Introduce the Two Simple Questions

Instead of pitching research directly, present two deceptively simple questions: “What are the objects?” and “What are the relationships between those objects?” These questions align with the first two steps of the ORCA process (Objects and Relationships). They are non-threatening and invite open-ended discussion. Gather your stakeholders around a whiteboard or Miro board. Explain that object-oriented thinking helps surface the core entities users interact with—like “orders,” “customers,” or “invoices”—and how they connect. By answering these questions together, you collaboratively expose gaps in shared understanding. The beauty is that stakeholders naturally start to realize what they don't know about user mental models. This awareness is the hook: they now understand that a little direct user input could fill those gaps, making the team's design decisions more robust.

3. Expose Hidden Complexity with Objects

Once you start listing objects, complexity emerges quickly. For example, in a healthcare app, “patient” might seem straightforward, but stakeholders may disagree on whether “medical record” is an object or an attribute. This debate reveals real-world nuance that users navigate daily. By mapping out all objects—using color-coded sticky notes (blue for objects, as per OOUX conventions)—you create a visual inventory that exposes multiplicity and overlap. Stakeholders often discover that they have been using different terms to refer to the same object, or worse, the same term for different things. This misalignment is a goldmine for selling research: you can point out that only user observation can resolve which mental model works best. The exercise shifts the conversation from “we need more budget” to “we need clarity to avoid future rework.”

4. Uncover Relationships That Stakeholders Overlook

After defining objects, move to relationships. Ask: “How do these objects relate? Can one exist without the other?” Stakeholders often default to simple hierarchies—like “customer has orders”—but users frequently think in complex networks. For instance, in a learning management system, does a “course” belong to a “program” or is it independent? These questions reveal hidden dependencies and constraints. By drawing relationship lines (with arrows indicating cardinality), the team sees where their assumptions diverge. One product manager may assume a one-to-one relationship while a developer sees many-to-many. This tension is productive: it proves that without user research, the design will likely miss critical use cases. Encourage stakeholders to note where they disagree and tag those spots as “research needed.” This turns research into a natural problem-solving tool rather than a bureaucratic hurdle.

5. Use the ORCA Gauntlet to Bridge Research and Design

The ORCA process—Objects, Relationships, CTAs (Call to Actions), Attributes—provides a structured path from research to a testable prototype. In the full methodology, you iterate through four rounds, each adding more detail. However, even just the first two steps serve as a “gauntlet” between research and design. If you have good research data, the ORCA map lets you distill insights directly into solid information architecture. If you have no research, the process highlights exactly where you need user input. Show stakeholders this spectrum: with research, the gauntlet guides you smoothly; without it, the process spits out vague, risky designs. This visual metaphor resonates because it frames research as a safeguard, not a luxury. By demonstrating how ORCA connects user needs to screen layout, you build a compelling case for investing in that foundational research phase.

6. Make Stakeholders Feel It's Their Idea

The most persuasive way to sell research is to let stakeholders sell it to themselves. During the object and relationship mapping, don't dictate answers; facilitate discovery. Ask questions like: “How would a user describe this relationship?” or “Where might we be over-simplifying?” As they grapple with contradictions, they'll naturally propose talking to users. Reinforce this by saying, “Interesting—user research could help us settle that, right?” When the suggestion comes from the team, it's no longer your uphill battle. They own the need. You can amplify this by documenting their questions as “research hypotheses” to test. Later, when presenting a research plan, reference those specific questions. The stakeholder who first voiced the uncertainty becomes your internal champion. This collaborative approach turns research from a cost center into a shared mission.

7. Build Momentum for a Research Phase

After one workshop, the team will have a list of unresolved assumptions—the perfect seed for a research proposal. Use this momentum to draft a lightweight research plan. Highlight the specific questions that emerged (e.g., “Do users perceive an ‘order’ as separate from a ‘shipment’?”) and the cost of not answering them. Attach rough estimates: “If we guess wrong, we'll need 10 developer hours to fix it later.” Compare that to the cost of a 2-hour user interview session. Suddenly, the ROI is obvious. Share the object map as a living artifact, and invite stakeholders to keep adding questions. This ongoing visibility ensures that research stays top-of-mind. Over time, your team will shift from reactive design to proactive discovery, all because two simple questions sparked a cultural change.

Conclusion: Selling UX research isn't about demanding more time or budget—it's about creating a collective realization that ambiguity is expensive. By guiding stakeholders through the ORCA questions of objects and relationships, you transform abstract concepts into concrete gaps that only users can fill. The numbered items above provide a step-by-step roadmap: first acknowledge the pain, then introduce the questions, expose complexity, uncover relationships, leverage the gauntlet, let stakeholders own the idea, and finally build momentum for a dedicated research phase. When you make research feel like a necessary next step rather than an extra ask, you'll find stakeholders not just approving your proposals, but championing them. The ORCA framework doesn't just structure your design—it structures your pitch, turning you from Oliver Twist into a strategic partner.