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
"It was a tax I had to pay my entire career — balancing the work and trying to lift my community."
Dantley DavisLeadership & Diversity—A Fireside Chat with Dantley Davis
September 17, 2020
"We need more storytelling and positive use cases to help people see how AI affects their specific roles."
Frances Yllana Jorge Arango Maria Taylor Briana ThomasThe Big Question about Impact: A Panel Discussion
September 24, 2024
"Our relationship is like a genuine brotherhood. We hang out almost every day."
Jim KalbachPeace is waged with sticky notes: Mapping Real-World Experiences
June 14, 2018
"Stakeholders saw design as a slow-moving black box — exactly what we were trying to move away from."
Sarah Kinkade Mariana Ortiz-ReyesDesign Management Models in the Face of Transformation
June 8, 2022
"It is not the responsibility of marginalized groups to do all the educating about their experiences."
Reginé GilbertAsking the Right Questions: Life, Hope and Moving Forward During the Pandemic
June 10, 2022
"Simon Roberts calls this the UX ification of research, which leads to a more transactional focus on informing technology requirements."
Robin BeersNavigating organizational systems: Rethinking researcher’s role in driving change
March 13, 2025
"I didn’t want to be an AI guy. That was never my goal."
Paul FordNew work, new words: A glossary for AI
June 9, 2026
"The value of a design system looks different depending on if you’re a developer, designer, or stakeholder."
Dan DonaldDesign Systems as a Vehicle for Systemic Change
June 1, 2023
"Our approach eliminates the need for developers to inspect design specs to recreate styling and layouts from scratch."
George Abraham Stefan IvanovDesign Systems To-Go: Reimagining Developer Handoff, and Introducing App Builder (Part 2)
October 1, 2021
Latest Books All books
Dig deeper with the Rosenbot
What are the benefits and challenges of pairing engineers and designers in small, focused pods for product development?
Why is practicing quick visual sense-making important for UX professionals?
How can designers use AI to create entirely new interaction paradigms instead of just improving productivity?