This document discusses ResearchOps, which is defined as the mechanisms and strategies that set user research in motion by providing the roles, tools, and processes to support researchers in delivering and scaling the impact of their work across an organization. An initiative was run by a global community to better define and validate the concept of ResearchOps through workshops and a survey. The initiative found that ResearchOps helps researchers focus on their craft by providing infrastructure, and depends on strong research leadership to succeed. The community aims to further shape understanding of ResearchOps to help with hiring and setting job expectations.

1. 東京、⽇日本
#WhatisResearchOps

2. OH NO! NOT
ANOTHER
OPS!

3. %&#@

4. ResearchOps is the mechanisms
and strategies that set user
research in motion. It provides the
roles, tools and processes needed
to support researchers in
delivering and scaling the impact
of the craft across an organisation.
@teamreops / @katetowsey

5. ResearchOps is the mechanisms
and strategies that set user
research in motion. It provides the
roles, tools and processes needed
to support researchers in
delivering and scaling the impact
of the craft across an organisation.
@teamreops / @katetowsey

6. @teamreops / @katetowsey

7. ResearchOps Community
& #WhatisResearchOps initiative
+ give you some context
+ the team
+ what we did
+ what we learned
+ what’s next

8. Context
@teamreops / @katetowsey

9. @teamreops / @katetowsey

10. 8 months later...
+ 1000+ Slack members
+ #researchops is lively
+ #whatisresearchops initiative is done
+ 60 organisers globally
+ 17 countries / 34 cities
@teamreops / @katetowsey

12. The aim of the Community is
to give shape to and validate
research operations AKA
ResearchOps.
@teamreops / @katetowsey

13. Why now?
In-house teams
are getting
bigger. Concepts
around research
leadership are
being formed.
More and more,
executives and
management are looking
to researchers for
guidance and answers.
And holding
researchers
responsible.
Research is being
accepted as an
integral part of
design and
delivery.
+ +

14. We’re in this phase of
massive growth.

15. We’re in this phase of
massive growth.
But.

16. Team size.
Buy in.
Support.
Infrastructure.
Coordination.
To-do list.
Pressures.
@teamreops / @katetowsey

17. Team size.
Buy in.
Support.
Infrastructure.
Coordination.
To-do list.
Pressures.
@teamreops / @katetowsey

18. Team size.
Buy in.
Coordination.
To-do list.
Pressures.
@teamreops / @katetowsey

19. When you see the list of
things that researchers are
doing, you’ll wonder how it all
gets done.
Sometimes it doesn’t.

20. Community
@teamreops / @katetowsey

21. Kate Towsey / UK
Andrew Maier / USA
Emma Boulton / UK
Brigette Metzler / Australia
Nishita Gill / India
Chris Adams / Germany
Kathryn Hing / Germany
Ruth Ellison / Australia
Ben Cubbon / UK
Steph Troeth / UK
TeamReOps

22. We wanted a shared understanding
of what ResearchOps is.
We did this through a series of global
workshops.
@teamreops / @katetowsey

23. @teamreops / @katetowsey

25. @teamreops / @katetowsey

26. Kate Towsey / UK
Ben Cubbon / UK
Steph Troeth / UK
Emma Boulton / UK
Audree Fletcher / UK
Andy Parker / UK
Mark McElhaw / UK
Saskia Liebenberg / UK
Monica Ferraro / UK
Ed Crowley / UK
Jane Reid / Scotland
Chris Adams / Germany
Kathryn Hing / Germany
Maria Arrilucea / Spain
Daniel Boos / Switzerland
Daria Hoplova / Russia
Hugo Froes/ Portugal
Global organisers
Lily Ainsworth / Australia
Sandy Ho / Australia
Michelle Pickrell / Australia
Kristina Lund Hansen / Australia
Katie Phillips / Australia
Catherine Sutton-Long / Australia
Johnny Linnert / Japan
Tomomi Sasaki / Japan
Rob Enslin / South Africa
Marie Slundt / South Africa
Nishita Gill / India
Shreya Toshniwal / India
Ruben Perez Huidobro / Canada
Kathleen Asjes / Sweden
Kea Zhang / Norway
Amanda Pike / USA
Marisa Morby / USA
Andrew Maier / USA
Holly Cole/ USA
Andi Galpern / USA
Ryan Hunt / USA
Michael Bam / USA
Sheetal Agarwal / USA
Andrew Maier / USA
Jeanette Fuccella / USA
Melissa Braxton / USA
Yushi Wang / China
Samantha Yuen / Singapore
Brigette Metzler / Australia
Ruth Ellison / Australia

27. This has all been driven by team.
We achieved things together.
It’s open source.
@teamreops / @katetowsey

28. What we did
@teamreops / @katetowsey

29. @teamreops / @katetowsey

30. We ran workshops using
Liberating Structures 1-2-4-all.
And asked 4 questions.
@teamreops / @katetowsey

31. 1. What research operational challenges have
you experienced?
2. What are your operational successes, if any?
3. Where do you see opportunities to improve
research operations in your organisation?
4. What do you think ResearchOps includes?
@teamreops / @katetowsey

32. We ran a survey that was
answered by 300+ people.
@teamreops / @katetowsey

33. @teamreops / @katetowsey
What we learned
What it is

34. @teamreops / @katetowsey
We’ve now got a definition.
Which will no doubt be
tested and shaped in the
future.

35. ResearchOps is the mechanisms
and strategies that set user
research in motion. It provides the
roles, tools and processes needed
to support researchers in
delivering and scaling the impact
of the craft across an organisation.
@teamreops / @katetowsey

36. "So we defined ResearchOps as infrastructure that
makes research teams more successful. So we talked
about ResearchOps doing recruitment, being
responsible for community-building, providing all kinds
of tools - the licenses, the software, hardware, tools,
audio/visual support, providing an insights repository -
it's a place where we can also support activities from
our teams, documentation, providing resources for our
stakeholders, resources potentially for onboarding, and
defining roles on our teams and creating partnerships."
- Melissa Braxton and Sheetal Agarwal, Seattle
@teamreops / @katetowsey

37. https://
www.aureliuslab.com/

38. https://kumu.io/TeamReOps/
what-is-researchops

39. ​ ​
mural.ly/link

40. What we learned
What it is
What it’s not
@teamreops / @katetowsey

41. It helps researchers focus on the craft.
It’s not craft.
It’s not only about insights and data. It’s also about people.
It’s not research methodology or strategy. It supports their
implementation.
It’s not research leadership. It supports research leadership.

42. What we learned
What it is
What it is not
What it depends on
@teamreops / @katetowsey

43. ResearchOps needs good
research leadership to
succeed.
@teamreops / @katetowsey

44. 34 x data sets about ResearchOps.
And lots of data about research
leadership too.
@teamreops / @katetowsey

45. What next?
@teamreops / @katetowsey

46. Our first aim was to give
shape to and validate
ResearchOps.
@teamreops / @katetowsey

47. Our first aim was to give
shape to and validate
ResearchOps.
@teamreops / @katetowsey

48. Our first aim was to give
shape to and validate
ResearchOps.
We’ve got new aims.
@teamreops / @katetowsey

49. Help companies know what they’re hiring
for.
Help hires know what their job should
include and what resources they need.
Include small business in the
conversation.

50. EPIC

51. Thank you
+ Follow @teamreops
+ Join the Slack waitlist
+ Come to one of our town halls
+ Watch town hall videos on Vimeo
+ Join the conversation: #ResearchOps and
#WhatisResearchOps
Branding and design by treemouse.com
https://twitter.com/teamreops
https://vimeo.com/
user89807865
teamreops@gmail.com