ADKAR for BIM: Making Change Management Work for Standards

Josh Kennedy: We'll be talking today about ADKAR for BIM. So change management, basically, when it comes to Revit, when it comes to BIM, and when it comes to Guardian. If you're not familiar with ADKAR, and I'd actually even be curious if anyone wanted to use the little raise hand thing if they are familiar with ADKAR.

You know, personally, I wasn't as much. Allison's used it in a past life as a BIM manager, as a change management process. But yeah, just to kind of set the stage, basically, ADKAR is like an approach to change management. It extends past Guardian, past BIM, you know, just kind of regardless of the industry, it's just a way to help people be aware and kind of adopt change that's happening at the organization. And so we wanted to kind of ride that train and tie it back to kind of two sides of the coin, like how Guardian can basically help with the changes that you're trying to implement or standards, worksets, best practices in Revit. And then we'll talk a little bit too about like the change management that comes with implementing Guardian itself.

So kind of both sides of that are what we're going to touch on.

Presenting today, as I mentioned a minute ago, is myself. Quick introduction for me. I've been here at Guardian for 3 1/2, so going on four years here soon. It's been really fun. Before Guardian, I was at Unifi, the content management system,

before that got bought by Autodesk and turned into content catalog. That's where I heard about Guardian and the product team and some of the cool things they were building here. But it's been a really fun past few years for me. I'm based in Northern California. Allison, you want to introduce yourself?

Allison Hawes: Sure. Yeah, I'm Allison Hawes. I'm a product specialist here at Guardian. Before joining here, actually, this is my one year anniversary month. I was with a couple local firms in Denver, Colorado. Started out as a baby intern architect, worked my way up to PA, and then made the switch to BIM manager, after I realized I loved Revit, I loved training. So I'm extremely excited to be talking about ADKAR and how Guardian can help with that. And before we move on, I did embed some sneaky links in here. So if you click on our pictures, it'll actually take you to our LinkedIn profiles. It should.

Josh Kennedy: I don't even think I knew that that was there. You probably told me before, but I like this presenting in Teams, which is maybe like a bonus feature or something we'll throw in here. I mentioned this to a few firms recently as I've been talking with them. And yeah, if you open up PowerPoint, there's actually a Present in Teams button, like when you're in a Teams call.

You open up PowerPoint, you hit the present in Teams button directly within PowerPoint, and you get all this cool stuff. You get a laser pointer, you can draw on the screen, you can have some fun. So Allison is full of tips and tricks that help with training.

I think a lot of the people I was looking through, you know, who'd registered for this specific webinar, I think there's a fair amount of people who might not be super familiar with Guardian. We're not going to really talk a lot about Guardian and the settings and things like that today. We're really talking about change management and some of the ways that Guardian assists.

but more from a kind of idea standpoint, I guess. So for those that aren't kind of familiar with Guardian, I really have like just two or three slides that talk about what we do to make sure that you have a good kind of foundational understanding. So we as a company have been around since 2018. It's been...

especially fun the past few years is we've really grown in popularity. I get the kind of benefit of telling people about Guardian for the first time every day. And it's really fun. It's a tool that a lot of people are like, I wish I had this like a year ago or two years ago. So we've grown A lot. We've added hundreds of firms over the past few years. Nowadays, you're working with close to 500 firms, across 25+ countries. We work with firms that have just a couple of employees and people in Revit to people that have firms that have thousands of employees in Revit. So really fun and exciting to see to work with the partners that we're working with.

Kind of why we exist in the 1st place starts with one, it started with Parley, our founder and CEO. He's a former BIM manager, kind of been in the trenches, been

fighting the fires, training people, maybe reiterating some training best practices. So today we've built our team to about 20 folks now, I think just over that. Most of our teams from the industry, people who have been directors of design technology, architects, engineers, BIM managers,

So we understand kind of what happens day-to-day in Revit, and we've tried to build a software to really help you be proactive and avoid the setbacks and the pitfalls and automate as much of the standards and consistency as we can with technology today.

How we do that from a really high level and how firms really implement Guardian is everything out-of-the-box is in a monitor mode. Firms typically deploy Guardian to their entire team. Day one, users, nothing changes for them. They don't log into the software. They continue working in Revit as they were the day before.

Guardian captures a bunch of information that can be really insightful into like model performance as well as like user trends. Like how are people using Revit? What are they hiding, copying, deleting? Where are they getting their content from?

