 Douglas says, we're looking for ways to help my company get more social and to help people to work more closely together. We've never used Yammer as a company, but now with Viva Engage, we're wondering if this is the right route for us. But do we need Yammer? That's a great question about engagement. Why would we need Yammer if our organization uses Engage? I think that there's still a lot of confusion around the name change with Yammer Engage coming in on the team side of it compared to the back-end Yammer. Ultimately, it's one and the same. Yammer is Engage and Engage is Yammer, so you need one to have the other, so you can have it on but not necessarily go into Yammer. You can just do it from the interface of Engage, but there is that little bit of a mismatch at the moment when it comes to what that looks like. I mean, there's going to be the Engage, and then you've got the paid side of anything across Viva as well, which can take these things to another level, but it's one and the same. You need one lit up to be able to use the other ultimately. Yeah. I love the fact that all the organizations that we're not a Yammer shop, and we won't use Yammer and turn that on, it's like when they're interested in Engage, it's like, yeah, it's again, it's the palm olive moment, so it's the same thing. Your hand is soaking in it. Sorry, I'm dating myself from an old 70s, 80s television commercials. Yeah. Look, I think Yammer, the name Yammer also, there's been a lot that has some past history around it that they don't want to use Yammer, but I think the naming is ultimately a little clever. They're going with the Engage name and coming at it from a bit of a different perspective, which I think is in Microsoft's best interest to kind of step away from some of that previous negativities that have been there around some of the Yammer name, but it's also being very positive. I've seen it coming from both sides and those that are really positive are struggling with the fact that it's going to Engage and all the rebranding. Yeah. Well, also too, it's having a, so there's other products that are also doing well because of their integrations in with team and people teams, people want to have that functionality. They want it in context with everything else they're doing within teams and Yammer, I mean with the, when it was the community's app, so the Yammer's community app added into teams and Yammer started growing again, I mean rapidly. And so it was one of the faster growing again products and people don't aren't aware that it was growing as quick as it was or it still is. And so yeah, with the rebrand refocus on that, you have like those core contextual experiences right there within the Engage app there right there on your left rail. So I've got it pinned, I'm often, I'll get the notifications, I'll jump into that with some of the new functionality like the storyline capability, the ability now to do videos and other images and add things like you would, it is very Facebook like, like why would an organization want that? Well, sometimes like I'm a member of dozens of different projects. And so there are teams for it, there are SharePoint sites underneath that, there's lists and libraries and kind of all those things. There's a lot of things that I do within the community that are not tied to any of my projects. So there's not a team for that. So there's, this is just one example, one scenario of why being more social and why Engage and Yammer are so helpful. But now you have the ability to go in and do on your storyline, I can add things in. Like I just, hey, I did this speaking piece at this community event. I was, my user group did this or I did a blog post on this topic, not tied to a project. I can go post that to my profile, tag it in different ways that people in projects that I'm not a member of can then find. It becomes, it surfaces that content, that activity or somebody six months from now may search on a topic and find a Christian shared that blog post that he wrote. And so they found it through that community because of the storyline activity. That's one of the powers of having an enterprise social network. That's why Facebook is, can be so powerful and all the ways that we mock it, but is, you know, and a lot of those social tools, but they're so powerful because we can share all of this unfiltered, disconnected content and ideas and images and videos and just all of this stuff. And it becomes relevant over time as people discover that as it surfaced in different scenarios based on how you're tagging it and groups that you're a member of. So it's incredibly powerful and I wish more organizations would go experiment with this. I think they find it much more powerful than they're thinking. There's always some confusion around why I use Yammer to Teams. And that just seems like it's coming up even this because of people have been using Teams as a cross business communication. But there's so many features that have come into Teams that have actually been designed and was created in Yammer. And that's where it's really powerful and strong for a cross organizational communication rather than a team to do communication. It's like, how do you break down those barriers? To some really good information that you're gonna find if you go to the adoption.microsoft.com site under the Yammer piece, there's actually best practice brainstorm. So there's a whole session, there's all these episodes that are fabulous, that so many great MVPs and organizations that have come together with Microsoft to run sessions. I would highly recommend going to the, literally the adoption site for Yammer to be able to get some more information around that, to be able to help make that decision because I know that for some organization trying to pull it apart a bit and understand some of those differences between if I use Teams or if I use Yammer or Yammer Engage, which is one and the same at this point. It's like why use one or the other and what do you wanna surface into Teams because it becomes your one place to go to do your work in Teams. So therefore Engage becomes a no brainer as far as I'm concerned when it comes to that community whether it's a social side of the community or it's hearing from leaders and be able to have two-way conversation. I mean an organization at the moment where they don't have something like Yammer or whatever it looks like they don't even have all of organization Teams or just anyway. So you've got really siloed organization and senior leadership that are just, it's one-way communication. It's not two-way communication. There's no way. No one is gonna email back the senior leader. So it's very difficult when it's all just very hierarchical. I bring up, I've mentioned this a few times but when back at the MVP summit a few years back when Teams was relatively new but they announced the org wide team. So do these massive teams and it was a full room of all MVPs and it was booze across the board and people were angry. Oh, that was 2008-ing wasn't it? I was there in 2008-ing. Yes, I remember. Why are you doing this? You're overlapping. Mike, you just think it's funny. The Teams people, they're like, oh, it's like, but they said it makes no sense. I get it, there's some large customers are asking for it but you were inserting into Teams, you're breaking the model. That is, you just described the, they wanna be able to communicate out to the entire company but that's what Yammer is primed for, for doing that. It's Teams, like you're, the way that it's supposed to work people is that your team is around the project. It's the people that are involved in and that work that needs to be done on a daily basis. Yammer and now Engage, it's for the broad company. Like, I don't know who might be interested in this. So it's like communities and of practitioners of, so we get together and like, we have a North America community within Yammer. We have a, you know, so it's, we have for each of our physical offices. So which are all of the North America offices. There's one for all of the global teams. There's musicians at Avpoint is another community. So we could go and post things to people of those circles of friends and contacts and share things within that context. There's also the all company community. So when our CEO wants to reach everybody, when we do the live streams of our monthly, all hands meetings, it's all done in that channel. That wouldn't belong over in Teams, which are customer related or initiative related or project related. And so that's the difference between those two. And then we also have our intranet. So that's, I'll separate it, you know intranet and then the teamwork in Teams and then the communities within Yammer now, now engage. And so it's just, it's a clear separation for us. They work together, they integrate. There's features that run across all of them, but give us a capability. I'm sorry, I know that I went off of Douglas's question, but. No, no, I look, you know, I don't disagree with you though, Christian. And I think that if they're gonna flip on and they're gonna use engage. Mike is looking disappointed, but I'm just gonna point that out. But if they're gonna use engage, they need to be really clear for the business, you know, what that comms plan looks like. What is it, what are you using that, you know, I'm gonna, we're gonna be using as an organization. This is how we're going to do it to drive it forward and making sure that you're not using Teams. And if you're already using Teams for a lot of that, does that componentry kind of shift or does it stay, what stays, what doesn't? So how have they been doing it in the past? It's all stuff they're gonna have to be really clear around their strategy and what goes, what goes where ultimately? And I think that's probably the biggest thing is if you're gonna line it up, be really clear for the business.