Short answer
Recognize that usability findings are a product of team interpretation and collaboration, not just objective data points.
- Field
- User-Centred Design
- Source
- ACM Transactions on Computer-Human Interaction (2019)
- Method
- Ethnomethodological study
- Evidence
- Moderate effect
Usability findings are not simply discovered but are actively constructed through the collaborative interpretation and negotiation of observed user interactions during testing. This user-centred design research insight is drawn from a 2019 study published in ACM Transactions on Computer-Human Interaction. Using Ethnomethodological study, researchers explored how this design variable affects real-world outcomes. The key design takeaway: Recognize that usability findings are a product of team interpretation and collaboration, not just objective data points.
Usability Findings Emerge from Collaborative Observation, Not Just Direct Detection
Usability findings are not simply discovered but are actively constructed through the collaborative interpretation and negotiation of observed user interactions during testing.
ACM Transactions on Computer-Human Interaction · 2019
Key Findings
- 01Usability findings are produced through the collaborative work of observers analyzing the test as it unfolds.
- 02Potential usability issues can be 'dissipated' or overlooked during the collaborative sense-making process.
- 03The conventional view of findings being 'there to be found' or 'read off' by evaluators is nuanced.
Application
Design takeaway
Recognize that usability findings are a product of team interpretation and collaboration, not just objective data points.
How to apply
When conducting usability tests, ensure that the observation and analysis phases involve structured collaborative discussion among team members to ensure a comprehensive understanding of user behavior and potential issues.
Project actions
- 01When reporting usability findings, describe not just the issue but also how your team discussed and agreed upon it.
- 02Consider how different team members' perspectives might influence the identification of usability problems.
Method & Evidence
Variables
Strengths & Limitations
Strengths
- +Provides a detailed, practice-based account of usability testing.
- +Challenges conventional, simplified views of usability evaluation.
Limitations
The specific tools and team dynamics of the consultancy might influence how findings are produced.
Reliability & validity
Reliability might be moderate as different teams could produce different findings. Validity is strong in representing the situated practice of usability testing.
Think critically
How might the 'dissipation' of candidate troubles during collaborative analysis impact the thoroughness of a usability evaluation?
Design Principles
"Usability evaluation is a socio-technical practice where findings are co-constructed through observation and shared interpretation."
This challenges the notion that usability findings are objective truths waiting to be uncovered. Instead, it highlights that the process of identifying and reporting issues is a social and interpretive act, influenced by the team's collective understanding and focus.
What This Means for Your Design
When you watch someone use a product, you and your teammates don't just see problems; you talk about what you see and decide together what counts as a problem, and sometimes you might miss things because of how you talk about it.
How to use in your project
- 1.Reference this study when discussing how your team interpreted user feedback or observed behaviors during your usability testing phase.
Add to My Project
Quick Cite
Paragraph starter
The process of generating usability findings is not merely an act of objective observation but a situated, collaborative practice. As demonstrated by Reeves (2019), practitioners actively construct findings through shared interpretation of user interactions, where potential issues can be both identified and, at times, dissipated through team discussion. This highlights the importance of acknowledging the interpretive lens through which usability data is processed in design practice.
Source
ACM Transactions on Computer-Human Interaction
How UX Practitioners Produce Findings in Usability Testing
journal · 2019
View sourceQuestions About This Research
- What does the research say about usability findings emerge from collaborative observation, not just direct detection?
- Recognize that usability findings are a product of team interpretation and collaboration, not just objective data points. Evidence: ACM Transactions on Computer-Human Interaction (2019).
- Why does "Usability Findings Emerge from Collaborative Observation, Not Just Direct Detection" matter for design?
- This challenges the notion that usability findings are objective truths waiting to be uncovered. Instead, it highlights that the process of identifying and reporting issues is a social and interpretive act, influenced by the team's collective understanding and focus.
- How can designers apply this research?
- Recognize that usability findings are a product of team interpretation and collaboration, not just objective data points.
- What were the main findings?
- Usability findings are produced through the collaborative work of observers analyzing the test as it unfolds.. Potential usability issues can be 'dissipated' or overlooked during the collaborative sense-making process.. The conventional view of findings being 'there to be found' or 'read off' by evaluators is nuanced.
- What research method was used?
- Ethnomethodological study.
- How strong is the evidence?
- Evidence strength is rated Moderate effect, based on a 2019 journal from ACM Transactions on Computer-Human Interaction.
- What should I do differently in my next project?
- When conducting usability tests, ensure that the observation and analysis phases involve structured collaborative discussion among team members to ensure a comprehensive understanding of user behavior and potential issues.
- What are the limitations?
- The study is specific to the observed design consultancy and may not generalize to all usability testing contexts.