11-Part UX Research Process Library 📚

What's a Research Process Library (RPL)?

In the creation of our UX Research Process Library, we've taken a chapter out of the field of UX Design. We've drawn extensive inspiration from the idea of developing and maintaining UX Design Pattern Libraries to turbocharge product design.

Just as a Design Pattern Library standardizes and codifies repeatable visual patterns, a Research Process Library standardizes and codifies repeatable research processes.

First, we'll explain what is a Design Pattern Library (DPL). A DPL is repository of user interface (UI) designs that are regularly used by designers to quickly / effectively / consistently create UI/UX solutions for digital products. Within the library exists re-usable, standardized UI design components and elements. The idea is to create a system of design patterns that function well together, improve speed, maintain consistency, and utilize common best-practices for the company and industry.

Similar to a DPL, we've developed a Research Process Library (RPL). Instead of repeatable visual patterns, we've built out a system of repeatable research processes. We've also broken down each process into underlying components and elements to uphold specificity and detail at all levels. Components 🧱 are defined as the multiple parts that make up a process. And elements are the pieces of a component, when broken down further.

Research Library ➡ Processes (e.g. Insight Theme) ➡ Components (e.g. User Story) ➡ Elements (e.g. user need)

You'll see this language used systematically throughout our articles. For example, within our RPL is a core process that is the Insight Theme. Of which there are 7 Components of an Insight Theme. The User Story is one such component. Each component is made up of several elements, such as the 4 Elements of a User Story.

Why a UXR Process Library is important

Having a Research Process Library (RPL) is important to UXR professionals, and the companies for which they work, for 3 reasons:

(1) Save time and energy for individual UXRrs, (2) Reduce cognitive load on stakeholders, (3) Increase scalability as a UXR team.

First, RPLs allow UX researchers to simply pull from the shelf of available research processes. Spend your time and mental energy focused on what matters most — identifying insights, themes, and recommendations. There's no need to reinvent of the wheel of how the work is done. Just focus on the doing. And be systematic ⚙️ about it.

Second, RPLs create predictable project deliverables with which stakeholders are familiar. The purpose is not to confuse stakeholders with new approaches, styles, or deliverables — similar to how a DPL is meant to keep designs straightforward for users. Keep it consistent. Make it repetitive. Save cognitive 🧠 load of others.

Third, RPLs help you move faster as a UXR team. The process is scalable when you replicate it over and over. Better yet, the whole UXR team can leverage it to create operational efficiencies. Normalization of inputs and outputs helps to make team members interoperable 🔄. It also also helps UXR teams to focus on the bigger picture of UX opportunities earlier, and more often.

1. Project Brief 💼

10 components of a useful UXR Project Brief.

• See 10 Components of a Useful UXR Project Brief 💼 to learn how to compose a UX research Project Brief that outlines all the major aspects of the UXR opportunity.
• A UX research Project Brief is a 1–2 page word document that outlines the relevant details to the UXR work-to-be-done — enhancing clarity and accountability.
• The 10 components of a UXR Project Brief: (1) Project name, (2) Stakeholders, (3) Business context, (4) Product metrics, (5) Research goal, (6) Research objectives, (7) Target participants, (8) Key questions to answer, (9) Activities to generate insight, (10) Timeline, (Bonus) Archive of deliverables.
• UXR Project Briefs are the best place to start when details and direction is ambiguous, since it's valuable to write down all the foundational bits.
• Project Briefs are a simple way to keep on track during the throws of a project, because they contain all the basics, easily referenceable, while enabling focus on forward progress.
• Project Briefs are useful tools for cataloguing past projects, with associated details and deliverables, for anyone looking to reference what a project was all about.

Return to overview ⤴

2. Research Protocol 🥼

Components of a Research Protocol

• See 3 Unique Components of a Research Protocol 🥼 to learn how to write a Research Protocol within the boundaries of the business that clearly details the research tasks.
• If raw user data is the gasoline that fuels the fire of the sense-making, the Research Protocol is drill, pump, and refinery all-in-one.
• Research Protocols are tactical, practical field guides for how to navigate conducting of user research. They specify with whom you'll research, how, which questions to address, and in what order.
• The 3 unique components of a Research Protocol: (0) Research goal & objectives, (1) Participant screening criteria (2), User scenario, (3) User tasks.
• Research Protocols are important to the UXR process because they provide an easy reference — for all stakeholders — to maintain focus and clarity before, during, and after user research studies.
• The form factor is usually a simple Word doc or Google doc containing sentences, paragraphs, and bullet-points, without much in the way of visuals.

Return to overview ⤴

3. Research Tasks ✏️

6-step guide for typical Research Tasks outline.

