Building stakeholder trust and understanding

Just to reiterate, the key thing for me is just that additional confidence that you get when you share with stakeholders the way that the data is transformed right away from the screen that they're used to seeing on whatever application they're using to what the report says. And actually being able to really hold someone's hand and walk them through that just buys you so much trust. And I think explains the rationale and the reasons why a particular change might be quite complicated, which they maybe didn't have visibility of before. I think that's probably another part of the question that you asked right in the beginning actually, Holly. Why did we migrate everything like for like? One part of that is like the business needs to understand how much work goes behind the scenes in transforming our data into the way that a report looks. And you need to be able to show them that kind of before you make any changes to it so they're aware that, is this a change I want to make because I just want to see it for the next ten minutes is an ad hoc request? Or is this a change that I want to make ongoing and it's going to take me a week? Because they may not have that visibility. Right? Yeah. And I think that whole piece has really improved at Gateground. The whole business is more aware of when you ask for a a change, how big a change is this? How much work does this take? Usually, I think a data team versus maybe like a product engineering team doesn't have as much resource to kind of not necessarily push back, but decide and decipher the business requirement versus the value add and how much time that could take.