Member-only story
Time to talk about Research-Ops
An emerging new discipline that has taken its name with a nod to DevOps and DesignOps.
I was inspired to gather my point of view here for the following reasons:
- There’s not a lot written on this topic because it is not a ‘thing’ yet.
- I wanted to spread hope and share the possibilities with the research community who can feel exhausted between budget conversations and/or executing in silos. (been there-done that)
- Announce to the leaders who are eager to find new ways to increase customer obsession in their organizations. This is the structural change that can set the behavioral change in motion.
First things first; a hat tip to Kate Towsey who baptized the Research-Ops slack channel and legitimized the need for this capability.
Alright, let’s get started. The definition is shifting sands. So, let me begin with mine and be prepared for a reality check.
Research-Ops is an emerging discipline. The primary goals are to:
- Operationalize customer research function to reduce inefficiencies and scale across projects via repeatable process with reliable timelines, ready-to-apply methods and templates.
- Make research more relatable and encourage cross-functional team participation in understanding customers
- Make research insights more accessible for everyone in the company to easily…