Summary
Software companies love to talk about their shiny new features but very rarely we get to see the why or the principles behind some of their product decisions and how those decisions impact customer's outcomes. In this session, Sofia Quintero, founder of EnjoyHQ will share the philosophy behind EnjoyHQ as a research repository and why it matters.
Key Insights
-
•
Research repositories often fail because UX teams operate as silos with disconnected goals from the broader organization.
-
•
Avoiding folder-based nested structures and instead using flat data models scales better and improves searchability.
-
•
Data entry is the enemy; automations and integrations are crucial to reduce manual input and increase repository adoption.
-
•
Cross-functional collaboration drives successful research workflows; repositories must serve multiple departments beyond just UX.
-
•
Building a repository platform requires balancing business growth and truly benefiting researchers without exploiting attention metrics.
-
•
Supporting modular, fluid research workflows rather than rigid project structures better reflects real-world research practice.
-
•
Openness to integrate best-of-breed tools respects diverse user preferences and avoids the trap of trying to do everything internally.
-
•
Easy data export and migration capabilities prevent vendor lock-in and build customer trust, even if it risks losing users.
-
•
Research teams inevitably use multiple overlapping tools; repositories must accommodate this complexity rather than fight it.
-
•
The founder’s values directly influence product decisions to prioritize ethical design over short-term engagement metrics.
Notable Quotes
"I didn’t want to be part of hacking our attention just to fulfill certain engagement metrics."
"The research repository should never become another silo inside the organization."
"Data entry is the enemy when it comes to sustaining a successful research repository."
"We say no to folders because nested structures don’t scale and they make it hard to find information."
"Research is messy and fluid; your tools should support modular workflows that evolve over time."
"We want to help researchers do exactly what they want, respecting their time and goals."
"We build integrations so teams can bring their data in and share it seamlessly across functions."
"We prioritize easy data export even though it might make it easier for customers to leave us."
"Every organization uses a combination of overlapping tools, and repositories need to support that reality."
"Our product decisions are driven by clear values that put the researcher’s benefit above business growth pressures."
Or choose a question:
More Videos
"If designers spend more time talking about titles than their work, we’re just gazing into our navels."
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
"Digital is a system, not a project. It’s there all the time and you have to keep iterating on it."
Lisa WelchmanCleaning Up Our Mess: Digital Governance for Designers
June 14, 2018
"We need to rethink how our cities are designed and function."
Vincent BrathwaiteOpener: Past, Present, and Future—Closing the Racial Divide in Design Teams
October 22, 2020
"It matters what you build, but it matters more if you learn."
Brenna FallonLearning Over Outcomes
October 24, 2019
"We are all experiencing a spatial collapse, a disruption of our mental models of how we navigate physical and virtual spaces."
Tricia WangSpatial Collapse: Designing for Emergent Culture
January 8, 2024
"Research should be done the same way products are built, with stakeholders as your users."
Edgar Anzaldua MorenoUsing Research to Determine Unique Value Proposition
March 11, 2021
"Leadership buy-in is really important—having an executive who understands the value of knowledge creation, distribution, application, and evaluation."
Designing Systems at Scale
November 7, 2018
"You’re never testing an idea purely; you’re always testing the implementation of that idea."
Erin WeigelGet Your Whole Team Testing to Design for Impact
July 24, 2024
