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
-
•
Avoid developing tools that create silos for research teams; promote cross-functional collaboration instead.
-
•
Prioritize user needs and ethical considerations over internal profit metrics when making product decisions.
-
•
Data entry should be minimized to enhance productivity; design workflows to facilitate easy data integration.
-
•
Integrate your product with existing tools to streamline processes and improve usability.
-
•
Utilize a flat data model to aid in efficient data retrieval, avoiding the complexities of traditional nested structures.
-
•
Recognize that research processes are often fluid and modular rather than linear, requiring adaptable tools.
-
•
Design for easy data migration so users can switch tools seamlessly without hindrance.
-
•
Build features that accommodate different research methodologies to keep the product user-friendly and flexible.
-
•
Encourage open communication of research findings across departments to ensure valuable insights inform broader decisions.
-
•
Establish clear values at your organization to guide product development and customer engagement strategies.
Notable Quotes
"I didn't want to be part of that as a founder."
"Whatever we have needs to help researchers not to become a silo."
"Data entry is the enemy."
"Every single team that I talked to has a combination of tools."
"We don't want to become everything; our philosophy is more about openness."
"We were forced to create nested structures, and that is really, really hard."
"How can we make everything that research has to create so that they can combine it in any way possible?"
"When you start using our tool, you’ll wonder why folders are even needed."
"For us, it was efficient from the very beginning that we build a ton of different APIs and data exports."
"The question is how you deal with decisions that do not support revenue goals."
More Videos
"Collaboration is crucial to navigate ambiguity in government service design projects."
Ed MullenDesigning the Unseen: Enabling Institutions to Build Public Trust
November 16, 2022
"When I suggest that we could be catalysts for robust action, this is what I mean."
Peter LevinSolve a Problem Here, Transform a Strategy There: Research as an Occasion for Expanding Organizational Possibility
March 25, 2024
"OKRs create ownership when teams feel empowered to reach those results."
Bria Alexander Benson Low Natalya Pemberton Stephanie GoldthorpeOKRs—Helpful or Harmful?
January 20, 2022
"Our power to unlock greater customer experience quality and efficiency is vital"
Kate Koch Prateek KalliFlex Your Super Powers: When a Design Ops Team Scales to Power CX
September 30, 2021
"We were really scratching our heads at some points about adoption."
Amy MarquezINVEST: Discussion
June 15, 2018
"Be okay with it being messy; humans are less predictable than algorithms."
Brenna FallonLearning Over Outcomes
October 24, 2019
"Sometimes good enough is good enough."
Brian MossWhat Does it Mean to be a Resilient Research Team?
March 9, 2022
"If you can't determine where you started, you can't measure how far you've come."
Adel Du ToitGet Your CFO To Say: 'Our Strategic Goal is User Obsession'
June 10, 2022
"Partnering with businesses allows us to ensure our focus aligns with top priorities."
Kate Koch Jean-Claire FitschenFlex Your Super Powers: When a Design Ops Team Scales to Power CX
September 29, 2021