And tying that together with which models are performing well and aren't can be really insightful. And that's usually where we start. First few weeks, we kind of monitor, see where the low-hanging fruit is, see what's happening that you might not be aware of. And then we help firms kind of customize the settings of Guardian that could be around automating your worksets. So regardless of the active workset, things are always placed where they should be.

It could be having Guardian clean your content. So line styles, old text types, values and parameters are all being mapped to your true standard while people work. There's no cleanup to be done. And then whatever else you have as far as best practices, you know, not hiding certain things, not moving completed work, all these things that people can do natively in Revit.

We help with some real-time training. So we help you get all that set up. And then really the beauty of Guardian is you basically teach it your standard. It runs on autopilot and just avoiding those setbacks, letting you focus on bigger picture kind of initiatives, letting your team focus on what they got in the industry to do, which is design cool spaces.

not to fight Revit and create support tickets and all those things. So that's just a little bit about us, kind of what we do, why we do it, how it happens.kkkk

But moving into ADKAR, I've got a couple more slides here, and then I'll pass it over to you, Allison. If you're not familiar with ADKAR, it's an acronym. Again, it's a change management kind of methodology. And it starts with the awareness, right? Making sure people understand kind of why change is needed.

And then helping with the desire. So creating that kind of willingness to change, educating people on how they can make an impact. And then the ability comes into giving the tools, right? Guardian can help with a lot of these things that we'll talk about, but giving the tools to actually make a difference, right? We're implementing these changes, these new standards, whatever it might be.

and then reinforcing that. You'll see that wheel up on the top right of the screen. It's kind of intentionally a wheel. That's because this is kind of ever changing, ever evolving, right? Standards change, best practices change. You jump to a new project. That client might have their own standards. So kind of go back to the awareness and continue kind of reinforcing these things that we're talking about.

What breaks with ADKAR? So some of the things that can typically go wrong.

Users might not know, like why standards exist or why they matter. I get to hear that all the time. People exploding CAD, importing CAD, didn't know that I shouldn't, didn't know why I shouldn't, right? So being able to kind of bring that awareness, not just once, but kind of constantly as people are working, so they're learning day in and day out.

And then the desire. I think this is a big one, right? This is the way it's always been done, or this is the way I've always done it, or this is how I did it at my last firm. We get to hear it all every day. I'm sure some of those things probably aren't foreign to many of you. But getting the buy-in, right, helping educate on and

convert people to getting bought into the process. We're all kind of trying to row together here towards a common goal of delivering a quality project efficiently.

The knowledge, right, as far as what breaks, right? Training happens, you know, early on when someone gets onboarded or early on in a project, right? It actually comes into practice months later sometimes. So being able to give that like just in time training, just in time information can go a really long way towards making sure that what was talked about.

In the past, it's actually happening.

And then the ability, right, giving the tools, giving the nudge at the proper times to make sure that people can do the things that we're asking them to do.

And then reinforcing, right? Being able to kind of see what's happening across the projects can really help in understanding, like, where does the team need additional training? Where can we revisit? What automations or protections can we turn on for these projects?

So how Guardian can help with some of these different areas here. When it comes to awareness, Guardian brings all these things to light, right? It shows kind of what's going on.

When it comes to the desire, you can earn buy-in by giving your team some tools that help reduce the friction that they're having in Revit, right? You can, you know, workset automation, sync traffic control. There's a handful of things that we'll talk about today that can really get buy-in and help people get behind the changes you're making for your standards.

When it comes to the knowledge, Guardian’s helping deliver that kind of intercepting, you know, this type of action is critical. We want to get them important information when they need it.

and the ability of giving those tools so that they can execute on these things. And then the reinforcement, again, kind of getting that just in time training, but being able to adjust the frequency. So if it's something they do, you know, once or twice a month or once or twice a year, at the next time they go to do that action, they're seeing those best practices, kind of being reminded of, you know, naming conventions or how they should be.

Going at these things.

So to kind of simplify all of that and hand it over to Allison.

You want to see it, we want to help them want it, learn it, give them the ability to do it, and then keep it going with the reinforcement.

But Allison is going to dive into these in a lot more detail here, so.

Take it away, Allison.

Allison Hawes: All right, I'm taking control of your screen. Make sure that works.

All right. So like Josh said, the little wheel at the top right will let you know kind of what letter we're on. And we'll break down within each letter kind of what those three breaks are within what ADKAR is. So for awareness, why change is needed. The first is blind spots - drift across the firm stays mostly invisible. The cost isn't quantifiable. Systemic patterns can be really hard to track. And if you implement change with no warning, a new expectation shows up with no explanation of why, there's going to be confusion and there's going to be resistance.

