Acceptance testing

Okay.

If possible, or if they have their dev UAT or staging environments, at least in those environments, they can convert those regional set up to zonal only within the region only because in dev staging or UAT, they don't want high resiliency, high ability or DR setup.

Okay.

So that can be limited to a particular region only.

And that's a hidden cost.

Okay.

So if it's not business critical, it's in their UAT or staging, keep it to your region only.

So you'll not pay the hidden cost or the operational cost.

That's then also, of course, a big challenge.

I mean, I think it was Anthropic just pulled back internet access from their UAT testers or their early testers because of the security concerns that it kept jumping out of the sandbox and doing what it felt like doing.

So they had to limit early testing from having internet access.

You're like, that's probably not great, right?

So the tactic here is identifying these key individuals and bringing them in early.

The research talks about involving them in user acceptance testing or UAT gathering their feedback and transforming them into peer guides.

Right.

Now, for anyone who hasn't been through a tech rollout, UAT is basically when a company lets a small group of actual employees test drive the software before giving it to the whole company, usually to hunt for bugs.

Yes.

Normally, UAT is treated as a technical exercise, but psychologically, it should be treated as an influence-building exercise.

Because of human nature.

Right.

So we do have several developers in-house and we do have a lot of custom code that has been created over the years, some one-off tools.

And recently we have just learned that it is That's one of the most efficient things we've experienced with this is converting old code to new code and building applications faster and honestly just quicker to UAT testing than what used to take a year takes a week, you know, sometimes with the initial launch.

But we're doing a lot of that also.

And I think that's gonna pay dividends.

And once I got into Tableau, then what do I do? I did a lot of building.

I did a lot of UAT.

I did a lot of trial and error.

But eventually he and I got something that worked really, really well for him.

I mentioned the descriptive statistics.

And I needed to match two very specific formats for the PDFs that we needed to submit for exhibits.

So I did a lot of trial and error, and I did a lot of UAT.

So let's get into it a little bit.

Boom.

Yeah, and so I think that that's a huge plus, because especially with a lot of studies having so many amendments these days, I think that that's a huge lift for the sites as well as the sponsors and the people who are doing the UAT testing and all that stuff.

I think, though...

I think it's an efficiency.

Because, you know, once you kind of assume that your requirements are relatively locked down and now you're starting, you know, even kind of your depth cycles, you know, every time you start introducing change during those processes, it's very disruptive, right? Because it requires you to go ahead and go back and it has implications to, you know, Thank you.

It has implications to the cycle time, and you're doing UAT over again, and you have to do...

It makes everything more complicated with QA testing and et cetera, et cetera.

Anyways, that takeaway from all that, to your point just a moment ago, just to tie us back together, is... is that we need to do a much, much better job of taking our requirements but presenting them to our customers early in the process.