Approach
I'm training to move into equitable Participatory Design research frameworks, drawing specifically from trauma-informed research, design justice, and equitable community-centered design.  
My main area of interest is in accessibility and disability inclusion in games and technology.
I have the most experience in User Centered Design, Human Centered Design, and Design Thinking frameworks, specifically focusing on research and accessibility.
Research Process
Every research project is a little different, but here is a high level process I might follow for a qualitative study under UCD/HCD frameworks. 
I'm happy to elaborate more on what I've done in the past, and what I hope to do in the future in a conversation!
1. Develop the research objective

I start with a conversation to understand research questions, design concerns, and the intended "user" or community of interest.
2. Evaluate test object, select protocol, plan, and write testware

If possible, I try the product and perform competitive reviews of a few market leading, similar products.
Then, I develop a research plan based on the objective, my experiences, and knowledge of the space. Ideally, this is done in partnership and together with the team. 

If the team agrees with the plan, I'd move on to creating discussion guide, survey design, or whatever else is needed to support the study.
3. Include the right people

I'm moving toward living expert and community-led design.
In the past, I've sourced from internal participant lists or external recruiters in the past.

It's critical to consider demographics, familiarity levels with product, and other key factors to ensure we're hearing from the right mix of people. 
4. Run the research, include the team

I moderate the study, which might include periodic benchmarking surveys, lookback, think-aloud, moderated, or unmoderated protocols (depending on the research objectives). 

In all my professional roles, we've supported livestreaming and/or observation. I encourage the team to participate and actively take on a role.

5. Lightweight, actionable insights

After debriefing with the team, I'd spend some time analyzing the data. 
This may involve affinity diagramming, issue identification, behavior encoding, analytics reviews, or survey analysis.
Then, I put together a lightweight report highlighting the main issues, any relevant usability heuristics, and some actionable high level design suggestions. 
I present the report, giving the team some time to digest and ask any further questions. 

6. Keep iterating

My job isn't done once the report is delivered.
I keep in touch with my project owners to see if I can answer any questions, provide feedback on proposed solutions, or run additional research. 
Ideally, we continue working together and iterating to improve the product.

You may also like

Back to Top