Summary
Join us as Zapier's Senior Insights Program Manager, Michelle Bejian Lotia, shares her research repository journey. With insights coming from all directions at Zapier, important research was often lost in the fray, resulting in repeated projects and siloed efforts. By consolidating insights into a repository that all stakeholders could access and contribute to, Michelle is looking to compound Zapier's research efforts and drive insight-led decision-making across the organization. Come along and hear firsthand the challenges and triumphs of rolling out a research repository in a growing, fully remote organization.
Key Insights
-
•
Zapier already had a strong, research-focused, remote-working culture, which eased repository adoption.
-
•
A major problem was poor discoverability of existing insights causing duplicate research efforts.
-
•
Multiple teams (UXR, market research, data insights) had differing formats, requiring flexible repository support.
-
•
Michelle used a "show don’t tell" approach by creating realistic user profiles and demo videos to secure stakeholder buy-in.
-
•
Curating and migrating existing research to the new repository took about a quarter, including deciding to unify qualitative and quantitative insights in one place.
-
•
Global Insight fields and metadata enabled powerful filtering and future-proofing across diverse content types.
-
•
Over a third of Zapier’s company engaged with the repository shortly after launch, indicating strong adoption.
-
•
The repository allowed UX researchers to do more focused literature reviews and build on past insights, speeding up research planning.
-
•
Flexible workflows and templates replaced formal peer-review approval, fitting Zapier’s transparent feedback culture.
-
•
Michelle sees AI as useful for summarizing and filtering insights but not for strategic interpretation or decision-making.
Notable Quotes
"People would think new research needed to be done because existing insights were hard to find."
"Show don’t tell was really critical for getting buy-in from stakeholders."
"We wanted everyone to have a serious wow moment on day one when they logged in."
"Once we put all these insights into the repository, things we already have get so much more value."
"Over a third of the company has signed in since launch, which felt amazing."
"Researchers can do more narrowly focused new questions because they see what we’ve already done."
"We deliberately use project folders as work-in-progress spaces before migrating insights into the main hub."
"Our culture means if someone publishes something questionable, there’s a transparent discussion."
"AI can help cut through the noise, but it can’t replace knowing our company strategy or customer context."
"Closing the loop by asking authors what action is taken from their insight helps researchers feel accountable."
Or choose a question:
More Videos
"There’s never enough attention you can give to change management in scaling design impact — don’t do it alone."
Standardizing Product Merits for Leaders, Designers, and Everyone
June 15, 2018
"Very few people in business are familiar with situational awareness unless they served in the military."
Simon WardleyMaps and Topographical Intelligence (Videoconference)
January 31, 2019
"Cisgender binary options in onboarding flows exclude non-binary and gender-expansive identities."
Sandra CamachoCreating More Bias-Proof Designs
January 22, 2025
"By observing Jeff’s concerns and asking questions, I was able to show empathy and focus on the problem rather than get defensive."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"We mitigated data privacy risks by subscribing to the corporate plan for ChatGPT, which offers enhanced security."
Fisayo Osilaja[Demo] The AI edge: From researcher to strategist
June 4, 2024
"Creating tangible artifacts forces reaction and debate, helping break enterprise paralysis and drive decisions."
Uday GajendarThe Wicked Craft of Enterprise UX
May 13, 2015
"No official kickoff was held, which meant shifting expectations and lack of alignment."
Davis Neable Guy SegalHow to Drive a Design Project When you Don’t Have a Design Team
June 10, 2021
"People felt designs were self-evident and too much explanation was a barrier to using the patterns."
Eniola OluwoleLessons From the DesignOps Journey of the World's Largest Travel Site
October 24, 2019
"Most of us in design are very process-oriented, but traditional devops tools are task and issue-centric, making collaboration hard."
Aurobinda Pradhan Shashank DeshpandeIntroduction to Collaborative DesignOps using Cubyts
September 9, 2022
