Thread by @RohanIrvine

Next up we have @katetowsey @RuthEllison & Bridgette Metzler bringing is up to speed about the ResearchOps movement that was created and flourished around the globe. And what does it mean for Australia?

Kate was working at a Research Infrastructure Support and noticed she was having the same conversations about research processes and operations. She started a slack group and had 200 people in a matter of weeks.
#dr19

The aim of the community from the beginning was to shape and validate what Research Operations was.

It had been happening in pockets but hadn't been unified.

So why is the ResearchOps conversation happening now?

With the investment in people and teams they're (Google have 800 researchers, Airbnb has 80) and everyone in businesses are figuring out how valuable we are.

As the team sizes and buy in gets bigger researchers and research teams need to be more coordinated.

The pressure is mounting to not only be great researchers, but great at filing and compliance.

The support infrastructure for research has not grown with the demand.

They conducted 5 workshops around the world

Sorry, they actually went from 5 — but ended up with 35 after research Twitter wanted to get involved!

To scale the workshops they created a workshop guide for others to run.

They used 1-2-4-all which is allowing people to think on a question, share it with a partner, share it with a group, then share it with everyone.

The first workshops had these questions, but a year later they don't seem quite right, but as researchers we learn and iterate.

They managed to touch over 1000 people through the workshops and surveys.

They ended up finding out they had created their own researchOps problems

Ruth is now going to touch on some of the findings:

Resource constraints
Recruitment
Communicating value
Scaling research
Managing knowledge and sharing insights
Maturity

Why do we need researchOps?

So what is researchOps?

First iterations of the ResearchOps framework.
#dr19

Breakdown of some of the parts of the ResearchOps Framework

Governance
Budget
Recruitment
Tools

What is NOT ResearchOps?

Bridgette is going to share with us the insights from the Australian workshops.

We didn't talk about strategy
We didn't really talk about tool

It speaks to Bridgette as research maturity not quite there because we're not talking about strategy

We had an idea that Tools fell into several buckets, where other countries kept tools all as one theme.

Bridgette thinks it may have to do with the size of the country and the nuance of getting research done across such a large geography.

You can play around with the research findings here: kumu.io/TeamReOps/what…

In Hobart they talked about:

In Melbourne:

In Canberra:

In Sydney:

ResearchOps is a team, but it's a seperate team to your researchers. Saying it's everyones responsibilities devalues your work and waters down the impact of your research.

The ResearchOps aim is now:

Build skills frameworks
Build a website
Research repositories

#dr19

@threadreaderapp unroll please!