So to start, you know, if each user is only seeing their own file, they don't see that drift that starts to happen across the firm. This is our Power BI template. We're looking at our family loading. Oh, let me use, there, we'll use the laser. The family loading tab here, this has been edited for clarity purposes, but this is something that I saw on my own projects. One team was using 09 - Gypsum Wallboard as a detail item. The next was 09 - Gyp Wall board, separated. We had Gypsum board, we had Drywall, we had gyp bd lowercase. And so users didn't know what the standard was.

And as the BIM manager, I don't know what the standard was either because I couldn't just update one because I had all these others floating around. So basically what the Power BI, what the data is doing is bringing awareness to the invisible.

For the next tab, we'll focus on the syncs here, and you can see there's quite a bit of data. But what we're going to focus on are the sync conflicts. So I think everyone kind of has a feeling that sync conflicts happen, but it just feels like maybe a bad day. Maybe you let your BIM manager, you hear as a BIM manager, of one or two sync conflicts, but then when you start to actually track it, that number ends up being so much more because maybe it wasn't brought to anyone's attention right off the bat. So we get that actual data, we get the actual numbers, and then we can start to see how frequently they happen, during what period of time, how many minutes of work have been lost to this. And so from here, we can then hopefully start to see this number go up. These are all the conflicts that have been avoided when we turn on the sync traffic control within Guardian. And we don't have those sync conflicts anymore. So it starts to help plug in some actual numbers. Speaking of

clickable links. I do have our ROI calculator down here so you can start to see where Guardian could help save some money here.

Change with no warning. Actually, I was just on a call earlier today where Guardian was implemented at the firm with no awareness before things were turned on. So end users were kind of caught off guard and it did kind of leave a bad taste in their mouths. So that's not what we want here at Guardian. We want to provide all the resources that you could ever want to let your end users know what Guardian is, what's coming, how it can help. We've got e-mail bulletins, PowerPoint slides, video, all sorts of things. We've even joined firms and we've done the presentation of what Guardian is. So we don't want to your end users to all of a sudden one day have change because that will lead to confusion and resistance. So yeah, Guardian provides all those resources to make sure there is warning of what's coming.

All right, desire, the willingness to change. Status quo resistance, kind of playing off that last slide. So new tools will disrupt routine, the reflexes to resist first. My favorite phrase ever, it's always been done this way or don't fix what ain't broke. We'll address that. And then will confront the elephant in the room with the big brother fear. If you're not aware, elephant that you see here is Peanut, our mascot. But Sanders can feel like surveillance or overhead, so we'll address that as well.

All right, for status quo resistance, so if new tools disrupt routine and the reflex is going to be to resist, let's focus on fixing things that people are already struggling with. So what we're seeing here is at the beginning, I'm in the core and shell active workset. I'm copying this grid, but I could place a new grid.

The point is, they have to be on the levels and grids work set, not core and shell. And as you can see, with Guardian, that happens automatically. So if something new comes about and people want to retract from adopting it, it's easier for the desire to follow the win instead of preceding it.

if we're not trying to argue someone into wanting change before they felt the benefit.

It's always been done this way. So in this example, our project central in Revit dashboard lets us see how many in-place families are in these models. And I can see these generic models, the main dining pendant light. Why? You can see it's a very simple family. It'd be very easy to make as a family and then copy around your project, but it's been modeled in place. And this is a pretty light example, but I've seen projects where it's three stories, multiple facades, and there's some sort of complex, you know, window awning element or something. And I understand why it was modeled in place at the beginning of a project. They're trying to get renderings out the door. It's much easier to just model in place quickly, make it look pretty. But then down the road, we get to CDs and these in-place families cause so many problems. You try to update a dimension, a material, whatever.

It just creates more work when you already have a ton of other deadlines you need to focus on. So this has always been done this way. With Guardian, you can either start to guide or prevent the modeling in place right from the get go, or it helps you decide to build into your budget sometime, maybe between SD and DD of

Okay, we modeled in place for renderings. Now let's go through. We can very clearly see what was modeled in place, what we need to turn to a family, so that by the time CDs come around, you don't have this issue kind of hanging over the entire project.

Okay, Big Brother fear. We have heard that Guardian is Big Brother. But we say Guardian is a training opportunity. And really where this is, the best use case for me is the import CAD versus link CAD. So I don't think that people are maliciously doing import CAD.