• See the 6-Step Guide to Drafting UX Research Tasks ✏️ to learn how to write Research Tasks for user interviews / observations, along with 7 tips for writing them in detail.
• Research Tasks exist within the UX Research Protocol, following the documentation of stakeholders, goal, objectives, timeline, screening criteria, and scenario.
• Research Tasks are defined as the specific phrasing for how the UX researcher elicits user feedback.
• Research Tasks are oriented directly at conducting the research. They're the detailed questions to be asked in the live research situation.
• The 6 steps of user Research Tasks: (1) High-level overview, (2) Context-setting, (3) Prototype high-level, (4) Focused deep-dive, (5) Reflections, (6) Summarization.
• Being more structured leads to: (1) better stakeholder collaboration upfront, (2) an even balance of research topics throughout, and (3) improved end-user participation and outcomes.
• Take your time in writing clear, succinct, and thoughtful 🤔 interview questions so that anyone internally or externally can easily follow along, on their own.

Return to overview ⤴

4. Data Analysis 🔎

Framework for making sense of user data using a User Journey Map.

• See 12 Frameworks to Assist in Data Analysis 🔎 to learn how to analyze UX research data for insights from user un/moderated interviews, observations, dog-fooding, and more.
• Data Analysis is the process of breaking down data — format it so it's easy to see, parse, pinpoint, and pull out bits that one finds most important.
• Frameworks provide a structured approach to let you see all the data on the same plane of sight in order to more easily pick out the insights.
• An insight is a new piece of information that gives us a better understanding of the user, while providing an opportunity to do something about it — insights come from several users saying, behaving, or implying the same thing.
• Watch for substantiated evidence of users' shared sentiment / actions about: pain points, confusion, opportunities to improve, positives, specific recommendations and ideas.
• Whatever gives us a better sense for where, what, when, why, and how to reduce pain points and multiply points of positivity in the broader UX is considered a valuable insight.
• Keep an open mind throughout the analysis process — stay unbiased, and let the data speak for itself. Give the data room to breathe, settle, and naturally filter itself.
• User quotes are an effective way to normalize data, without imposing your 2-cents — quotes retain the core meaning of a user's perspective, with subsequent insights / ideas.
• Spend the time to transcribe, and stay entrenched in the user quotes / facts / stats to more easily surface topics that resonate, repeat, and reside among users.

Return to overview ⤴

5. User Stories 💕

Framework for writing User Stories in UX Research.

• See 4 Elements of an Effective User Story 💕 to learn how to write User Stories that capture and communicate user needs to effectively inform product design.
• 4 elements of User Stories are: (1) Written from the users' perspective, (2) Describe what the user needs or desires, (3) Supported with reasoning why, (4) Succinct and consistent.
• User Stories don't have to explicitly state the answer or solution, but rather provide context as to what is needed, by whom, and why.
• The format of a User Story: "As a user [X], I need / want [Y], so that / because [Z]".
• User Stories are best accompanied by several other supporting elements: title, video, verbatim, quote, and recommendations.
• A typical UXR project will output 4–8 User Stories as one part of the final deliverable.
• User Stories allow partner stakeholders to know exactly what to expect from your UX research projects.
• Consistent User Story documentation allows for long-term identification of opportunities beyond immediate products.

Return to overview ⤴

6. Insight Themes 🤯

7 components of an Insight Theme. Last 2 components not shown.

• See 7 Components of Compelling Insight Themes 🤯 to learn how to create Insight Themes that clearly communicate UX opportunities while saving time and energy.
• An insight is a new piece of information that gives us a better understanding of the user, while providing an opportunity for the business to do something about it.
• An Insight Theme is a group of insights that share some common element — the result of many insights coming together qualitatively, quantitatively, and auto-magically.
• The 7 components of Insight Themes: (1) Title, (2) User Story, (3) User quote, (4) Video highlight, (5) Direction, (6) Personality, (7) Storytelling.
• UX Researchers need a sound understanding for the business, data, experience, and curiosity to create compelling Insight Themes.
• Through sorting, arranging, re-arranging, and theming, a UX researcher will have enough content for 3–7 Insight Themes.
• 3 reasons to keep Insight Themes simple: (1) it allows the UX researcher to move faster (2) it allows others to know what to expect (3) it helps you scale over time, people, and projects.

Return to overview ⤴

7. User Insight Storytelling 🤟

Framework to adhere throughout User Insight Storytelling.

• See 3 Points to User Insight Storytelling Success 🤟 to learn how to to succeed in User Insight Storytelling as measured by stakeholder comprehension and willingness to act.
• Use the open-face sandwich feedback method for User Insight Storytelling: (1) Positive appreciation → (2) Opportunities to improve → (3) Recommendations for how to solve.
• Summarize all UX opportunities and prioritize all UX recommendations onto 1-slide each as presentation book-ends to aid in digestion of information by stakeholders.

