qualitative-research-through-design

name	Qualitative Research-Through-Design
description	Apply research-through-design (RtD) methodology to investigate wellbeing in design contexts. Use when conducting user research, creating prototypes for understanding user needs, iteratively validating design decisions, or documenting lived experiences. Combines qualitative inquiry with iterative design and participant co-creation.

Qualitative Research-Through-Design for Wellbeing

Research-Through-Design (RtD) is a rigorous methodology that treats design artifacts as research instruments. Rather than designing to solve a known problem, RtD uses iterative prototyping and participant engagement to investigate complex design challenges and generate new knowledge.

Methodology Overview

Core Principles

1. Design as Research: Artifacts and interactions reveal insights that surveys alone cannot
2. Iterative Inquiry: Each prototype informs the next cycle of investigation
3. Participant Co-creation: Users aren't studied but collaborate in knowledge creation
4. Contextualized Learning: Understanding emerges from real-world use, not decontextualized settings
5. Embodied Knowledge: Lived experience and tacit knowledge are primary data sources
6. Reflective Practice: Designer reflexivity about their own biases and assumptions

RtD for Wellbeing Design Process

Phase 1: Problem Framing (4-6 weeks)

Goal: Understand the design space through participant lenses, not researcher assumptions

Activities:

• Contextual Inquiry: Observe users in natural environments (home, workplace, recreation)
• Shadowing: Follow users through daily activities relevant to design question
• Deep Interviews: 60-90 minute unstructured conversations about lived experience
• Photo Elicitation: Participants photograph their world; discuss images together
• Journey Mapping: Co-create visual representations of user pathways and emotional arcs

Deliverables:

• Rich descriptions of participant worlds (personas, but narrative-based)
• Identified pain points and wellbeing opportunities
• Design themes and tensions worth investigating
• Preliminary "How Might We?" questions framed with participant language

Analysis:

• Thematic Coding: Inductive identification of patterns from interview transcripts
• Affinity Diagramming: Group themes by relationships and clusters
• Emotional Mapping: Visualize affect and wellbeing fluctuations in context
• Constraint Identification: Systemic factors affecting user agency and flourishing

Phase 2: Design Exploration & Prototyping (8-12 weeks)

Goal: Create tangible prototypes to investigate design possibilities and participant needs

Prototype Fidelity Progression:

1. Sketch & Storyboard (low-fidelity)

   • Paper sketches, comic-style interactions
   • Quickly explore multiple directions
   • Gather initial reactions

2. Role-Play & Bodystorming (embodied exploration)

   • Act out interaction scenarios
   • Participants physically engage with imagined interface
   • Reveals gestural and emotional dimensions

3. Digital Mockup (medium-fidelity)

   • Interactive prototypes in Figma or similar
   • Realistic workflow but not fully functional
   • Test navigation and information architecture

4. Functional Prototype (high-fidelity)

   • Working code or near-working implementation
   • Extended use in realistic context
   • Investigate edge cases and emotional nuance

Co-design Sessions (Structure):

• Warm-up: Creative activity to establish trust and energy (30 min)
• Context Setting: Remind participants of design challenge (10 min)
• Exploration: Participants interact with prototypes (30-45 min)
• Reflection: Guided discussion about experience (30-45 min)
• Synthesis: Participants help interpret findings (15 min)

Key Questions to Investigate:

• Does this design respect user autonomy or feel controlling?
• Does it enable competence or increase cognitive load?
• Does it foster genuine relatedness or perform intimacy?
• What emotional states does it evoke? Are they intentional?
• What aspects feel aligned with user values?
• What unintended consequences emerge?

Phase 3: Iterative Refinement (Ongoing)

Goal: Deepen understanding through successive prototype generations

Each Cycle:

1. User Testing Session: 3-6 participants interact with current prototype
2. Data Collection: Video, audio, think-aloud protocols, observation notes
3. Participant Feedback: Structured and informal reflection
4. Analysis & Insights: Identify what the prototype revealed about needs
5. Design Decision: Specific changes informed by findings
6. Prototype Evolution: Implement and prepare for next cycle

When to Stop Iterating:

• Patterns have stabilized (no new insights from 2 cycles)
• Diminishing returns on refinement
• Core design principles clarified
• Ready for evaluation phase

Data Collection Methods

Video & Screen Recording

• Strengths: Captures nonverbal communication, interaction patterns, emotional reactions
• Analysis: Code interaction sequences, moment-by-moment emotional shifts, hesitations
• Ethical: Always get explicit video consent; transcribe sensitive sections

Think-Aloud Protocols

• Participant narrates reasoning while using prototype
• Strengths: Direct access to mental models and decision-making
• Limitation: Artificial, changes behavior; use sparingly with difficult tasks

Observation Notes

• Contextual field notes during sessions
• Record emotions, body language, environmental factors
• Note moments of confusion, delight, frustration, engagement

Semi-structured Interviews

• Prepare guide with core questions, adapt to conversation flow
• Opening: "Tell me about your experience with the prototype"
• Deepening: "You seemed hesitant when... Can you tell me more?"
• Exploring: "How did that compare to how you currently do this?"
• Closing: "Is there anything you wish the design did differently?"

