This is part one of a three-part template/guides resource for documenting UX research repository work.
How to use this template
This template helps UX research teams who want to socialize their UX research repositories. An ‘All About’ space is useful for increasing research visibility, identifying research debt and bringing more value to ongoing research projects. This space provides an overview of individual research projects. I created this template to make my UX archiving work in Dovetail easier, hopefully it will help you, too.
I’ve implemented and tailored this template to the needs and goals my last several teams as a Research Ops and repository specialist. In doing so, I’ve found that it has some great benefits: 1) This transforms your repository from an archive into a learning space. 2) Links to relevant research findings and artifacts makes the ‘story’ of a research project easier to follow 3) By taking time to create an all about space, a researcher will refine and broaden their understanding of each research project. 4) A template like this saves time. Researchers are busy individuals, this can serve as a starting place for building research reports. It also gives a repository polish and makes it easier to present.
Intended users: Any research repository end user (i.e new and existing researchers, onboarding, product development, business development, stakeholders, leadership etc.) who reads this page will understand the project and why and how it is relevant to products and their organization as a whole.
Tips: Pairing all about and use case information will likely inform researching funding decisions. Add and embed links to your research repository archive, Use Case and raw data links throughout this space.
What is ___?
Introduce the research project in 1-2 sentences. What is the project and why is it important?
Use this space to aid project onboarding and instructional documentation: uploaded client videos and product explanation documentation, project roadmap, etc.
Not to be confused with personas, add initial key information about end users not yet narrowed down to archetypes. For example, who is using the product you’re working on? Here are some examples of information to record:
ex. “The following user data has been drawn from the 2019 annual customer satisfaction survey results out of 400 responses collected via SurveyMonkey” (include links to raw survey, survey results and/or presentations)
Add a brief explanation of the current stage of research and links to the research project archive and relevant artifacts. ex. “We have just completed survey interviews and are moving on to...”
1. Research Project Stage (YYYY)
2. Research Project Stage (YYYY)
3. Research Project Stage (YYYY)
4. Research Project Stage (YYYY)
- Research Stage
This section can provide a lot of value and strengthen cross-functional repository socialization and work visibility. Consider adding the following artifacts. Do not use this space as a design work archive (it’d be better to add links to current design work, if anything). This is merely a glimpse of the design teams contributions during the building stage—very helpful for new team members requiring access.
Here are some examples of what you can include:
- Software/platform/language used (i.e. Material)
- Current sprint design software links
- Design system/UI kit Link
- Landscape research and design rules
Add as many links as possible here, this will help repository end users understand the big picture impact of this particular research study.
Examples of internal reference information: All background information. Program overview, research project use case, related research projects and studies, early inspiration and landscape research, meetings, related software and projects, frameworks, company site, case study, Drive folder, etc.
Examples of external reference Information: Product, client and company/organization links, articles, videos, blog posts, etc. that will be especially helpful to newly onboarded team members starting to learn about this research project.