Return to overview ⤴

8. Recommendation Prioritization 🤓

Process of fleshing out, ranking, plotting, and prioritizing recommendations.

• See 5 Methods of Prioritizing Recommendations 🤓 to learn how to prioritize recommendations from UX research so they're ranked by most important variables.
• The process of UX Recommendation Prioritization preemptively answers the question, 'Now, what?' for product stakeholders.
• A structured approach is the best way to generate UX recommendations for a product — insight theme creation (What?) → actionable recommendations (So, what?) → prioritized recommendations (Now, what?).
• The 5 methods of recommendation prioritization are: (1) Impact x Ease matrix, (2) Forced Rank analysis, (3) Haves and Have-nots, (4) Experience Touchpoint plotting, (5) Strategic vs. Tactical comparative table, (Bonus) If you only do 1-thing...
• UX recommendations are important to prioritize because doing so showcases leadership and authority.
• If nothing else, having a prioritized list of recommendations will prompt a meaningful discussion about what everyone believes is the most important, if not what you suggest.
• The first step is to normalize the actionable UX recommendations — further clean them up, give each a title, clearly write out the details, and notate for which User Story it solves.

Return to overview ⤴

9. Improvement Action Plan 🎬

The 4 components of an Improvement Action Plan

• See 4 Components of an Improvement Action Plan 🎬 to learn how to make a UX Improvement Action Plan from research to make positive changes happen.
• An Improvement Action Plan is a tool that breaks down the prioritized UX recommendations (tasks) into specific, measurable actions (to-do's) to be tackled by the organization.
• The process creates a cross-functional to-do list to make sure UX recommendations are seen through to completion.
• Improvement Actions (to-do's) double click on UX recommendations, which originate from Insight Themes, originally derived from user insights.
• The 4 components of an Improvement Action Plan: (1) Action items, (2) Lead, (3) Progress, (4) Recommendation.
• Be specific when creating the to-do's to make sure the work gets done. Be measurable to quantify progress, and track impact for the organization.

Return to overview ⤴

10. Insight Database 💡

Diagram of an UXR Insight Database, along with inputs and outputs.

• See 4 Ways an Insight Database Creates Value 💡 to learn how to create a UXR Insight Database that elevates your UX research practice.
• An Insight Database is a place where you store user Insight Themes in order to make them searchable and organizable for later use.
• 4 ways an Insight Databases creates value: (1) Force you to think more holistically, (2) Allow you to identify unmet user needs, (3) Help you earn a seat at the decision-making table, (4) Give partner teams a better glimpse into the full user experience.
• Insight Databases represent an elevation of the UX research practice to a strategic level.
• Make an Insight Database with a Google Sheet spreadsheet to easily share and edit by many.
• Don't spend more than 5–7% of your time maintaining your Insight Database and related artifacts.

Return to overview ⤴

11. Design Principles 💎

3x So, what?: Raw data ➡ Insights ➡ Insight Themes ➡ Design Principles

• See 3 So-what's to Develop Design Principles 💎 to learn how to craft powerful Design Principles that maximize strategic impacts from UX research.
• Design Principles provide strategic guidance for significant — and systematic — improvements to be made to the user experience.
• Design Principles help internal departments to align efforts, and to move in a coordinated fashion towards an envisioned UX.
• The 6 components of Design Principles: title, visual, statement, reel, context, and direction.
• The process of creating Design Principles includes 3 major steps: raw data ➡ insights ➡ Insight Themes ➡ Design Principles. Each step is considered a So, what? transition.
• Design Principles are the key deliverable of the Influence phase. After completing 10+ projects you'll have the Insight Themes available to yield value-add Design Principles.

Return to overview ⤴

(Bonus) UXR Project Guide 📌

5-phase User Experience Research Project Guide

• See 5-Phase UX Research Project Guide (+Bonus) 📌 to learn how to run UX research projects that improve insight delivery and operate at the speed of business.
• UX research is the study of a product's user experience to identify/test new opportunities, so that the business can improve key metrics associated with a positive UX.
• The 5-phases of a UXR Project: (1) Plan, (2) Execute, (3) Analyze, (4) Synthesize, (5) Implement, (Bonus) Influence.
• The reason to use a standardized project guide in UXR is so that both you and your stakeholders have certainty about what to expect, and when.
• The 5-phase UXR Project Guide (+bonus) is the turbocharger that increases design and development horsepower for the engine of the business (Product)

Return to overview ⤴

Templates to assist in practical RPL application

UX research template toolbox for guided approach to projects.

If you like what you see here, and you'd like a kickstart to your own UXR project, then check out 6 Templates — with Examples — for UXR Projects. In this article, you'll find downloadable template files that will get you up and running at once.

Decide which UXR phase you're in, pick a template, and operate at speed!

Back to top ⤴