Nick Higbee

Yeah.

That's such an amazing quote, Betsy.

I mean, with five minutes to run through the research plan, that is impressive.

I can see why it helps you gain quicker research advocates, get that immediate buy-in.

That sort of trust is invaluable.

It reminds me, Nick, you mentioned that this resulted in a huge increase in research stories as well, the cookbook.

Is that right?

I wonder if maybe you could expand on that and tell us about what kind of supported that growth as well.

I'm really curious with all those different research stories in Azure DevOps, how has this changed the approach that your team takes when collaborating with stakeholders?

I imagine, for instance, prioritizing quality insights, for instance, might change expectations on time investments for those insights due to different types of research.

I'm wondering if any examples around that maybe stand out.

No, absolutely answers that.

I think you can't underplay also the amount of work that went into this system.

To your point, there were new needs really identified along the way and built into this.

I was wondering, Benny, maybe

Maybe you could expand on the operations side a little bit about that.

For instance, you know, requesting standard playbook materials from consulting and then adapting those to your cultures.

We talked about that a little bit early on.

But

Would love if you could expand a little bit more on how you got that internal buy-in specifically with adapting standard materials, knowing what materials to get as well to fit those new needs and new use cases, all those new types of stories.