I think it's as simple as they either don't know that link CAD exists or they don't know the importance of linking CAD. And so this is something I've said, if you're a BIM manager, you've probably said it a million times, please don't import CAD, only link. But before Guardian, you really couldn't do anything about that.

So this is something that we can get in front of. Maybe we want to prevent it. So this is something that your users start to see. It will pop up when they use the incorrect command. But it's not just getting in the way of their workflow. The text is small here, but we've got recommended workflow. So it tells you instead of import,

go to link. Maybe a did you know, a quick blurb on why we don't want to import. We can even link to, you know, external websites, internal learning management systems, anything that gets that message across. So we really don't want this to be like a gotcha. I talked to someone at AU that she saw this more as it's less of a slap on the wrist for end users, but more she was made aware of the gaps in her training and she could see where more help was needed.

All right, moving into knowledge, how to change. So rollout goals could be vague. If you've got a lot of specific behaviors you want to fix, you kind of don't know where to start if you've got quite a few. Having nothing to teach yet. If you don't have a standard that's written down or it's hard to find, you can't teach toward it.

And like Josh mentioned, you know, if training happens once or early, it's really hard for that to survive when a deadline comes around.

So for the rollout goals are vague. That is exactly why we've got a really robust onboarding program. Another clickable link here that goes to our onboarding website. So if you'd like more information on it. But essentially, we start with just gathering insights. So that Power BI dashboard that we were looking at earlier,

That's your data. We start to see how your users are working in Revit. And from that, we start to develop education and risk avoidance. If you've got a ton of things that need to be changed, this helps us narrow that focus. We'll start with just a handful of items. We'll start with the low hanging fruit, we'll move on to the apples here, the low hanging fruit, the easy wins, you know, curating standards and automations. This is where we can start to set up the work set rules. So those grids and levels go to the correct work set right away. So we work with you to make sure your goals are not vague, but very specific and easily attainable.

And then we review and optimize with you. So we don't want you to get Guardian and just say, okay, good luck. We'll check in with you throughout the year, start to see what other tools. You know, Guardian has a ton of different options and it's hard to get through them all in onboarding. So let's go through it in a couple months, see where else we could turn things on.

So really, we really want to help you maximize your investment and make sure that Guardian is implemented.

Nothing to teach yet. So I've heard quite a bit. I don't have standards yet, so I can't get Revit. I'm sorry, I can't get Guardian. And that's where Guardian actually helps is with getting your standards rolled out. So our model properties here, we start to see everything that's in your file, and we'll start to focus on just line styles here.

So we can see there's a 7 and a 7 - ultra heavy. Sorry, it's really small on my screen. They're literally the exact same line style. That's what this duplicates column is showing us. We don't need two things named differently that are the same. So let's remove those duplicates.

Now we can start to see this contract limit line style is not used. This contract limit line is used one time. So let's get rid of the one that isn't and keep the one that is. So we can go through that. If we do this for all of line styles, before you know it, it's standardized. And now we can move on to a different tab and do the same process there.

So what we see this is a very incremental process. It's starting to define your standards. It's using the properties that are in your files, and it's just taking small bites at a time. We don't expect you to do all the standards all at once.

Here's Peanut. He's our little mascot that comes kind of default with these messages, but these are fully customizable. You can swap him out for whatever else, but essentially what this command message is doing is training in the moment. So my example is I would give firmwide trainings and I would get great feedback and also be straight up told this isn't applicable and I'm never going to remember it. And that was fair. If you're not needing what I'm training you on in the moment and you're not doing it constantly, you're not going to remember months or a year down the road when you actually do need to know. This is something that we've seen a lot too, you know, loading families from not content catalog or whatever your content management system is, that can cause problems. And so we can set up this command message that does give the information of why you're seeing it and what you could do to do things the correct way.

All right, ability practicing the change. So manual cleanup is the bottleneck. If you only have one person or a small group of people hand fixing every non-standard element that doesn't scale and it's not sustainable, I have been there. BIM managers lacking the time. Building standards compete with everything else on their plate. I've also been here. You're drowning in tickets, helping people build families or figure out why something is not visible. Standards take a back burner and at that point it's really hard to move anything forward.

And it's easy to forget the steps. So maybe you do know what the standard is, but you're in the moment, you're trying to get a deadline out the door. It's easy to forget what the best practice is.

