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
"Design thinking is for everybody. It’s collaborative, inclusive, and cross-disciplinary."
Doug PowellClosing Keynote: Design at Scale
November 8, 2018
"A growth mindset in research means being ready to adapt protocols based on what actually works with participants."
Mila Kuznetsova Lucy DentonHow Lessons Learned from Our Youngest Users Can Help Us Evolve our Practices
March 9, 2022
"Signals are something that’s happening at the horizon, percolating at the fringes of society or in a narrow subset of the population."
Sarah GallimoreInspire Progress with Artifacts from the Future
November 18, 2022
"Junior team members don’t have to talk directly to executives; working effectively with peers can create grassroots buy-in."
Lada Gorlenko Sharbani Dhar Sébastien Malo Rob Mitzel Ivana Ng Michal Anne RogondinoTheme 1: Discussion
January 8, 2024
"We created an AI persona called Dreamweaver to answer real-time team capacity and project questions."
Alnie FigueroaThe Future of Design Operations: Transforming Our Craft
September 10, 2025
"If you measure an infinite number of customers, every change would be statistically significant, but not every change would be meaningful."
Landon BarnesAre My Research Findings Actually Meaningful?
March 10, 2022
"I felt like a journalist pretending to be a designer."
Emily EagleCan't Rewind: Radio and Retail
June 3, 2019
"We did a blended approach with a visual refresh first to minimize differences between old and new and buy time."
Malini RaoLessons Learned from a 4-year Product Re-platforming Journey
June 9, 2021
"Project management was focused on outputs, assuming the correct feature was already defined."
Asia HoePartnering with Product: A Journey from Junior to Senior Design
November 29, 2023
Latest Books All books
Dig deeper with the Rosenbot
How can service design and design ops collaborate intentionally to increase UX service capacity?
What are effective tactics to build organizational buy-in for service design practices over time?
How can teams integrate inclusive design into early product development stages to avoid costly late fixes?