TeamReOps Profile Banner
TeamReOps Profile
TeamReOps

@TeamReOps

Followers
3K
Following
697
Media
97
Statuses
1K

Tweets from the global team of organisers behind the ResearchOps Community.

Joined May 2018
Don't wanna be here? Send us removal request.
@TeamReOps
TeamReOps
2 years
New on ResearchOps Community Medium - Japanese translation of The 8 Pillars of User Research! https://t.co/PYUdFo2yVX Thanks to Rikuto Murakami for the translation!
Tweet card summary image
medium.com
翻訳元:The Eight Pillars of User Research | by Emma Boulton | researchops-community | Medium
0
1
2
@TeamReOps
TeamReOps
2 years
New ResearchOps Community article — Peter Fossick’s 8 Ps Framework for ReOps It’s a useful organizing tool pulled from his new book “Operations Thinking - Research Operations” https://t.co/Mq0AxJHQ37
Tweet card summary image
medium.com
In today’s rapidly evolving business landscape, organizations are realizing that the key to creating products and services that truly…
0
0
2
@TeamReOps
TeamReOps
2 years
New ResearchOps Community article — Minimum Viable Taxonomy Level 2! A toolkit for building out a taxonomy that facilitates report categorisation and more complex activities such as data analysis, insights discoverability, and more… https://t.co/lkiafllzvb
Tweet card summary image
researchops.community
The MVT Level 2 process was led by Annette Boyer who authored the original toolkit on which this article is based. This article was written by Will Edmiston, Rogério Lourenço, Karolina Kowalczyk,...
1
0
0
@TeamReOps
TeamReOps
2 years
Incentives were a hot topic at #ROC23 this year, including people who can't accept #incentives like a speaker or two of ours. So we donated their honorarium to help @MSF_USA save the lives of people caught in crisis. #doctorswithoutborders #MédecinsSansFrontières
0
1
1
@TeamReOps
TeamReOps
2 years
Ops can breakdown silos
0
0
0
@TeamReOps
TeamReOps
2 years
There are no handoffs, it comes from working closely with each other.
1
0
0
@TeamReOps
TeamReOps
2 years
Post study — insights with a short life span
1
0
0
@TeamReOps
TeamReOps
2 years
Reporting — poor stakeholder engagement
1
0
0
@TeamReOps
TeamReOps
2 years
Execution — nothing takes the wind out of your sales like struggling to recruit participants
1
0
0
@TeamReOps
TeamReOps
2 years
Planning — Slapdash candidate screeners
1
0
0
@TeamReOps
TeamReOps
2 years
Pre-study — incomplete recruitment briefs Brings Ops into the conversation early on
1
0
0
@TeamReOps
TeamReOps
2 years
5 friction points
1
0
0
@TeamReOps
TeamReOps
2 years
Our next presentation is Kate Fisher & Julia Cowing — Relationship-building with researchers: Failure and recovery #ROC23
1
0
2
@TeamReOps
TeamReOps
2 years
Thank you Rachel!!!! An absolutely incredible presentation!
0
0
0
@TeamReOps
TeamReOps
2 years
Q: What are the automated processes? A: The plan across program for research, recruitment and scheduling. When it's entered it is added to multiple pages, and it will add that to other pages and suggest what they might look at.
1
0
0
@TeamReOps
TeamReOps
2 years
Q: How is the organisation aware of what research is coming up A: We have key lines of communication with other researchers and we share the same document management system and we meet regularly to share what we're working on. We field a lot of queries from other departments
1
0
0
@TeamReOps
TeamReOps
2 years
Q: Templates for desk research and tips A: One of the key things was making sure the benefits could see the date of confidence to a date, so a new project team can start from a certain point rather than from the start. We ask the research to write a summary of what they have
1
0
0
@TeamReOps
TeamReOps
2 years
Q: Your tech stacl A: It was already through the security and governance — we're using Atlassian suite, so we didn't have to do a massive change management project and hidden costs associated with new software
1
0
0
@TeamReOps
TeamReOps
2 years
Q: How do you get buy in higher up? A: Speak management's language, focus on the narrative management want (reduce budget, more efficient, demonstrate on the smaller scale) Because it was a flagship benefit projects it had massive upper management visibility
1
0
0
@TeamReOps
TeamReOps
2 years
Don't be daunted Prioritise Work with the resources available Find out what your org and team needs are Always think about efficiency Bring the team with you
1
0
0