So for this manual cleanup, we're looking at our incoming properties dialog, and this is what admin would see when content is loaded into a family. These are all the properties that are coming with the content. And because this list is so long, I'm going to say maybe a manufacturer website is the source of this. But

We're just going to focus on the line patterns. So from this list, now I can start to see what I don't want to bring into my file. I don't want beyond. I do want dash, dash, dot, dash, dot, dot, but I want that to be named to my company standard. I'll remove these as well, and the hidden is being named to my company standard. So I set these rules up.

And then Guardian learns it. So I don't have to repeat this every single time. Guardian knows and it's working with me as I start to load in more content. It remembers the rules that I've set up.

For BIM managers lacking the time, we'll focus on line styles again. So again, we had a bunch of duplicates here. We had some that were in use, some that were not. I see some capital letters here. I see a temp. You know, we want this all to be cleaned up and it's kind of overwhelming to start.

But today, I'm going to tackle it. I'm going to start setting up these mapping rules. I'm going to remove the things I don't need, make sure things are named the way I do want it, so that by the time I show up tomorrow, look at how pretty that list is. I love it. It's following my office standards. It looks nice. I don't have to worry about users you know, grabbing the wrong line style. And because I've set up these rules, if temp comes back in, whatever I set here, that's what Guardian remembers. So it's not going to re-enter the relics of the past won't haunt you. Oh, that's pretty good for October.

I didn't make that connection till just now. We don't want to haunt you.

Josh Kennedy: I like it. If I could, I'd just...

Allison Hawes: Thank you, Josh. Thanks for laughing with me.

Josh Kennedy: Yeah, no, I was just gonna quickly add, yeah, we're kind of we're showing a lot of what you know, we work with like the admin of Guardian to do some of this cleanup, and I really like your point, like it might be line styles this week, even for firms that are like in the process of, you know, rolling out new templates or rolling out new standards, right? It might not be everything all at once, but...

This week, let's do line styles.

The end users, really, they're just beneficiaries of like a lot of these tools, right? Like, so just to kind of emphasize that, like temp that you talked about, or you know, any of these things, E dash light, the next time the user kind of brings that in, Guardian just silently in the background is monitoring those transactions, so it's not interrupting your users to automate all this cleanup. So to your point, like somebody goes to an old project, they go to their secret stash on their machine or wherever they might be getting this content from, it's getting cleaned up on the way. And I think that's a big part of the ability to kind of make an impact with some of this change.

Allison Hawes: Yeah, that's a great point. I'm showing kind of how the admins can help with the ability, but you're right, the end users benefit from that as well. It makes their ability a lot easier.

Easy to forget the step. I mean, this is an end user use case, I would say. So, you know, going to create a new sheet, you know, you got to add that sheet name and number, but I would see people forget to fill out these parameters that organizes it in the project browser. And so you have a ton of things under your three question marks.

And I would get requests from users complaining about their models because messy, they couldn't find anything. Nothing was where it was supposed to be. So rather than ask them, okay, remember, every time you create a new sheet, you have to fill out these couple parameters. Guardian can help be like that in the moment training.

It's not really training, but just like helping you remember that step. So everything stays organized. Everything stays easy to find. And it's something that makes the bim managers happy as well as the end users.

Bonus, we've got chicken and egg deployment here, so you can't get buy-in without data. You can't get data without buy-in. Josh, I'm going to hand this over to you.

Josh Kennedy: Sure, sure. Yeah, I was surprised a little bit by the chicken and the egg. I wasn't expecting it so soon. No, you're good. Yeah, you can't get buy-in without data. You can't get data without buy-in. Yeah, this is a really cool part of Guardian. It's one of my favorite parts about working here is that the product team has designed this to be like the silent deployment that I kind of talked a little bit about early on. And so me and my team, what we do a lot of is helping people evaluate the tool for the first time, right?

Taking a look at it, doing a demo, doing a team demo. And a lot of times what makes a really easy case is if you can kind of build the case, see your data, not just Guardian's website and kind of what we claim, but see this all in action. And so we help firms basically deploy this with a 30-day free trial.

Guardian can start monitoring silently, give you all the information you might need, right? How often are people hiding, copying? What are they deleting? What are they hiding, right? All this information without kind of making the commitment quite yet. And then I see a lot of firms use that information to like build the case, to get the buy in.

