Why Research Is Key to Design Success
Navigating the maze of screen design can leave one feeling lost, especially when clarity surrounding user needs is shrouded in ambiguity. Have you left planning meetings with a sense of unease, grappling with directives that seem to conflict with past conversations? Many designers are in the same boat, yearning for a clearer picture of the user and the overall system. However, the constraints of time and budget often restrict the ability to obtain that critical user insight. The hesitance to directly seek user engagement can often feel like Oliver Twist timidly asking for more—a struggle against the pushback of limited resources.
The solution isn’t just to ask for more research; it’s about drawing stakeholders into the conversation, prompting them to identify the assumptions and complexities that pose the greatest risks. When stakeholders recognize that they hold a stake in understanding user needs, their motivation can shift dramatically. Instead of merely pointing fingers at the problem, they can engage in a dialogue framing it as their own discovery, transforming the dynamic of the process.
In this article, I’ll demonstrate how you can spotlight these misalignments by guiding your team through two essential questions:
- What are the objects?
- What are the relationships between those objects?
Bridging Research and Design with ORCA
These pivotal questions align directly with the initial steps of the ORCA methodology, which could redefine how you approach the convergence of user research and design. So, what exactly is ORCA? It stands for Objects, Relationships, CTAs (calls to action), and Attributes—a framework poised to enhance your design process by establishing a solid foundation rooted in user research.
ORCA is an iterative approach comprising four rounds and an extensive fifteen steps, enhancing clarity around various components. It arms you with the tools needed to synthesize research findings into a structured design that fosters coherent user interactions. I often refer to ORCA as a “garbage in, garbage out” method. The prototype’s efficacy hinges on the quality of input it receives; without adequate research, the entire operation risks devolving into guesswork. Notably, the onset of the ORCA methodology can also play a vital role in advocating for the necessity of robust user research.
Essentially, ORCA serves as both a compass and a crucible, guiding effective transitions from research insights to the design stage. With strong data, you can ride the wave from insight to implementation. Yet, without that critical research, the process might redirect you back to square one with a list of pointed inquiries still unanswered.
Fostering a Culture of Inquiry
As Mark Twain aptly put it, “What gets us into trouble is not what we don’t know. It’s what we know for sure that just ain’t so.” The early steps of the ORCA process, particularly Object Discovery and Relationship Discovery, reveal the misalignments that often fester beneath the surface of project assumptions. Many designers encounter frustration rooted in miscommunication, often stemming from team confidence in their mental models.
The key to change lies in collaboration. Instead of confronting your team with accusations of error, guide them to recognize the ambiguities in their understanding autonomously. When stakeholders own their misconceptions and acknowledge gaps, you’ll find that advocating for user research becomes infinitely easier, and the team can align their insights.
Think about a scenario where the users are healthcare professionals, and you’re tasked with redesigning a clinical interface. Your conversations about user needs might sound vague and unconvincing: “We need to understand how doctors use this app better.” But that doesn’t provoke action.
Instead, aim for specificity by facilitating stakeholder dialogue that produces targeted inquiries. Picture this exchange:
“What’s the frequency of patient sharing among doctors?”
“Can one patient have multiple primary care providers?”
“Are caregivers treated as part of the patient’s care team?”
When stakeholders voice these detailed questions, the sense of urgency to explore answers shifts the perception of screen design. Building systems without comprehending the real-world dynamics of users feels reckless and ill-advised.
Establishing a concrete grasp of these relationships and objects isn’t merely beneficial; it’s essential to avoid creating cumbersome, counterintuitive designs. Without understanding the user landscape, your designs may stray from what users truly need, leading to a frustrating experience.
The Cornerstone Questions
So, how do we foster this rich inquiry efficiently and effectively? It starts with two foundational questions tied to the ORCA process:
- What are the objects?
- What are the relationships between those objects?
Securing answers to these questions enriches your Object Definition Workshop, where basic queries evolve into nuanced discussions, illuminating the necessity for deeper user research.
As we move forward, I’ll guide you on executing this workshop with your team while also emphasizing the importance of preparation—specifically through what I like to refer to as "noun foraging."
Sealing the Deal on User Research
Bringing synergy to your team isn’t just a nicety; it’s a necessity. When you dig into defining objects and their relationships, you pave the way for clearer communication across all stakeholders. Positioning everyone on the same page before diving into screen design can save you countless hours of confusion and rework later. It’s about making the invisible visible.
You're not just compiling a laundry list of questions at this point; you’re igniting a fire that will justify the need for user research. Ask the group to reflect on the uncertainties identified during the workshop. Don’t shy away from prioritizing these questions based on their risk level. The logic here is straightforward: if you design without addressing a critical question, you might face significant repercussions later on.
Consider framing your closing argument around these uncertainties. “What happens if we proceed without answers?” This isn’t just a rhetorical question—it's an opening to highlight the stakes involved in neglecting user input. By labeling certain questions as high-risk, you're positioning decision-makers to champion user research, compelled by their own assessments of potential fallout.
Now comes the pivotal moment: ask for a budget to conduct user interviews. Present the need for 6-8 conversations focused on those critical, unresolved questions. It’s your chance to underline the importance of preemptive insights from real users.
And here’s a pro tip—if you're new to this arena, adjust the language of your questions for users. Open-ended inquiries will yield better insights, while leading questions risk skewing their responses.
Don’t Skip the Object Definitions
If you walk away with one piece of advice, make it this: don't let screen design happen without first articulating the objects and their relationships. This isn’t just a checkbox on your project plan; it's foundational. If you've secured a united understanding of these elements before sleeving up your design, you stand to gain in efficiency and clarity.
Not only will this alignment save you from painful iterations down the line, but it will also engender smoother user interactions with your product. When users see an experience that resonates with their expectations, they’re more likely to embrace it.
I genuinely hope these methods help you gain the time and resources necessary to connect with your users before you begin designing interfaces. Engaging in noun foraging and the Object Definition Workshop are only the beginning. These strategies form part of a larger toolkit—the ORCA process—that can sidestep late-game scrambles over scope and strategy.
Good luck! Now go out there and sell the value of research—your users are counting on it.
