Natalie Padilla

So that just explains the benefits, the required resources, and the duration of a usability test without overburdening them with everything we need to execute.

And then that third... Oh, go ahead, please.

Yeah, I got you.

So that third artifact is that meal plan or the tasting menu, which we wouldn't have gotten to without recognizing the other things were separate, right?

So the meal plan is like a set of predefined studies that can be matched to various recipes.

phases of a product development cycle.

And so for example, we have this program kickoff one.

program kickoff is like a tasting menu it includes stakeholder interviews generative user interviews and competitive analysis and what's nice about that is then when a program kicks off a design lead can just take that off the shelf make stories in the backlog get everything set and get things moving with like minimal rework trying to like reiterate our practice every time something starts up they just we just run the play or run the tasting menu in this case

So a good case study here, just to give some backup for how it worked out, is we did have a situation a few months ago where a lead was asked to skip usability testing because we had the unfortunate situation where

Stakeholders believed that was going to take too much time.

It was going to push off timelines.

So we didn't have room for it.

And so we did what we were asked.

We pushed back.

We did what we were asked.

But then once the code was going to demo, a higher-up stakeholder started asking for validation.

They're like, well, did we validate this?

And that was a tough spot for our design lead, right?

But because we had this, she was able to pull it, make stories, turned everything around in less than a week.

and the quotes on both sides were really good.