Rosenverse

This video is only accessible to Gold members. Log in or register for a free Gold Trial Account to watch.

Log in Register

Most conference talks are accessible to Gold members, while community videos are generally available to all logged-in members.

Co-creating research enablement with your tech org: a case study

Gold
Tuesday, March 10, 2026 • Advancing Research 2026
Share the love for this talk
Co-creating research enablement with your tech org: a case study
Speakers: Elizabeth Sklar and Jessica Sheng
Link:

Summary

Challenge we faced - We’re a small, centralized research team that sits within our organization’s Strategy team. For years, we’ve wanted to invest more in enablement, esepcially for our Technology teams. However, with limited resources and a steady stream of high-priority research requests from executives, we struggled to make progress. - We’d experimented from time to time with enablement efforts, but we hadn’t seen meaningful change in behaviors or research fluency. For example, we built templates, shared them, and put them in our internal knowledge library – but team members quickly forgot where to find them, and they got lost in the ever-growing library. We gave basic research training to the Design team, but that wasn’t enough to impact the Technology org as a whole – their Product and Engineering counterparts didn’t share the same context and didn’t buy in. - We knew we needed to become enablers as our company grew and large-scale research questions were increasing, but our past efforts hadn’t been the best use of our limited resources; just focusing on the top priority research had been more impactful than the enablement efforts we’d made thus far. Signals it was time for a change - We earned strong executive buy in. After seeing the impact that well-scoped, well-timed research made when led by our team, Tech leadership was ready to have their people dedicate time to it as well. We showed them clear measurable outcomes – that enabling teams to do research will reduce time-to-impact for our customers, and allow us to scale research impact without significant investment in new headcount. - We had the resources. Leadership buy-in allowed us to invest upfront to roll out enablement efforts at scale. - Other Technology processes were changing at the same time. There was a large initiative to improve our product development lifecycle and implement new related processes. Our research enablement efforts could attach to those and reinforce them, rather than being their own disconnected initiative. How we’re addressing In the past six months, we shifted gears and made a concentrated investment in research enablement across our ~400-person Technology org. This case study shares how Research and Research Operations partnered to build and scale research education, operations, and tooling across Product, Design, and Engineering. In particular, this case study will focus on our design and delivery of multi-day hands-on skill building workshops for the Technology org, and an accompanying research playbook. How we’re measuring success We measured insights fluency of our Technology organization using a self-assessment survey (~n=175), which we’ll re-administer at the conclusion of our workshop series in January. This will provide clear data on change in knowledge. Also at that time, we’ll be formally evaluating behavior change via usage metrics of our playbooks and templates, usage of Research Office Hours, and Research Support Requests. Lastly, we’ll be evaluating with Technology leadership to gain understanding of new research taking place across their org, and whether and how it’s impacting decision making.

Key Insights

  • Providing research materials alone is insufficient; teams need serious skill development to produce quality data.

  • Co-creating enablement programs with the product organization ensures better alignment and adoption.

  • Multi-day, interactive workshops aligned with the product development lifecycle enhance hands-on learning and retention.

  • Embedding research support within existing communication tools like Slack improves accessibility and reduces friction.

  • Offering tiered support—from full partnership to office hours—helps balance workload and meet varying team needs.

  • Dedicated enablement efforts significantly increase confidence and engagement in research across diverse teams.

  • Though resource-intensive, going big on research enablement yields disproportionately higher impact than additional effort.

  • Sharing strategic research responsibilities with product teams generates more bandwidth for high-level company research.

  • Leadership openness to investing team time on research enablement is critical for success.

  • Continuous iteration and feedback integration are necessary to keep enablement relevant and effective in a growing organization.

Notable Quotes

"We thought she was in great shape and we were thrilled, then found out she didn’t know to BCC 500 customers—this still stresses me years later."

"We went very, very big instead of an annoying side project; it became the core of our research systems."

"Our past enablement was exacerbating issues because teams had resources but not enough skills."

"We are co-creating with the product organization to make sure everything fits seamlessly rather than being separate."

"We put heavy trust in our stakeholders and co-created the curriculum with them."

