If you're thinking of a composable mindset, so, a composable mindset is an understanding of different processes and different system that work together towards business one or more business objectives. So, the whole concept of a central system really speaks against that. So first of all getting the, the idea that all processes are important and they work together to this purpose, all systems are important and work together is important to grasp, because once you have a central system or central process, it's very easy to start building another monolith. Does that make sense? So it's, if you think of your CMS as your central system for your, let's call it a marketing platform then it's very easy for the architect to get the mindset that we have to bolt things on top of the CMS. And once you have that mindset then the CMS starts to become to become another monolith If you kind of break yourself free from that and think content management is one process, that's the CMS, you've got another which is presentation of content to the user, that's the website, that's another process. It's not really related to the CMS, of course it uses the CMS, but it's not related, login for example, could be another feature or another business capability and and that can also be separated out. Maybe it doesn't even need to know about the CMS, maybe it's a completely different system that works in a different way. So getting the architects to a mindset where the important thing here is the process and not the the system is key to understanding composability. Um, the I would say another thing is to maybe also even free yourself from the idea of technology. Architects, especially IT architects are very focused on how do we solve a problem with technology? The interesting thing when you start to look at composability is that some of the business processes you have might be solvable even without technology, even without or at least without technology that you have to develop and own. So think about software as a service. Software as a service doesn't mean that there's no servers and there's no no technology underneath but it's abstracted away from you. What you buy is a piece of software that already runs on a server somewhere else. So getting IT people to understand that things can be solved without technology is a good, is a key thing as well. So understand that maybe you can let's say something like it's a good example like business intelligence for example, if you want to have analytics around your platform then instead of installing a technology and creating a technology that analyzes and gives you insight on the platform, maybe you can hire an external service to do it. Maybe you can call in some guys and they can create a report for you every month that just tells you how is the platform doing what is the insight. In that case you don't need to do any technology, You don't have to invest in people and technology knowledge and all those kind of things. All you have to do is find a company that can do that. That runs that platform for you. So composability is also about understanding that things can actually be, let's call it outsourced or there's other services that can be hired in from the outside.