 Richard has a question about user adoption. So buckle up everybody. It's going to be right here. What are the biggest challenges your end users face when starting with Microsoft 365? So Richard likes the bold big topics, apparently. We're starting at a 10,000 foot level, not at a 1,000 foot level. Right. Anybody want to begin? Oh, I could begin, but I don't know if I'd ever stop. So you all just tell me when to stop. One is proper training. That's the thing that everybody thinks, yes, most of the applications and things you do are very intuitive. Or they've done it before. They've always used mail or they've always used this. Things are different. They work differently. There's new functionality, things that are built in that weren't there before. So training is a must. Also communication to them. So there's a lot of... I'm just going to use the word attitude maybe for users. The more they feel communicated with on what's going on, when it's going on, they embrace it a lot more. When things are shoved on them and they're told, they tend to not be as receptive to the change, right? And so making sure that you're communicating and getting feedback from them on things. It is always very key to one, ask for feedback, but then two, let them know you're actually listening. Two different things, right? So go solicit that feedback, let them know you've listened, prove it that you're listening to them. Hey Stacy, I'd like to say that one of the things kind of ties into both of these is... So years ago, one of the reasons why I started doing, initially with SharePoint, I had a session, some folks watching might be aware of this. It used to be like 10 features that you've never used and it started in SharePoint that you didn't know about, or features you've never used but should. And I haven't looked in a couple of years now, but at one point over a half a million views of just that slide deck, which is very popular there. But I got into the productivity tips because you have so many people that are familiar with, of course, the Office Suite and they're somewhat familiar with Teams and maybe SharePoint and OneDrive and the other tools, the other solutions that are out there. But they're not familiar with the latest. They're not familiar with all the integrations around that. So with the productivity tips, that's why I love that category of content in general, like from other MVPs and experts that are out there is because nine times out of 10, I've seen it before, I've used it before, but then there's that 10th one where like, wow, I didn't know that it did that. I didn't know it worked like that. That's how often the end user training is. People are bored to tears, they're going through the basics, things that like, I know this stuff, I know this stuff. Whoa, wait a second. I had no idea that I could do that, that it worked like that. And that happens to everybody in those sessions. So this is exactly why my presentation QuickWinds came about, right? QuickWinds, because people like, but they didn't know how to use it, what they could do with it, or these little caveats, right? I've had people in like my one hour QuickWinds session say that five minutes that you just showed me that, paid for my entire trip to this event, right? Because it made them more efficient, they were able to get more done. So and the cool thing is, is that presentation, I've given it so many times, I bet you over 200 times, right? Because it's constantly changing, because the technology keeps changing and new things keep coming out, right? You know, I've been working on a, literally a workshop, it's Microsoft 365 A to Z, which goes through the different apps and how you could use them within your organization and stuff like that. Well, what did you put down for Q? Actually for the Q slide is literally some like QuickWinds type of stuff, littler things. So yeah, but thank you, because it took me a while to figure out what the heck I was going to do for Q, but thank you. So what I want to say about this is looking at it from an aspect of not only educating the users, which I took a little different approach when I was doing some 365 migrations. I did a, I went and talked to people and found out what the problems that they have currently and tried to match them up with the solutions that 365 gave. And then I would show them that, hey, the problem that you have over here doesn't exist over here or the problem you had over here, you can work around it with this in 365. And that they became more receptive at that point of that transition. But I will say that there are so many variables in this question because number one, it says starting with Microsoft 365, where are they coming from? What environment are they actually coming from? Are they coming from an environment that's all Google apps? Are they coming from an environment that is like prehistoric and they're still using Lotus Notes and things like that? Which is the file share, right? Yeah, or they're just using a file share and they're using basic spreadsheets for everything. It all depends on the situation. And each one is unique. So when you say the biggest challenge is really the biggest challenge is identifying what they currently have and use and how they use it and matching it to what they can be doing, could be doing and should be doing in 365. That to me was the hardest part because it's not a one for one. Usually it's not. Usually it's not as simple as, oh, you're going from Google Docs to Microsoft Word. It's not that simple, okay? The two don't look alike. They don't work alike. They don't anything alike. That's like the features. That's like the user experience, the interface itself. Then there's, and Mike, before we restart recording, you mentioned this too is the migration of the data. Being able to, your adoption could be tied to whether you can find your content. So it's not just moving from that other location, those other environments, all of your data over there, but it's also then how you reorganize that content within the new system. So if it is different. Is it going from Google Drive into OneDrive? Is it going into, or are you going to introduce your users to SharePoint? We're going to move everything from Google Drive into SharePoint and going from Google Drive to SharePoint is a huge jump, huge jump. Going from Google Drive to OneDrive, not so much because it's just file shares, right? Not a big deal. But the thing about it is, is that there are nuances between all of them. I'm just using the Google Apps as an example, but realistically, I had a company that not only a year ago was still using Lotus Notes. That's why I brought that up. They're still using Lotus applications because they're strictly an IBM shop. That's it. Everything was IBM. So to try and match that up was like matching up a dinosaur kind of application to something that is off the bottom. A fighter jet. Yeah, it's crazy. So I was actually going to bring up that exact same example. So I've worked with dozens of companies that were Lotus Notes companies and moving over to the Microsoft stack. And one of the clients in very large financial services company, it was being driven kind of top down. The new CIO said we're going to Microsoft technology forcing the org and they had a lot of problems because people hadn't bought into that. So big part of it was they didn't take the time to really get the buy-in from the organization of the value of why we're moving, what it'll bring us. So they hadn't sold people on that. Like you need to have some degree of buy-in from the organization. Do that feature mapping. Show how things move across, how you move the data. Now, I was going to bring up another point that from the migration standpoint of all that content. Lotus Notes works very different. It's different functionality. This is just one example for a user adoption there. But what it was, the learning from a user adoption standpoint was that there's only so much that you can automate with tools to move on the back end that there has to be a strategy that is user driven to train people on the new features. They know where their old content is and it's almost, you can spend all the time trying to move it on the back end and make it all line up and map it the exact same way and tag things properly. Or you can train users on, hey, here's the new system. Give them time to do it, say within the next 60 days and then they go move their content. They do that. And they know where it is. They know where it is. So funny how when you ask the people who own the content to manage their content, how things get put in the right places or they recognize that I no longer need this content. So that's where training becomes important, right? I mean, you train them because take, I mean, so a situation I'm in right now, like file share, everybody knows there's no organization in a file share, there's four copies of everything and all this kind of stuff. And they don't have views and all this kind of stuff. You train them and then you just show them examples, right? Examples of how their content can look in SharePoint so they can find it easier, all that kind of stuff. And they're sold, right? But you got to show them first. The other thing that I do is when I talk about the app, the mapping that Mike was referring to, is I find the things that they should start with because that's what they're using right now. And I turn all the other apps off so that they can focus on their current needs. And once that's then, as the company's deciding, okay, now we want to introduce these apps and then these and then do the training as you go on because you give them too many apps all at once, content is going to be everywhere and everybody's going to be doing it differently. Yeah. Funny how that happens. I know. You got anything, Hal? From my end of it, it's not so much Lotus Notes and things like that. The stuff that I've dealt with has always been small businesses and people who start off using Outlook.com or as we were discussing earlier, they get a family, an Office 365 family, which is basically again is Outlook.com with you, you throw in some of the Microsoft productivity applications. And in those cases, if you're moving, it's even a little bit more difficult there because if you're when you're moving from that area to full Office 365, they already have substantial familiarity with email and Word and Excel and things like that, but they aren't even close to understanding the differences between the two systems and the advantages and the extras and the other bounty brony points and stuff you can do that you couldn't do. Yeah. And that can be really confusing. Well, yeah, I've used this site, I've used Outlook forever and in Yata and so on. And why doesn't it? Well, it doesn't work here because it's a different place. And you've got different features and different functionality. It's the same, most of it is the same granted, but you've got different things in different places. And well, you've got it on the web. You've got it on your desktop. You've got it on your phone. A lot of that you couldn't do with the situation that it was. And there's a, in this case, not only do you have to learn, but you have to unlearn first. Yeah. Well, I was just thinking of how practically how we've handled this in the past. So as much training upfront, you get that structured, you get that in place, you let people know, hey, here's what we'll be going through with all the materials. Also, as those questions come in, and a lot of the questions are that mapping between the old and the new. And people ask those questions. You may not have it properly documented. The new system may not handle it the same way or handle it at all. Whatever that is, have detailed FAQs that are searchable that people can get through. Then on top of all that, one of the best tools in larger organizations, this goes back to my experience in the 90s, working for the phone company, was doing the Friday lunch and learns where you had users that had done the mapping themselves, and then they say, here's what I did and here's how I dealt with this change and this is what I learned about it and sharing that. And that was, and we had those, a couple, few companies, three companies that I worked for over the 30 years that did it on a regular, almost weekly basis, had the lunch and learns. And so people go in and they state like, here's the business problem trying to solve. And we had some people that, I just like, no one's gonna show up to that. Everybody knows how to do that. The room is packed. Like everybody has those same questions. So you can't, managing all this, assume that you know what questions people are going to bring. Document FAQs, have the lunch and learns around that and then modify your ongoing training. So you can learn from the people that have been trained, what else you need to add to the people that have not yet been trained.