6 Comments
User's avatar
𝚐𝚎𝚘𝚛𝚐𝚎's avatar

We desperately need more 'ResearchOps makers' stepping up to create scalable knowledge architectures for business units outside UX, much like Salesforce Research has successfully demonstrated. Achieving this practically overnight requires aiming for enterprise-wide research repos and developing the chops to confidently build fully vector-based semantic prompts. I am thrilled to say this evolution is already happening with me as we fully embrace this exciting new wave of agentic ResearchOps. That said, makers are about self experimentation... so it's a both/and when it comes to me/I and the Other. This is easier to do as a consultant to small orgs than as an enterprise associate since large orgs are slow to adopt agentic processes.

Kate Towsey's avatar

Thanks for your comment, George. I've not seen the Salesforce articles or demos, but I'd be interested to. Do you mind linking a reference? I agree that I-Me-Mine AI is a necessity, and, on top of that, we need the system makers to step up. I'm pleased to hear that you're experimenting with the cutting edge.

𝚐𝚎𝚘𝚛𝚐𝚎's avatar

The Salesforce reference is from Nalini Katamraju's presentation (3/24) a few years back at the Advancing Research Conf. just prior to your book release 9/24. The content is behind a paywall at Rosenfeld Media. Her presentation is called "Research After UX". https://rosenverse.rosenfeldmedia.com/videos/research-after-ux . There are quotes below the video.

Below are just 2 of many other quotes:

"What happens if research does not report into UX? What might happen if we uncouple research from UX?" ~Nalini Katamraju

"After the move, our work had more impact, more visibility, and we're present across the entire product life cycle." ~Nalini Katamraju

The ResearchOps Review's avatar

I'm late to respond to this, George, but thanks for the additional references. I shall take a look! Kate

Kyle Kubas's avatar

Holy S***! Yes, this is exactly the world we are living and breathing right now as ReOps leaders, and it's a huge opportunity. Thank you for so clearly articulating this - multiple ways we are moving and grooving internally clock to this, around positioning ourselves to lead the way in building these durable systems in a sea of ad hoc Replits. The tidal wave of Claude Code is making this work even more imperative. Time will tell if the positioning will work. Appreciate your POV, always - keep going!

The ResearchOps Review's avatar

Hello, Kyle. 👋 Kate here.

Thanks for letting me know that this article hit a home run.

Your comment gave me an image of ripples ("Replits") and waves ("The tidal wave of Claude Code"). The water analogy is a good one: we can get wiped out by the tsunami, get bogged down in mud, or learn to surf the wave—or better yet, build and own the waterpark before anyone else.