Opening Keynote: Operating in Context
Summary
You know that thing where you start a new job and suddenly realize that all those great rules of thumb you thought were almost universally true are either impossible or ineffective in your new organization. Welcome to Leisa’s life. In this talk Leisa will share her experience of completely resetting her idea of best practice, implementing a strategy that is the opposite of what everyone expected, and why so few people do what they think is right. You’ll also get bonus thoughts on how to best set up your research team for maximize effectiveness.
Key Insights
-
•
One dedicated researcher per team, researched every sprint, and including users with access needs proved transformative at GDS.
-
•
Boldly asking for needed resources, even if initially seen as outrageous, can secure more support than self-limiting negotiation.
-
•
Context radically changes what research practices and team structures will succeed; one strategy does not fit all organizations.
-
•
Distributed locations and low local user diversity at DTA required extensive fieldwork and creative ways of sharing insights, like empathy walls and Showcases.
-
•
Embedding researchers in every team is not always possible or beneficial, especially in complex, distributed product organizations like Atlassian.
-
•
Pairing researchers to focus on craft and professional growth helps shift teams beyond comfort zones and improve quality in challenging contexts.
-
•
A strong user-centered mindset, rather than pure product or feature focus, is crucial to understand broader user goals beyond current product usage.
-
•
Building research capability and consistency across multiple agencies demands different leadership and operational approaches than centralized teams.
-
•
Avoid focusing on researcher-to-designer or researcher-to-engineer ratios; success depends on problem focus and depth of involvement rather than numeric formulas.
-
•
Uncertainty and humility are assets; embracing them keeps the door open for learning and adapting strategies to changing contexts.
Notable Quotes
"My kids know everything. If you listen to conversations with them, they say I know, Ma, I know."
"Context is really super important not only for design and research but for how you design organizations and ways of working."
"One researcher per team for at least three days a week was considered an outrageous luxury at GDS in 2013."
"If you make rules, put numbers in them, and say them confidently, sometimes people actually do them."
"When negotiating, bring plan A—show what you need and what good looks like—even if it seems outrageous."
"Ratios always start on the premise of spreading people too thin, which is not a great way to get success."
"At DTA, distributed teams and lack of local diversity meant everyone was out in the field a lot to get diverse input."
"Empathy walls emerged at DTA because teams needed a visceral way to bring stories back from the field."
"At Atlassian, many confident non-researchers were already doing lots of research, which was an opportunity and a challenge."
"Choosing the right hill to die on is so important and so hard; the problems that matter come around again and again."
Or choose a question:
More Videos
"You are all very excited about the future of design ops because you are charting the course together."
Alana WashingtonTheme 3 Intro
October 1, 2021
"We started to see children and teenagers as users, not just audiences."
Sofía Delsordo Kassim VeraPublic Policy for Jalisco's Designers to Make Design Matter
December 8, 2021
"Operational excellence means making everything easy — for your team, your customers, and others to understand your value."
Crystal PhilcoxThe Many Faces of Operations
November 6, 2017
"When you press a button like an upvote, it’s the developer’s job to make sure the visual state is communicated via ARIA landmarks."
Sam ProulxDesigning For Screen Readers: Understanding the Mental Models and Techniques of Real Users
December 10, 2021
"I didn’t want to be part of that as a founder, hacking attention just to fulfill engagement metrics."
Sofia QuinteroThe Product Philosophy Behind EnjoyHQ
March 10, 2021
"This is a just-do-it moment. Ask for forgiveness, not permission."
Doug PowellDesignOps and the Next Frontier: Leading Through Unpredictable Change
September 11, 2025
"Design strategy focuses on providing a framework for developing design solutions that support a given product strategy, whereas product strategy addresses the business model, the roadmap, and prioritizing requirements - Frank Guo."
Johanna KollmannInsights-Driven Product Strategy: Get your Research to Count
December 6, 2022
"Black box decision making is a hallmark problem—information goes in, something comes out, but we have no clue why."
Joel BranchHumanizing AI: Filling the Gaps with Multi-faceted Research
March 11, 2021
"If the folks that design this tech don’t know how it works, it’s okay if you don’t know either."
Katie JohnsonDisrupting generative AI products with just-in-time consumer insights
June 4, 2024