"Our bet was that distributing ownership would create more advocates and free bandwidth for strategic work."

"We tried hybrid sessions but quickly learned splitting virtual and in-person was better for experience."

"We underestimated the amount of work; each workshop took about 40 hours per person to prepare and run."

"Asking for help and engaging is actually a sign of growing confidence among teams."

"This process has moved us from facilitators of knowledge to owners of knowledge."

Ask the Rosenbot
Ricardo Martins
Unlocking the power of advanced quantitative methods
2025 • Advancing Research 2025
Gold
Sarah Brooks
Theme 3 Intro
2021 • Civic Design 2021
Gold
Angelos Arnis
State of DesignOps: Learnings from the 2021 Global Report
2021 • DesignOps Summit 2021
Gold
Bria Alexander
Opening Remarks
2023 • DesignOps Summit 2023
Gold
Mandy Drew
What Role(s) Can Research Play in Responsible Design?
2021 • Advancing Research 2021
Gold
Jack Behar
How to Build Prototypes that Behave like an End-Product
2022 • Design in Product 2022
Gold
Mujtaba Hameed
Frameworks for Excellence: Using Visual Thinking and Communication to Elevate Your Research
2024 • Advancing Research 2024
Gold
Tricia Wang
From Users to Shapers of AI: The Future of Research
2024 • Advancing Research 2024
Gold
Sarah Gallimore
Inspire Progress with Artifacts from the Future
2022 • Civic Design 2022
Gold
Megan Nipe
Human-Centered Design for Engagement: Maturing from Newsletterville to Personalized, One-to-One Messaging
2021 • Civic Design 2021
Gold
Bria Alexander
OKRs—Helpful or Harmful?
2022 • DesignOps Community
Emily Williams
When UX Research and Institutional Racism Collide: A Case Study
2021 • Advancing Research 2021
Gold
Laura Klein
Human vs. machine: Testing AI’s ability to synthesize and analyze research
2026 • Advancing Research 2026
Gold
Raven Veal
Dark Metrics: Illuminating the Negative Impact of Digital Health Design
2021 • Advancing Research 2021
Gold
Daniel Korczynski
Why AI Is Bad at Research (and how to make it actually useful)
2026 • Advancing Research 2026
Gold
Terry Buckman
Wargaming (An Introduction)
2023 • Enterprise Community

More Videos

Jim Kalbach

"Design ops’ job is like jazz rules—it provides a framework so creativity can flow without worrying about inventing structure mid-process."

Jim Kalbach

Jazz Improvisation as a Model for Team Collaboration

November 6, 2017

Louis Rosenfeld

"Don’t write a book expecting to retire on royalties; this is a specialized field with modest sales."

Louis Rosenfeld

Coffee with Lou: Should You Write a (UX) Book?

March 7, 2024

Catt Small

"You don’t have to become a manager or director to advance; becoming a principal IC role is equally influential."

Catt Small Micah Bennett Brian Carr Jessica Harllee

What's Next for ICs: Exploring Staff and Principal Designer Roles

February 22, 2024

Marieke McCloskey

"Typically we get stuck answering the questions we know we can answer but lose the chance to see the big picture."

Marieke McCloskey

User Science: Product Analytics & User Research

March 11, 2021

Llewyn Paine

"Even if you’re not doing facial recognition, storing face and voice data is under growing legal scrutiny."

Llewyn Paine

[Demo] Deploying AI doppelgangers to de-identify user research recordings

June 5, 2024

Joshua Noble

"You don’t want to overdesign just to make something more data interpretable because that can lead you down a dark path."

Joshua Noble

Casual Inference

October 6, 2023

Sara Logel

"We’re biologically wired to respond to intellectual challenges the same way as physical threats."

Sara Logel

Your Colleagues are Your Users Too

March 29, 2023

Bria Alexander

"Enterprise is kind of sexy because big, hairy, hard problems of scale and distribution live at the enterprise."

Bria Alexander Louis Rosenfeld

Welcome

January 8, 2024

Sam Proulx

"When you design for the edges, you make things better, more fluid, more customizable for everyone."

Sam Proulx

Online Shopping: Designing an Accessible Experience

June 7, 2023