 Carl asks, does anyone have any good methods of dealing with team sprawl? I've inherited, whoa, that's, that's a, well, there's, there's a topic. We also solve world peace at the same time. Yes, right here, the next five minutes. I've inherited an instance and to say it as a mess would be an understatement. We have more teams and we have people. I've already turned off the create team function for most people to stop it getting worse, but now I have to sort out this disaster. So good methods for dealing with team sprawl. It's going to involve a spreadsheet and a drink and a late night. And a wooden spoon to slap people in the back of the hand. Yeah, I had, I had one fellow in IT and they just got teams and he decided to set up a team for pretty much every team. So overnight there was 76 teams overnight with no consultation or what do they need or the naming convention or were there already shared mailbox and distribution lists with names? So then there was multiple names going on in the cal. Oh, look, it was just so yeah, I get the sprawl, but I mean, he did well by at least stopping the creation of them. This can be just a, even if it's just a, you get an app to just put a one step between creating going, do you need, is there one already created? An approval process, right? Just a one step approval process where people have to submit and there's somebody who clicks the approval button massively lowers the amount that are created. If that's all you do, you're going to, that's going to get you well on your way. Yeah, but the horses are already out of the, out of the gate, right? Yeah. You know, so let, I like to go back to my simple, you know, who needs to work together? What are they working on and how they get that work done and doing a matrix? So I create like a matrix of all the teams and then the people, depending on which one's wider, which one's tall and just say, who needs to work together? When you start seeing consistency, that should have been a team. And then what, what were they working on those become the channels of the team instead of having one team for events and another team for, you know, um, you know, company events. Well, maybe that's different, but, and then if needed strategically add private channels for subgroups, if you need to, but strategically don't go crazy with private channels. That's my thing. Well, and that's a great point. It's not just about, you know, uh, like there are provisioning tools that are out there and I'll come back to that, but they're, you know, but that often doesn't help to answer this question of like, hey, I'm in the midst of it right now. How do I clean this up? But I would say that there are third party tools that are out there. This is a class of tools that have been built for by ISVs, partners out there, um, for teams, uh, to solve this problem so that there's a provisioning process in the front end. We can actually go and apply that and applies like a governance layer. Well, it will force all existing sites to then adhere to a review process. So then what happens is the owners of each of those sites after 30 days, 60 days, 90 days, whatever you assign have to go through and, and justify is it still active and what's still going on with it? Is it still necessary? And so it forces them to do some cleanup. Right. I've tackled it as well, Christian, from a, from a couple of ways with going into organizations because I'm dealing with the, you know, the end user and the business side and there's often already sprawl. I always go, well, how far into it are they? If you've got then some history of exactly that they're not using and, you know, who is in it. Um, training. I've gotten gone in and gone, you know, because often they've got them there, but they just don't know all they're really doing is having it for the files, but they just haven't got to the point where they're understanding how to work out loud in channel. So part of that is education. Are they going to use it? And I start to see them removing and consolidating and because the people that have created in the first place often just don't know what or why. So it comes down to an education piece to be able to do it. And then you've got the back end technical of here's the list and asking the organization and sending information out, um, uh, where we've done a sort of giving just a merged email. Whereas go, this is your team. This is what's going on. It's not being utilized. Do you need it and doing it that way as well where we've kind of tackled it from just a, just a generic sort of email going out sort of thing. You know, what do you need a way that education is usually the biggest, the biggest way to start turning it around. Yeah. Well, governance governance governance. Right from there. Yep. Well, and a lot of, you know, one of the things is, well, how do I organize it? And I, a lot of times we'll find out how, how does your organization group? Like, cause a lot of places group in different ways. So certain industries group by project, some group by department, some group by teams, right? So like there's a natural order in most companies about how they group people like Sherry was saying, grouping people who work together on the same thing. And how they work together. Not how their org chart is. Right. Or chart is different than how they work. It's how they work day to day. Do you work in projects? Do you work in departments? Do you work in teams? Do you work in committees, right? Those typically tend to make very, very good team choices. And then like you were saying, just kind of pull them in from some of those disparate teams and maybe get rid of those older ones. Making my channel, but the hard part is you can't move the content. You can't move the conversations that already exist. So yes, you can. You can now. You can migrate them. Yes, you can. Oh, the sessions. Yeah, you can migrate conversations. You can migrate chats. You can migrate content. I've been doing it for clients for the last couple months. So my understanding is only content. So I'm happy. Okay. Yeah, yeah, yeah, we need to talk. We need to talk.