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
"Showing people that design Ops will make their lives easier is key to adoption."
Meredith Black Elyse HornbacherBuilding Community and Common Trends to Look for in 2021
December 17, 2020
"Representation is key to avoiding harm and misinterpretation, especially when working with Indigenous and marginalized communities."
Tricia WangThe most popular design thinking strategy is BS
January 27, 2022
"In government, the org chart really matters – it influences who talks to whom and who gets to interface."
Michael LandEstablishing Design Operations in Government
February 18, 2021
"When adversity arises, showing your team aims at the same business target lowers chances of negative impact."
Bassel Deeb Will OsbornDo More With Less: Equip and Lead Design Orgs Through Adversity
October 2, 2023
"There wasn't much attention paid to onboarding team members—not the clients or users, but the actual team."
Tanya SnookDesigning the team experience: Building culture through onboarding
November 4, 2021
"We introduced a context diamond and prototype diamond to impose guardrails around AI-assisted prototyping."
Allan LowsonRehashing the Double Diamond: Collaborating across functions with AI-assisted prototyping
June 9, 2026
"Minimalization feels like a secret mega principle with huge benefits for performance, people, planet, prosperity, and purpose."
James ChudleyDecarbonising User Journeys: How minimising enables us to do more with less
February 19, 2025
"It’s not move fast and break things; it’s slow and steady."
Scott Jensen Sarah Delaney Carmen LiuShort Take #2: UX/Product Lessons from Your Industry Peers
December 6, 2022
"Maker time was the most difficult project I’ve ever handled, but it made a huge difference."
Brennan HartichCommunicating and Establishing DesignOps as a New Function
November 7, 2018