Participatory Annotation

• Users mark up printed or digital prototypes
• Circle problem areas, add notes, suggest changes
• Combines visual and verbal feedback

Experience Mapping Workshops

• Participants collaboratively create journey maps during sessions
• Map emotional highs/lows, pain points, moments of agency
• Integrates lived experience as primary data

Analysis & Interpretation

Thematic Analysis Process

1. Familiarization: Immerse in data (watch videos, read transcripts)
2. Initial Coding: Mark meaningful units relevant to research question
3. Theme Development: Group codes into emergent themes
4. Theme Refinement: Define relationships between themes
5. Interpretation: Connect themes to design implications
6. Member Checking: Share findings with participants; refine interpretations

Coding Frameworks

Deductive Coding:

• Apply pre-existing framework (e.g., Desmet's 13 needs)
• Code for how prototypes support/frustrate each need
• Enables systematic comparison

Inductive Coding:

• Allow themes to emerge from data
• Capture unexpected wellbeing dimensions
• Reveals researcher blind spots

Hybrid Approach (Recommended):

• Start with framework, remain open to emergent themes
• Code for known constructs AND note anomalies
• Stronger validity and responsiveness

Interpretive Rigor

Triangulation:

• Multiple data sources (observation, interview, artifact)
• Multiple researchers (compare independent coding)
• Multiple cycles (patterns across iterations)

Negative Cases:

• Actively seek exceptions to identified patterns
• Revise interpretations to account for outliers
• Prevents overconfident claims

Reflexivity:

• Document researcher assumptions and biases
• Acknowledge positionality (how your identity shapes interpretation)
• Question design decisions motivated by researcher preference rather than data

Transparency:

• Quote participant language in findings
• Show coding examples
• Explain interpretation reasoning
• Acknowledge limitations

Wellbeing-Specific RtD Considerations

Emotional Safety

• Prototyping intimate wellbeing features may surface vulnerabilities
• Create psychologically safe co-design environments
• Have mental health resources available
• Debrief with participants about emotional impact

Ethical Participation

• Informed consent explaining research purpose and use
• Participant right to withdraw without judgment
• Equitable compensation for time and emotional labor
• Transparent about commercialization plans

Authenticity vs. Idealization

• Challenge tendency to design "perfect" wellbeing experiences
• Investigate real-world friction, ambivalence, complexity
• Resist simplistic "happiness" as design goal
• Explore how design supports flourishing amid life's difficulties

Capturing Nuance

• Wellbeing is context-dependent and personally defined
• Same feature affects different people differently
• Document individual differences, not average user
• Explore contradictions (e.g., comfort vs. growth challenge)

Documentation & Outputs

Design Artifacts

• Annotated Prototypes: Screenshots with insights, design decisions noted
• Journey Maps: Emotional arcs and wellbeing touchpoints
• Insight Cards: Key findings on individual cards (shareable)
• Personas: Rich narrative descriptions of user worlds

Research Outputs

• Design Principles: Derived from findings (e.g., "Design for autonomy, not dependence")
• Interaction Patterns: Demonstrated to support specific wellbeing needs
• Caution Points: Where design commonly frustrates wellbeing
• Wellbeing Framework: How design operates within Desmet's model

Dissemination

• Research Reports: Detailed findings with quotes and analysis
• Visual Presentations: Design research stories for stakeholders
• Academic Papers: Rigorous analysis for peer review
• Practice Guides: Actionable principles for design teams

Common Challenges & Solutions

Challenge	Solution
Small sample sizes feel unrepresentative	Document participant diversity carefully; focus on depth not breadth
Lack of statistical significance	Shift to qualitative validity criteria (credibility, transferability)
Difficulty recruiting participants	Partner with community organizations; compensate fairly; iterate on recruitment
Participants tell you what they think you want	Triangulate with observation; look for contradictions; test with real use
Analysis feels subjective	Apply systematic coding; multiple coders; member checking
Stakeholders want "proof" from RtD	Complement with quantitative measures; frame as exploratory precursor
Design direction from feedback feels unclear	Focus on patterns, not individual suggestions; synthesize principles

Integration with Other Methods

RtD + Psychometrics:

• Use validated scales to measure wellbeing outcomes of prototypes
• Complement numeric findings with qualitative richness

RtD + Participatory Design:

• Co-design sessions are natural RtD activity
• Participants as researchers in problem framing

RtD + Service Design:

• Investigate entire experience ecosystem, not just interface
• Map touchpoints and stakeholder interactions

RtD + Design Ethnography:

• Extended immersion in user contexts
• Long-term relationship building with participants

Resources & References

• Key Authors: Frayling, Findeli, Koskinen, Smeenk, Zimmerman & Forlizzi
• Methods: Design probes, experience prototyping, cultural probes
• Tools: Atlas.ti, NVivo, MAXQDA for qualitative data analysis
• Communities: Design Research Society, International Association of Societies of Design Research