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
"Self-directed learning is hard and busy, but you have to make time and schedule learning religiously."
Sara ConklinA UXer’s 12-Month Journey from Climate Concern to Climate Credibility
June 26, 2025
"We as people are our data, which means we have to treat data problems with care and consideration."
David ConradThe Feeling of Data
September 14, 2023
"Novice users can try things out thanks to automation, but experts can focus on the challenging and creative pieces."
Clara Kliman-SilverUX Futures: The Role of Artificial Intelligence in Design
June 7, 2023
"You want to assist people in framing the interaction and setting their expectations correctly so they know how to be successful."
Savannah CarlinDon't botch the bot: Designing interactions for AI
June 4, 2024
"We have crypto nights like people pleasing, perfectionism, silos, and burnout—which we watch out for carefully."
Kate Koch Jean-Claire FitschenFlex Your Super Powers: When a Design Ops Team Scales to Power CX
September 29, 2021
"You need thick skin to deal with longstanding institutions who are skeptical because they've seen many projects come and go."
Magdalena ZadaraZero Hour: How to Get Far Quickly When Starting Your Digital Service Unit Late
November 16, 2022
"Just throwing numbers at people does not engage them; pairing data with personal stories or quotes makes the findings resonate."
Eduardo Ortiz Robin Beers Rachael Dietkus, LCSW Bruce Gillespie Jess Greco Marieke McCloskey Renee ReidDay 3 Theme Panel
March 13, 2025
"Design leaders with shared ownership at the C-suite table impact revenue and product research significantly."
Fatimah RichmondThe Future of ReOps as a Strategic Function: A Roadmap for Getting There
March 25, 2024
"Broken processes aren't scalable."
Sarah Sgarlato Pierini Kevin NewtonFrom Passion to Execution: A Story of Evolving Research Maturity at LinkedIn
September 9, 2022