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

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
Kate Kalcevich
Integrating Accessibility in DesignOps
2024 • DesignOps Summit 2024
Gold
Nathan Shedroff
How Will Design be Taught When the Schools Shut Down?
2026 • Rosenfeld Community
Sam Proulx
Online Shopping: Designing an Accessible Experience
2023 • DesignOps Summit 2023
Gold
Frances Yllana
DesignOps–Leading the Path to Parity
2023 • DesignOps Community
Séamus Byrne
Aligning Teams with Choreography
2024 • Enterprise Experience 2020
Gold
Alla Weinberg
People Are Sick of Change: Psychological Safety is the Cure
2023 • DesignOps Community
Louis Rosenfeld
Opening Remarks
2023 • DesignOps Summit 2023
Gold
Kristin Skinner
Five Years of DesignOps
2021 • DesignOps Summit 2021
Gold
Rebecca Buck
Mission: Keep Talent in Research Roles!
2021 • Advancing Research 2021
Gold
Adam Cutler
People + Places + Practices = Outcomes
2016 • Enterprise UX 2016
Gold
Sam Proulx
Understanding Screen Readers on Mobile: How And Why to Learn from Native Users
2023 • Enterprise UX 2023
Gold
Dave Hora
A Research Skills Evolution
2021 • Advancing Research 2021
Gold
Sandra Camacho
Creating More Bias-Proof Designs
2025 • Rosenfeld Community
Nathan Curtis
Discussion
2016 • Enterprise UX 2016
Gold
Lisa Spitz
Building Trust Through Equitable Research Practices
2022 • Civic Design 2022
Gold
Chris Govias
Perspectives on Civic Design
2021 • Civic Design Community

More Videos

Jon Fukuda

"If you don’t operationalize content early, you end up with last minute crunches breaking the design."

Jon Fukuda Jake Burghardt Jose Coronado Natalie Dunbar Denise Tilles

All the Ops: Successful cross-functional collaboration

September 10, 2025

Alana Washington

"You are all very excited about the future of design ops because you are charting the course together."

Alana Washington

Theme 3 Intro

October 1, 2021

Andrew Michael

"At Hotcho, we started with a qualitative focus, swung too far into quantitative, and then found a balanced middle ground."

Andrew Michael

Building a Product Insights Team

March 10, 2022

Nalini P. Kotamraju

"I have a tagline my team is tired of hearing: about 50% of work is getting it done and 50% is getting it used."

Nalini P. Kotamraju

Two Jobs in One: Being a “Leader who is a Researcher” and a “Researcher who is a Leader"

March 10, 2021

Prayag Narula

"Companies have started building their own base camps, but these feel more exclusionary compared to grassroots ones."

Prayag Narula Rida Qadri

HCI 2.0: Humanity Deserves the Attention that UX Research has to Offer

March 28, 2023

Yunyan Li

"Visual specs must include behavior, styles, accessibility, and edge cases so developers build accurately."

Yunyan Li Anna Le Jen Kim

UX Best Practices

June 11, 2021

Shipra Kayan

"We had to push through analysis paralysis and trust our guts as customer-facing teams that knew the business."

Shipra Kayan

How we Built a VoC (Voice of the Customer) Practice at Upwork from the Ground Up

September 30, 2021

Dorelle Rabinowitz

"Feedback isn’t about liking. Helpful feedback needs to be, is this solving your problem or not."

Dorelle Rabinowitz

The Magic Word is Trust

June 15, 2018

Sarah Brooks

"Please continue to share your thoughts and questions as you’ve been doing over the past few days."

Sarah Brooks

Theme 3 Intro

December 10, 2021