SELECT video_content FROM LIBRARY WHERE SLUG='migration-like-for-like-vs-a-bigger-opportunity-for-change'
Migration like-for-like vs. a bigger opportunity for change
Loading video player...
Seen in other customers, different team members even have a copy of the same report but like slightly different. And there was kind of a discussion at the time when we were doing the migration as to whether we were going to migrate stuff like for like or if we were going to try and find opportunities to change some of those existing reports into something different, more valuable. I guess can you talk a little bit to that, like the decision ended up just being like for like at the time and you made some good points as to why. You'd like Yeah. Think there's definitely an element of gauging trust across the business. For different teams, you'll have different levels of confidence and the ability to be able to either recreate from scratch Yeah. And and verify against maybe the front end of the platforms that they're using day to day that you're getting data from or your internal application potentially for your product led business. And other teams, they may not feel as confident in that, but they may trust the existing reporting. So it is very much a case by case basis. Yeah. And then there's also, like, the time constraint. Right? I think for me, the general approach that we took was we were quite constrained by time Across the business for it. And we felt that the best approach by a very, very small number of assets was to migrate like for like, a, because it just meant that we could have multiple people working on it Yeah. Of which we did employ some of the account professional services team as well. So it was useful to just be able to say, this is what we have. These are the tables in our warehouse that we used to power it. This is what it looks like in in Looker. See if you can get the same numbers in count. And I think I think that worked really well in general. And I think by kind of having this process of itemizing out each of the different assets that we wanted to recreate and migrate, we really were able to quite quickly draw out a to do list for after the migration of what we actually wanted to change or improve or what we wanted to consider changing in the future, not just thinking about making this look identical to what it was. Yeah. Actually thinking about what are what are the bugbears of the stakeholders when we're reviewing the new versions of them as well, which was excellent.