Building for Scale: Creating the Zendesk UX Research Practice
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 requires deeply understanding internal stakeholder pain points through listening sessions before making hires.
-
•
Recruiting representative research participants was the top bottleneck and perceived cause of slow insight delivery at Zendesk.
-
•
Legal restrictions on participant incentives and imperfect CRM data complicated recruitment of key user groups like support agents.
-
•
Embedding a dedicated research operations coordinator within design operations was critical to centralize recruitment and logistics.
-
•
A hackathon prototype for an integrated internal recruitment tool (ZenRate) proved conceptually sound but lacked organizational support to maintain.
-
•
External vendor tools like UserTesting and Qualtrics were chosen for security, compliance, collaboration, and data portability to speed research turnaround.
-
•
A rolling omnibus study program assigned researchers to focus on specific user roles, enabling recurring qualitative studies and shared recruiting pools.
-
•
Training workshops to improve interviewing skills helped democratize research quality among designers and product managers.
-
•
Structured data capture and analysis templates using Google Sheets and Miro enabled richer insight sharing beyond isolated projects.
-
•
Building an internal help center with searchable playbooks and a ticketing system improved accessibility and tracking of research requests, supporting team growth.
Notable Quotes
"When I started at Zendesk in 2018, there was a single UX researcher in Singapore doing her best to serve 28 product designers around the globe."
"Participant recruitment was the number one problem that people mentioned."
"We were asking for users to give us their time, but we weren’t showing them that we recognized that their time had value."
"Some product managers just skipped getting customers involved in the development process at all."
"Having a back office support in place made it much easier to convince new researchers to join the team."
"The proof of concept actually worked, but it had to be coded as an internal application, and somebody would have to maintain the tool."
"We used user testing’s built-in panel and that significantly reduced the turnaround time on conducting design studies."
"If you think of research methods as design patterns, the interview is a basic design pattern at the heart of most qualitative research methods."
"A lot of the rich juicy details from their time on sites would have been lost, and that hurt my nerdy soul."
"Since everyone was doing their own research, the quality of the research being done was pretty inconsistent."
Or choose a question:
More Videos
"We had to convince our director and executives by showing how the repository added real value for the product team."
Taylor Jennings Joe Nelson Alex KnollRepository Retrospective: Learnings from Introducing a Central Place for UX Research
March 9, 2022
"How we orient ourselves to the future impacts how we experience the present."
Nicole AleongFuture Orientations to Everyday Life: Futures Anthropology as a Methodology
March 26, 2024
"Disruptive innovation doesn’t happen overnight; you have to practice, fail, learn, and have patience."
Jeff GothelfInnovation Studios: the Engines of Enterprise Experimentation
May 14, 2015
"If you don't have dedicated accessibility people, start grassroots by building empathy and rallying teams around user stories."
Saara Kamppari-MillerDesignOps for Inclusive Design and Accessibility
May 26, 2022
"Our culture has diminished a lot of the other things in life that are supposed to give us meaning and put infinite pressure on work."
Tess DixonC'mon Get Happy
September 29, 2021
"Building a great culture means caring for individuals and creating rituals like recognition and shared learning."
Liam ThurstonWhy Your Design Team Is Quitting, And How To Fix It
June 10, 2022
"Communication matters—sending an email to an executive with spelling mistakes can ruin your respect."
Ian SwinsonDesigning and Driving UX Careers
June 8, 2016
"At Atlassian, many confident non-researchers were already doing lots of research, which was an opportunity and a challenge."
Leisa ReicheltOpening Keynote: Operating in Context
November 7, 2018
"Without a design ops function, teams make their own flavors that dilute brand and accessibility."
Rachael Greene Alison DavisBuilding a Design Ops Practice that Really Works (Most of the Time)
October 2, 2025