And then really the beauty of that is we're kind of ahead of the curve. And it almost doesn't make sense to say ahead of the curve, because we're kind of like moving the curve, I guess, in a way, because most firms that are implementing Guardian have taken advantage of that. And so we have this like leg up. We head into onboarding, and we know exactly what we're going to tackle first, second, and third.

because we've been monitoring what's going on for the past three or four weeks. So yeah, it is really kind of like both at the same time, if you will.

Allison Hawes: Yeah. It's hard to need proof of the need before purchasing a new product, but you need the product to prove the need. So yeah, we do hope the trial is kind of that happy medium there.

All right, moving into reinforcement, the last letter of ADKAR, sustaining the change. So compliance will fade without feedback. If nobody sees that backslide, nothing will correct it. Or maybe there's too few of champions. If reinforcement rests on only a few people, it won't hold.

as well as too much too fast. Aggressive enforcement will burn the goodwill that is needed to make this last.

So just like at the beginning of the slides here, looking at the data to kind of help you understand what to turn on or off, we can also start to check that throughout the process of just seeing where things are. I don't know if it's easy to see, it's kind of small on my side, but override Graphics

by element. The 2 colors, the light blue is showing how many times that's not happened, and the dark blue is showing how many times that still happens. And so from there, maybe we were just in that monitor mode, just collecting that information. And now we know maybe we need to turn this on to a guide or a prevent, start to get in front of the users and train them.

We don't want you overriding graphics in element or by element. And maybe we have that guide going for a while, and it happens every single time someone tries to override graphics by element. Maybe we continuously start to see the data within our backstage that maybe we can ease off. Maybe we just do it once a week.

And then we continue to check the backstage. Uh-oh, those old habits are creeping back. People are starting to do it again. Okay, maybe we need to make it in every time. So like Josh had said earlier, this is always evolving. This is always being updated, and it's based on your information. So we don't want the drift to keep.

happening over time. And without this feedback loop, you would kind of miss out on seeing when things would start to slip.

Oh no, okay, pretend you didn't see that. So for the too few champions, we'll get to that in just a second, but where this came from was a new firm that had purchased Guardian. I loved how they wanted to do this instead of it being kind of top down of here's what's coming.

It was, let's vote together on, we want people to get our families from the right place. We don't want them copying from old projects. We don't want them going to their secret stash. So let's vote on what meme we want to have. They got rid of peanut, but what meme do we want in the message? So,

These are three. You can select them from our meme pack here online. We've got quite a few pretty good ones. But Megan, if you have that poll, I'm curious, if we were a firm together, what would we want as our meme for getting content from the incorrect location, one, two, or three. I can't pick. They're all my favorite.

Josh, you have a preference?

Josh Kennedy: Oh, I was trying to move the poll so I could see the middle one better.

Allison Hawes: They're all good, I think. And I think, did Jake create all these? These are all...

Josh Kennedy: I know. I think #2, Jake might be the creator of all of these ones. Yeah. I've submitted my own vote, so I'm curious.

Allison Hawes: Do you like that? Yeah.

We love seeing, okay, perfect. Yeah, we love seeing what people come up with. So please share if you have a good meme, if you get Guardian and start to use your own. We love seeing it. I think that's probably enough time if we can see the results. Curious what we voted on.

Josh Kennedy: I can see it in the chat. It looks like #2 is the winner right now, but we're getting good votes on all of them. Yeah, we had this when I started years ago, and it's been added to slowly over time. We have a meme starter pack.

Allison Hawes: Oh, can you? I turned the chat off.

Okay. Okay.

It's still going.

Josh Kennedy: If you really like the meme approach, you can download it from our downloads page. AI characters, you know, we see people have a lot of fun and like introduce whatever their culture is into these kind of messages to break the ice and make this kind of training, you know, more fun.

Allison Hawes: Yep.

Yeah, and I do like that it's kind of a group effort. So everyone feels like they had a hand in this. It's not just, hey, we're not letting you do something. It's okay, we all voted on this together. Maybe it's not the one that you wanted, but it's more of a group effort.

Alright, I think #2 is the winner.

Um, alright.

So for the too much too fast, that is something that we don't want to happen. So we have what we call growing into Guardian. So we start from that, getting the data, then we start to develop into the education and risk avoidance, then we can turn on the standards and automation. So we don't expect you to dive in right away and turn a bunch of things on. We want to help you grow into it so it's successful. This is your tool. These are your standards. We're just here to help you implement them.

So that is Guardian and ADKAR as one last clickable link. If you didn't click on any of the others, this will take you to our home screen.