Fireside Chat
Summary
In this insightful fireside chat, Mike, a seasoned design lead with over 15 years of experience, discusses his evolving relationship with user research and design leadership. Although he humbly admits to not being a researcher himself, Mike highlights the critical role that research played at Twitter and now at Kraken, one of the world's largest digital asset exchanges. He emphasizes that research should be seen as a time-saving and impact-enhancing discipline rather than a bottleneck, particularly when advocating for research teams to be compensated equally to engineers, reflecting their technical expertise and influence. Mike also shares strategies for building and scaling research departments, including hiring, delegation, and organizational alignment, stressing the importance of securing high-level champions such as a CEO or CTO. He explains the unique challenges of conducting sensitive remote research in the crypto space, where privacy and geopolitical issues matter deeply. When addressing common resistance by engineering teams to research, Mike identifies hubris, lack of exposure to strong research, and directive leadership as key factors. He advocates for a culture where team members proactively improve processes beyond their defined roles, supported by behavioral evaluation frameworks rather than outcome-based ones, fostering equity and collective growth. Mike concludes with practical advice to mirror engineering career ladders for researchers to simplify compensation and promotion discussions and reinforce research's equal footing within tech organizations. The conversation is rich with reflections on equity, efficiency, and culture-building in research and design.
Key Insights
-
•
Research, when done well, saves time and prevents costly misdirection, making it an investment rather than a delay.
-
•
Researchers should be paid equally to engineers because their technical skills are equally essential to product success.
-
•
Aligning research teams under influential company leaders, like the CEO or CTO, is key to gaining organizational support.
-
•
Building research teams involves thoughtful hiring pacing to balance individual contributors and managers.
-
•
Remote research in sensitive areas like crypto requires special attention to privacy and geopolitical concerns rarely seen in consumer products.
-
•
Many engineering teams resist research due to hubris, lack of exposure to quality research, or top-down mandates ignoring user evidence.
-
•
Encouraging team members to contribute beyond their explicit roles improves processes and strengthens the team culture.
-
•
Evaluating researchers and designers on behaviors rather than outcomes ensures fairness and accounts for project context variability.
-
•
The research function should report to the part of the organization that can best leverage it, which may vary by company and context.
-
•
Mirroring engineering career frameworks for researchers simplifies compensation and promotion conversations, providing clarity and equity.
Notable Quotes
"I know less about research than anybody at this entire conference, I guarantee."
"At Twitter, I learned how much we were failing users globally despite thinking we were doing excellent work."
"Designers and researchers should get paid like engineers—it's time to value them the same."
"Research is there to save you time, not to take up time."
"If you go a day without making a single decision, that means all decisions in your team have been made correctly."
"I want people on my team to get outside their lane to help improve the team beyond their direct responsibilities."
"Many engineering teams think they know best and would rather take a road to nowhere than wait for research."
"Remote research in crypto is about much more than flipping through a feed; it involves sensitive financial data and privacy concerns."
"You have to find your champion as high up in the company as possible to push for research and equitable pay."
"Mirroring engineering’s career ladder for researchers stops weird conversations about titles and pay differences."
Or choose a question:
More Videos
"Tech industry’s feelings about process can create real problems for UX teams when it makes it hard to create systems."
Amy ThibodeauOpening Keynote: Process and Ambiguity
October 23, 2019
"I found the problem solver in the UI developer and identified the project’s sponsor who really felt the pain."
Carl TurnerYou Can Do This: Understand and Solve Organizational Problems to Jumpstart a Dead Project
March 28, 2023
"Weave in great user stories that exemplify your key points to maximize engagement."
Bruce GillespieLearning from journalism: Balancing impactful communication with compassionate storytelling
March 13, 2025
"We don’t want anyone to change their favorite tools; we build plugins to share wireframes or prototypes directly."
Aurobinda Pradhan Shashank DeshpandeIntroduction to Collaborative DesignOps using Cubyts
September 9, 2022
"Drag and drop ease, and collaborative affinity diagramming in the tool, were unexpected but very welcome advantages."
Taylor Jennings Joe Nelson Alex KnollRepository Retrospective: Learnings from Introducing a Central Place for UX Research
March 9, 2022
"Digital medicine apps are legally considered a pharmaceutical, available by prescription only."
Daniel J. RosenbergDigital Medicine Design
September 26, 2019
"Design influence is messy and requires clear articulation of how we serve business and customer success."
Jack MoffettUX Metrics That Matter and The Future of our Design at Scale Conference: A Community Conversation
September 22, 2022
"If I stop doing it, it stops, and I'm the human in the loop, or the monkey in the middle."
Christian CrumlishThe Pygmalion Effect: In Which a Vibe Coding Experiment Becomes a Million Lines…
August 14, 2025
"Community-centered design allowed us to uplift the value of lived experience and embed it directly into budgeting."
Alexia Cohen Adriane AckermanIncreasing Health Equity and Improving the Service Experience for Under-Served Latine Communities in Arizona
December 4, 2024
