UX Research Lab is a portfolio repository of realistic UX research artifacts for frontend products, accessibility tools, nonprofit websites, developer education, and developer experience. It is designed to show how research strategy can connect product decisions, interface design, accessibility, and engineering execution.
This repository is intentionally Markdown-only. It focuses on the thinking, methods, evidence structure, and decision frameworks behind research-led product work rather than a polished frontend demo.
Modern UX Design Engineers are often asked to translate between user needs, product strategy, implementation constraints, and accessibility requirements. This repo demonstrates that bridge through practical research documents: research plans, interview guides, surveys, affinity maps, usability testing materials, A/B test plans, personas, journey maps, case studies, and reusable templates.
All sample studies are labeled as Portfolio Simulation where appropriate. They are written as credible examples of how research could be planned, documented, analyzed, and converted into product recommendations without claiming that live participants were recruited or interviewed.
- Recruiters evaluating UX research and product thinking in a design engineering portfolio
- Hiring managers looking for evidence of structured problem solving
- Product teams interested in how frontend implementation choices affect user experience
- Accessibility teams reviewing research literacy around inclusive design
- Developers exploring research methods for developer experience improvements
- Generative research planning
- Semi-structured interviews
- Task-based usability testing
- Survey design and analysis planning
- Affinity mapping and qualitative synthesis
- A/B test planning and decision rules
- Persona development
- Journey mapping
- Accessibility-focused research
- Developer experience research
- Portfolio case study writing
UX research is most useful when it changes what gets designed, built, measured, or removed. These artifacts show how research can inform:
- UX design through clearer user goals, decision criteria, and interaction risks
- Frontend engineering through usability, state clarity, navigation, error handling, and performance considerations
- Accessibility through assistive technology needs, content clarity, keyboard support, cognitive load, and WCAG-informed evaluation
- Developer experience through documentation quality, onboarding friction, command-line confidence, and tool adoption barriers
Start with the case studies for the clearest portfolio narrative, then review the research plans and testing artifacts to see how the work is structured. The templates show repeatable process, while personas and journey maps demonstrate synthesis and product thinking.
Recommended review path:
- Read the case studies in
case-studies/. - Compare the related plans in
research-plans/. - Review
usability-testing/findings-report.mdandusability-testing/severity-matrix.md. - Scan one interview guide, one survey, and one affinity map.
- Review the templates as evidence of repeatable research process.
| Folder | Purpose |
|---|---|
| research-plans | Research strategies for frontend, CLI learning, accessibility, and nonprofit website projects |
| interview-guides | Semi-structured interview guides for designers, developers, admins, and accessibility users |
| surveys | Survey instruments for usability, accessibility training, nonprofit feedback, and developer learning |
| affinity-mapping | Simulated qualitative synthesis maps with themes, pain points, needs, and recommendations |
| usability-testing | Test plan, script, scenarios, findings, and severity matrix for a frontend learning platform |
| ab-testing | Experiment plans for donation flow, signup CTA, onboarding copy, and result analysis |
| personas | Research-informed personas for core product audiences |
| journey-maps | Journey maps for learning, auditing, donating, and command-line onboarding |
| case-studies | Portfolio case studies connecting research insights to product recommendations |
| templates | Reusable Markdown templates for future research work |
- Be clear about what is simulated.
- Use research language that is practical, not inflated.
- Connect findings to product decisions.
- Treat accessibility as a core research responsibility.
- Make artifacts easy to review quickly without losing rigor.
This project is available under the MIT License. See LICENSE.