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
- Design as Research: Artifacts and interactions reveal insights that surveys alone cannot
- Iterative Inquiry: Each prototype informs the next cycle of investigation
- Participant Co-creation: Users aren't studied but collaborate in knowledge creation
- Contextualized Learning: Understanding emerges from real-world use, not decontextualized settings
- Embodied Knowledge: Lived experience and tacit knowledge are primary data sources
- 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:
Sketch & Storyboard (low-fidelity)
- Paper sketches, comic-style interactions
- Quickly explore multiple directions
- Gather initial reactions
Role-Play & Bodystorming (embodied exploration)
- Act out interaction scenarios
- Participants physically engage with imagined interface
- Reveals gestural and emotional dimensions
Digital Mockup (medium-fidelity)
- Interactive prototypes in Figma or similar
- Realistic workflow but not fully functional
- Test navigation and information architecture
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:
- User Testing Session: 3-6 participants interact with current prototype
- Data Collection: Video, audio, think-aloud protocols, observation notes
- Participant Feedback: Structured and informal reflection
- Analysis & Insights: Identify what the prototype revealed about needs
- Design Decision: Specific changes informed by findings
- 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
- Familiarization: Immerse in data (watch videos, read transcripts)
- Initial Coding: Mark meaningful units relevant to research question
- Theme Development: Group codes into emergent themes
- Theme Refinement: Define relationships between themes
- Interpretation: Connect themes to design implications
- 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
1---2name: qualitative-research-through-design3description: 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.4---5
6# Qualitative Research-Through-Design for Wellbeing
7
8Research-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.
9
10## Methodology Overview
11
12### Core Principles
131. **Design as Research**: Artifacts and interactions reveal insights that surveys alone cannot
142. **Iterative Inquiry**: Each prototype informs the next cycle of investigation
153. **Participant Co-creation**: Users aren't studied but collaborate in knowledge creation
164. **Contextualized Learning**: Understanding emerges from real-world use, not decontextualized settings
175. **Embodied Knowledge**: Lived experience and tacit knowledge are primary data sources
186. **Reflective Practice**: Designer reflexivity about their own biases and assumptions
19
20## RtD for Wellbeing Design Process
21
22### Phase 1: Problem Framing (4-6 weeks)
23
24**Goal**: Understand the design space through participant lenses, not researcher assumptions
25
26#### Activities:
27- **Contextual Inquiry**: Observe users in natural environments (home, workplace, recreation)
28- **Shadowing**: Follow users through daily activities relevant to design question
29- **Deep Interviews**: 60-90 minute unstructured conversations about lived experience
30- **Photo Elicitation**: Participants photograph their world; discuss images together
31- **Journey Mapping**: Co-create visual representations of user pathways and emotional arcs
32
33#### Deliverables:
34- Rich descriptions of participant worlds (personas, but narrative-based)
35- Identified pain points and wellbeing opportunities
36- Design themes and tensions worth investigating
37- Preliminary "How Might We?" questions framed with participant language
38
39#### Analysis:
40- **Thematic Coding**: Inductive identification of patterns from interview transcripts
41- **Affinity Diagramming**: Group themes by relationships and clusters
42- **Emotional Mapping**: Visualize affect and wellbeing fluctuations in context
43- **Constraint Identification**: Systemic factors affecting user agency and flourishing
44
45### Phase 2: Design Exploration & Prototyping (8-12 weeks)
46
47**Goal**: Create tangible prototypes to investigate design possibilities and participant needs
48
49#### Prototype Fidelity Progression:
501. **Sketch & Storyboard** (low-fidelity)
51 - Paper sketches, comic-style interactions
52 - Quickly explore multiple directions
53 - Gather initial reactions
54
552. **Role-Play & Bodystorming** (embodied exploration)
56 - Act out interaction scenarios
57 - Participants physically engage with imagined interface
58 - Reveals gestural and emotional dimensions
59
603. **Digital Mockup** (medium-fidelity)
61 - Interactive prototypes in Figma or similar
62 - Realistic workflow but not fully functional
63 - Test navigation and information architecture
64
654. **Functional Prototype** (high-fidelity)
66 - Working code or near-working implementation
67 - Extended use in realistic context
68 - Investigate edge cases and emotional nuance
69
70#### Co-design Sessions (Structure):
71- **Warm-up**: Creative activity to establish trust and energy (30 min)
72- **Context Setting**: Remind participants of design challenge (10 min)
73- **Exploration**: Participants interact with prototypes (30-45 min)
74- **Reflection**: Guided discussion about experience (30-45 min)
75- **Synthesis**: Participants help interpret findings (15 min)
76
77#### Key Questions to Investigate:
78- Does this design respect user autonomy or feel controlling?
79- Does it enable competence or increase cognitive load?
80- Does it foster genuine relatedness or perform intimacy?
81- What emotional states does it evoke? Are they intentional?
82- What aspects feel aligned with user values?
83- What unintended consequences emerge?
84
85### Phase 3: Iterative Refinement (Ongoing)
86
87**Goal**: Deepen understanding through successive prototype generations
88
89#### Each Cycle:
901. **User Testing Session**: 3-6 participants interact with current prototype
912. **Data Collection**: Video, audio, think-aloud protocols, observation notes
923. **Participant Feedback**: Structured and informal reflection
934. **Analysis & Insights**: Identify what the prototype revealed about needs
945. **Design Decision**: Specific changes informed by findings
956. **Prototype Evolution**: Implement and prepare for next cycle
96
97#### When to Stop Iterating:
98- Patterns have stabilized (no new insights from 2 cycles)
99- Diminishing returns on refinement
100- Core design principles clarified
101- Ready for evaluation phase
102
103## Data Collection Methods
104
105### Video & Screen Recording
106- **Strengths**: Captures nonverbal communication, interaction patterns, emotional reactions
107- **Analysis**: Code interaction sequences, moment-by-moment emotional shifts, hesitations
108- **Ethical**: Always get explicit video consent; transcribe sensitive sections
109
110### Think-Aloud Protocols
111- Participant narrates reasoning while using prototype
112- **Strengths**: Direct access to mental models and decision-making
113- **Limitation**: Artificial, changes behavior; use sparingly with difficult tasks
114
115### Observation Notes
116- Contextual field notes during sessions
117- Record emotions, body language, environmental factors
118- Note moments of confusion, delight, frustration, engagement
119
120### Semi-structured Interviews
121- Prepare guide with core questions, adapt to conversation flow
122- **Opening**: "Tell me about your experience with the prototype"
123- **Deepening**: "You seemed hesitant when... Can you tell me more?"
124- **Exploring**: "How did that compare to how you currently do this?"
125- **Closing**: "Is there anything you wish the design did differently?"
126
127### Participatory Annotation
128- Users mark up printed or digital prototypes
129- Circle problem areas, add notes, suggest changes
130- Combines visual and verbal feedback
131
132### Experience Mapping Workshops
133- Participants collaboratively create journey maps during sessions
134- Map emotional highs/lows, pain points, moments of agency
135- Integrates lived experience as primary data
136
137## Analysis & Interpretation
138
139### Thematic Analysis Process
140
1411. **Familiarization**: Immerse in data (watch videos, read transcripts)
1422. **Initial Coding**: Mark meaningful units relevant to research question
1433. **Theme Development**: Group codes into emergent themes
1444. **Theme Refinement**: Define relationships between themes
1455. **Interpretation**: Connect themes to design implications
1466. **Member Checking**: Share findings with participants; refine interpretations
147
148### Coding Frameworks
149
150**Deductive Coding**:
151- Apply pre-existing framework (e.g., Desmet's 13 needs)
152- Code for how prototypes support/frustrate each need
153- Enables systematic comparison
154
155**Inductive Coding**:
156- Allow themes to emerge from data
157- Capture unexpected wellbeing dimensions
158- Reveals researcher blind spots
159
160**Hybrid Approach** (Recommended):
161- Start with framework, remain open to emergent themes
162- Code for known constructs AND note anomalies
163- Stronger validity and responsiveness
164
165### Interpretive Rigor
166
167**Triangulation**:
168- Multiple data sources (observation, interview, artifact)
169- Multiple researchers (compare independent coding)
170- Multiple cycles (patterns across iterations)
171
172**Negative Cases**:
173- Actively seek exceptions to identified patterns
174- Revise interpretations to account for outliers
175- Prevents overconfident claims
176
177**Reflexivity**:
178- Document researcher assumptions and biases
179- Acknowledge positionality (how your identity shapes interpretation)
180- Question design decisions motivated by researcher preference rather than data
181
182**Transparency**:
183- Quote participant language in findings
184- Show coding examples
185- Explain interpretation reasoning
186- Acknowledge limitations
187
188## Wellbeing-Specific RtD Considerations
189
190### Emotional Safety
191- Prototyping intimate wellbeing features may surface vulnerabilities
192- Create psychologically safe co-design environments
193- Have mental health resources available
194- Debrief with participants about emotional impact
195
196### Ethical Participation
197- Informed consent explaining research purpose and use
198- Participant right to withdraw without judgment
199- Equitable compensation for time and emotional labor
200- Transparent about commercialization plans
201
202### Authenticity vs. Idealization
203- Challenge tendency to design "perfect" wellbeing experiences
204- Investigate real-world friction, ambivalence, complexity
205- Resist simplistic "happiness" as design goal
206- Explore how design supports flourishing amid life's difficulties
207
208### Capturing Nuance
209- Wellbeing is context-dependent and personally defined
210- Same feature affects different people differently
211- Document individual differences, not average user
212- Explore contradictions (e.g., comfort vs. growth challenge)
213
214## Documentation & Outputs
215
216### Design Artifacts
217- **Annotated Prototypes**: Screenshots with insights, design decisions noted
218- **Journey Maps**: Emotional arcs and wellbeing touchpoints
219- **Insight Cards**: Key findings on individual cards (shareable)
220- **Personas**: Rich narrative descriptions of user worlds
221
222### Research Outputs
223- **Design Principles**: Derived from findings (e.g., "Design for autonomy, not dependence")
224- **Interaction Patterns**: Demonstrated to support specific wellbeing needs
225- **Caution Points**: Where design commonly frustrates wellbeing
226- **Wellbeing Framework**: How design operates within Desmet's model
227
228### Dissemination
229- **Research Reports**: Detailed findings with quotes and analysis
230- **Visual Presentations**: Design research stories for stakeholders
231- **Academic Papers**: Rigorous analysis for peer review
232- **Practice Guides**: Actionable principles for design teams
233
234## Common Challenges & Solutions
235
236| **Challenge** | **Solution** |
237|---------------|------------|
238| Small sample sizes feel unrepresentative | Document participant diversity carefully; focus on depth not breadth |
239| Lack of statistical significance | Shift to qualitative validity criteria (credibility, transferability) |
240| Difficulty recruiting participants | Partner with community organizations; compensate fairly; iterate on recruitment |
241| Participants tell you what they think you want | Triangulate with observation; look for contradictions; test with real use |
242| Analysis feels subjective | Apply systematic coding; multiple coders; member checking |
243| Stakeholders want "proof" from RtD | Complement with quantitative measures; frame as exploratory precursor |
244| Design direction from feedback feels unclear | Focus on patterns, not individual suggestions; synthesize principles |
245
246## Integration with Other Methods
247
248**RtD + Psychometrics**:
249- Use validated scales to measure wellbeing outcomes of prototypes
250- Complement numeric findings with qualitative richness
251
252**RtD + Participatory Design**:
253- Co-design sessions are natural RtD activity
254- Participants as researchers in problem framing
255
256**RtD + Service Design**:
257- Investigate entire experience ecosystem, not just interface
258- Map touchpoints and stakeholder interactions
259
260**RtD + Design Ethnography**:
261- Extended immersion in user contexts
262- Long-term relationship building with participants
263
264## Resources & References
265
266- **Key Authors**: Frayling, Findeli, Koskinen, Smeenk, Zimmerman & Forlizzi
267- **Methods**: Design probes, experience prototyping, cultural probes
268- **Tools**: Atlas.ti, NVivo, MAXQDA for qualitative data analysis
269- **Communities**: Design Research Society, International Association of Societies of Design Research