A collection of UX research work focused on accessible products, developer tools, learning experiences, and nonprofit websites.
I'm DeAndre Perry. My background sits between UX research, product thinking, accessibility, and frontend development. I enjoy taking a broad product question, figuring out what the team actually needs to learn, and turning that research into clear next steps.
I built this repository to document how I approach that work. It includes research plans, interview guides, surveys, usability studies, synthesis tools, and experiment plans. You can find more of my work on GitHub.
| Project | Main Question | Current Status |
|---|---|---|
| Frontend Index | What helps designers and developers choose the right UI pattern with confidence? | Study ready; research has not started |
| 508dev | How can teams move from finding an accessibility issue to fixing it well? | Research proposal |
| CLI Academy | How can beginners learn the command line without feeling stuck when something goes wrong? | Research proposal |
| Nonprofit Website | What helps visitors trust and use a nonprofit website without making the site harder for staff to maintain? | Research proposal |
Frontend Index is the most complete project in the repository. It includes the research strategy, recruitment screener, competitive review, prototype plan, synthesis structure, and decision log.
Most of these projects are simulations. They show how I would plan and carry out the research, but they do not claim that interviews or usability sessions already happened.
I label assumptions as assumptions and keep example findings separate from real evidence. When I add completed research in the future, I will only share participant material that is de-identified and approved for public use. Recordings, contact details, and private client information do not belong in this repository.
| Folder | Contents |
|---|---|
| projects | Complete project stories and links to supporting work |
| case-studies | Short summaries of each project |
| research-plans | Research questions, methods, sampling, analysis, and delivery plans |
| interview-guides | Semi-structured guides for designers, developers, nonprofit staff, and disabled participants |
| surveys | Survey drafts with response options and analysis notes |
| affinity-mapping | Early hypothesis maps that are ready to be tested against evidence |
| usability-testing | A test plan, moderation guide, tasks, reporting example, and severity model |
| ab-testing | Experiment plans and a results template |
| personas | Provisional behavioral archetypes, not fictional research findings |
| journey-maps | Early journey maps with clear validation plans |
| templates | Reusable research templates |
| research-operations | Consent, data handling, evidence storage, and impact tracking |
A project starts with a decision the team needs to make. The plan explains what we need to learn and why a method fits. The research tools collect the evidence. Synthesis turns that evidence into findings, and the decision log shows what changed afterward.
I use a few simple labels throughout the repository:
- Evidence: something observed or measured
- Interpretation: what I think the evidence may mean
- Hypothesis: an idea that still needs to be tested
- Decision: what the team chooses to do and why
- Be honest about what is real, simulated, or still unknown.
- Choose a method because it fits the question, not just to check a box.
- Keep observations separate from interpretation.
- Look for evidence that challenges the preferred solution.
- Include accessibility, consent, privacy, and participant comfort in the plan from the start.
- Connect recommendations to an owner and a way to check whether they worked.
- Write for people who need to make a decision, not only for other researchers.
The frameworks and templates are available under the MIT License. Participant data, client material, and third-party assets are not included.