Log in or create a free Rosenverse account to watch this video.
Log in Create free account100s of community videos are available to free members. Conference talks are generally available to Gold members.
Summary
Design teams are often faced with lack of research resources that can lead to bottlenecks in execution, an ever growing backlog of research questions or worse releasing products without sufficient research. This can lead to rework and expensive development costs. A rapid research program is a tactical, flexible framework that helps teams build better products by executing on more research faster. This model requires aligning resources to operationalize the process and reduce the overhead and time of standard research processes like recruiting.
Key Insights
-
•
Rapid research is primarily useful for quick, tactical, or evaluative UX design questions that require fast feedback to unblock product decisions.
-
•
Rapid research programs benefit from clear processes, recurring and predictable cadences, and defined roles like moderators, recruiters, and note takers.
-
•
Rapid research is not suited for large, exploratory foundational research questions or scenarios where answers generate more questions without time to iterate.
-
•
Stakeholder support—especially from product teams and designers—is critical for the success and integration of rapid research into product workflows.
-
•
Three common rapid research models are: short and focused (single topic, single moderator), multi moderator (multiple moderators per topic), and multi topic (one moderator covering multiple topics).
-
•
The multi-topic model with one moderator handling several topics per session is effective for scaling across multiple teams and maintaining tight coordination.
-
•
Research operations support, especially in recruiting participants, is essential to running rapid research efficiently at scale.
-
•
Rapid research programs can connect dots across teams by sharing findings, reducing redundant work, and contributing insights to foundational research.
-
•
Documentation and socializing research findings in accessible formats and channels are crucial, especially in fully remote setups.
-
•
Rapid research is a complement—not a replacement—for other UX research methods, enhancing agility but still relying on other types of deeper research.
Notable Quotes
"Rapid research is a flexible framework for quickly executing UX research for fast and often tactical or evaluative design decisions."
"You wanna do rapid research when the feedback or the findings is gonna be focused and impactful."
"Rapid research is really great if you wanna promote research within your organization, but it’s not supposed to be the only thing you do."
"Stakeholder support is pretty important because if people on your team just don’t have time, they’re not gonna be able to commit to their roles."
"Having a predictable cadence makes it way more useful for teams to contribute and benefit from rapid research."
"The advantage of having one moderator is I work with all the teams pretty much and can connect the dots across products."
"Rapid research programs enable designers to submit research questions and feel empowered to participate actively in the research process."
"If rapid research findings create more questions but you don’t have time to address them, it’s probably not the right method."
"We ended up doing an average of five labs per quarter covering 12 to 15 research questions, which helped avoid design delays."
"Rapid research is going quickly; you get a lot of information fast, but the analysis isn’t as deep as other methods."
Or choose a question:
More Videos
"Low vision users often invert colors and use magnification levels as high as 400 percent to reduce eye strain."
Sam ProulxSUS: A System Unusable for Twenty Percent of the Population
December 9, 2021
"There are lots of little mushroom patches of design sprouting up, but they're disconnected and not sharing."
Michael LandEstablishing Design Operations in Government
February 18, 2021
"Our one metric that mattered was maximizing the number of VOС-tagged tickets solved – showing customer feedback made it to the roadmap."
Shipra KayanHow we Built a VoC (Voice of the Customer) Practice at Upwork from the Ground Up
September 30, 2021
"Communication matters—sending an email to an executive with spelling mistakes can ruin your respect."
Ian SwinsonDesigning and Driving UX Careers
June 8, 2016
"The trusted partnership between the chief of staff and the executive is critically important."
Isaac HeyveldExpand DesignOps Leadership as a Chief of Staff
September 8, 2022
"Change is messy and it can be uncomfortable, much like baking bread—it’s hard to imagine sticky dough turning into a perfect loaf."
Amy EvansHow to Create Change
September 25, 2024
"Super strength is the resilience and endurance to partner and drive strategic impact backed by customer obsession."
Kate Koch Prateek KalliFlex Your Super Powers: When a Design Ops Team Scales to Power CX
September 30, 2021
"It’s impossible to be angry with a warm cup of tea in your hand."
Dave GrayLiminal Thinking: Sense-making for systems in large organizations
May 14, 2015
"The challenge is whether your organization has the energy to overcome cultural and technical barriers driving researchers back to disposable knowledge."
Matt DuignanAtomizing Research: Trend or Trap
March 30, 2020
