Summary
In eighteen months, Zendesk’s UX Research practice grew from a single researcher to a seven-person team. The new research program has greatly enhanced Zendesk’s design and development process. Along the way, researchers have successfully informed design strategy and helped improve product quality and usability. Veevi Rosenstein is deliberately crafting the UX research practice from the inside out to support Zendesk’s growing development organization. She’ll share her approach and overall vision for the research program, including operational plans, methods, toolkits, communication and knowledge capture strategies, and the steps she’s taken to make it all happen.
Key Insights
-
•
Scaling UX research at Zendesk started with deep listening sessions to understand existing pain points and stakeholder needs.
-
•
Participant recruitment was the biggest bottleneck slowing product research and needed a dedicated coordinator role.
-
•
Internal development of recruiting tools like ZenRate was hindered by lack of IT and dev bandwidth, pushing towards selecting external SaaS solutions.
-
•
UserTesting’s built-in panel dramatically shortened turnaround times for usability studies and convinced stakeholders to invest in the tool.
-
•
Creating a rolling study program assigned researchers to specific user roles, increasing efficiency and preventing participant fatigue.
-
•
Improving designers’ and product managers’ research skills through workshops on unbiased interviewing raised the quality of research insights.
-
•
Providing easy-to-use templates and shared analysis methods like affinity diagrams helped teams collaboratively capture and reuse research data.
-
•
Developing role-based user profiles from aggregated research data gave product teams focused, actionable personas for design decisions.
-
•
Centralizing research resources in a searchable internal help center empowered self-serve learning and increased research practice consistency.
-
•
A ticketing system to track research requests helped manage demand and build a case for growing the UX research team further.
Notable Quotes
"When I started at Zendesk in 2018, there was a single UX researcher serving 28 product designers around the globe."
"Participant recruitment was the number one problem that people mentioned, and it was the primary reason UX research initiatives felt like they took too long."
"At first, product managers often skipped getting customers involved or talked to the same four or five friendly customers repeatedly."
"Having a pool of interested users and tracking their participation helps avoid participant fatigue and internal bottlenecks."
"We created a rolling study program where researchers owned expertise for specific user roles, resulting in more efficient studies."
"Research methods are like design patterns, and the interview is a basic pattern everyone can learn to do well."
"Some teams went right into brainstorming based on what they remembered from observations without documenting or analyzing the data."
"I showed teams tips and templates to organize and analyze raw data so insights could be shared and reused beyond one project."
"Our UX research team leveraged detailed analyses to create Zendesk’s first set of role-based profiles as a foundation for user personas."
"Implementing a ticketing workflow lets us track research requests and responses and build a stronger case for more headcount."
Or choose a question:
More Videos
"You need strong regional players with negotiation skills to navigate the split loyalties in global teams."
Adam Cutler Karen Pascoe Ian Swinson Susan WorthmanDiscussion
June 8, 2016
"We don’t get upset when users say one thing and do another, but we freak out when our leadership behaves that way."
Peter MerholzThe Trials and Tribulations of Directors of UX (Videoconference)
July 13, 2023
"Nobody knows who’s supposed to decide what around digital, and that’s the problem."
Lisa WelchmanCleaning Up Our Mess: Digital Governance for Designers
June 14, 2018
"Policy change is the backbone of effective climate strategies in urban areas."
Vincent BrathwaiteOpener: Past, Present, and Future—Closing the Racial Divide in Design Teams
October 22, 2020
"The squad model flopped for us after six months but created culture triads that stuck around."
Brenna FallonLearning Over Outcomes
October 24, 2019
"Treat identities as elastic, not as fixed personas, because people’s needs and roles are complex and changing."
Tricia WangSpatial Collapse: Designing for Emergent Culture
January 8, 2024
"Proto personas created by cross-department participants helped us build unbiased, relevant survey questions."
Edgar Anzaldua MorenoUsing Research to Determine Unique Value Proposition
March 11, 2021
"We want to build teams with diverse skill sets so we can create a full picture during the knowledge creation phase."
Designing Systems at Scale
November 7, 2018
"A lot of developers are way too confident they write perfect code; testing bug fixes often reveals hidden issues."
Erin WeigelGet Your Whole Team Testing to Design for Impact
July 24, 2024
Latest Books All books
Dig deeper with the Rosenbot
Is it worthwhile to accept a lower salary offer to get a job in a competitive UX market?
How might subscription services be redesigned using thinking styles to better address user financial and emotional concerns?
What design principles did the Shakers use to create a sense of warmth and belonging in their communities?