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
"Screen readers let us jump from one heading to another, replicating the experience of skimming a page visually."
Sam ProulxSUS: A System Unusable for Twenty Percent of the Population
December 9, 2021
"Government is seven plus years behind industry – not bleeding edge, more like the dull butter knife edge."
Michael LandEstablishing Design Operations in Government
February 18, 2021
"We had to push through analysis paralysis and trust our guts as customer-facing teams that knew the business."
Shipra KayanHow we Built a VoC (Voice of the Customer) Practice at Upwork from the Ground Up
September 30, 2021
"Innovation is about being fearless, breaking rules, and refusing to stop at the way things have always been done."
Ian SwinsonDesigning and Driving UX Careers
June 8, 2016
"The chief of staff serves as a bridge between the design program managers, executive assistants, and other ux and product chiefs of staff."
Isaac HeyveldExpand DesignOps Leadership as a Chief of Staff
September 8, 2022
"Change is messy and it can be uncomfortable, much like baking bread—it’s hard to imagine sticky dough turning into a perfect loaf."
Amy EvansHow to Create Change
September 25, 2024
"You should take risks, and if you fail, you need to fail fast and pivot immediately."
Kate Koch Prateek KalliFlex Your Super Powers: When a Design Ops Team Scales to Power CX
September 30, 2021
"Beliefs are habits of action; they are the rules that guide how we decide to act."
Dave GrayLiminal Thinking: Sense-making for systems in large organizations
May 14, 2015
"Providing immediate tactical value is the big one for just-in-time curation."
Matt DuignanAtomizing Research: Trend or Trap
March 30, 2020