Natalie Padilla

So our stakeholder came back saying like, wow, I expect this would be a month before we saw results.

And the design lead came back and said, this was very easy and it was nice to be able to pull

it into a sprint without having to reiterate everything that I had expected from the research in the story.

I didn't have to rewrite the whole practice.

I just pulled the card and said, do this.

And then that worked.

And it pivoted and delivered very quickly.

Yeah, that's a really good question, Natalie.

I have an example, I think, of this that sort of dances around your question, but I think it does get to the right answer.

And it's good because it's a specific example.

um our our user test research method card or our recipe so when we like when we started we were just building out the first cards we had we're still figuring out like what the scope of it is and how granular they got right and we had this user test research method card and what ended up happening is we split it into three and this is this is through working with you i promise this is coming back to your question

So we we first started on those cards.

There was some aversion to complexity, I think, and making sure that the ops were at the right level was important.

Maybe we were too concerned about complexity.

I think it's like you've got to feel your way into a new system.

And so we wanted to start small and then, you know.

include complexity where it was important.

But I came to one of the consulting sessions and we went through a few rounds of this where we were kind of talking back and forth about how granular we should get.

And this is like one of the first ones.

I remember I asked you about this and you had pulled up three test templates from your playbook.