So as a BI architect, I mean different projects have different complexities, like if there's a migration project, I will focus more on daily to daily basis, what is the planning, split planning, check out for the stories that we have, especially more for migration perspective and compare between the two reports or between the two data, right? So how the data integrity is there, whether the pipelines are working fine, our data sets are fine, is there any outage or not in terms of refreshing the reports, as well as any kind of other challenges that we have, like if we are failing in some other tasks, like the data integrity is not there, or we are moving into the next step, that is on the mind. But if it is more towards not a migration, it's just more of a development and creating a holistic end to end EDW as well as architecture and reporting, then it's difficult and then it's different. So I will focus more on what we have as reporting, it will be more discussion on our daily to daily basis with the team, because we don't have a sample which we are migrating to from. So here we have more discussion with the end user, how they want to see the reports, how they want to see the data and also look in terms of the complexities they wanted to like, I can give an example for the Power Apps. So if they want some more functionalities that are there and then leading my team in terms of defining any issues with their work. So I set up some time with them in terms of technical challenges, if they are not able to understand the situation or they are not able to understand or create a Spotify logic or issue with any Spotify reports. That's something I looked into on a daily to daily basis.

