Latest / The ADHD Skills Lab / Why Your Team Hates New Softwares (And What to Do About It)
Transcript
- 0:00SPEAKER_01: I even know people who are like, the system shift is the reason I got fired.
- 0:03SPEAKER_01: So it's an emotional thing.
- 0:04SPEAKER_01: Whether people like it or not, you know, I've had people in my offices kind of tear up when it comes to talking about tasks and systems and project management.
- 0:12SPEAKER_01: There's six phases here that we're gonna go through to successfully shifting your team over to improved software.
- 0:18SPEAKER_01: Hello everybody, and welcome to today's episode of the ADHD Skills Lab.
- 0:22SPEAKER_01: I'm super excited to be talking to you today.
- 0:24SPEAKER_01: I'm joined by my husband Robert Waterson, and we're gonna be going over a little bit of what it takes to actually shift your team to a better software.
- 0:35SPEAKER_01: And the reason we're talking about this is one, we do this for companies as part of fractional COO role that we do for ADHD business owners, but also because I think in a world of AI and processes that are being updated all the time, this is a conversation that's been coming up a lot.
- 0:53SPEAKER_01: In fact, we were talking to somebody today who is coming back from a maternity leave and getting back into a business where she has to think about software risk compliance and all of those kinds of pieces.
- 1:08SPEAKER_01: And the shift, even in the last five months, maybe six months since she'd been back at work with AI.
- 1:17SPEAKER_00: Yeah, introducing.
- 1:18SPEAKER_01: It was making a huge difference.
- 1:20SPEAKER_01: So for a lot of people, this is gonna be a period of time where you have to think about your software and you have to start updating.
- 1:28SPEAKER_01: And that's gonna introduce a lot of struggles for a lot of people.
- 1:30SPEAKER_01: So we wanted to talk about it a little bit today.
- 1:33SPEAKER_01: And if you're thinking, wait, ADHD fractional COO, I think I could uh use some of that.
- 1:38SPEAKER_01: Um you can click the link down below and chat with me, and we can talk about whether you're a good fit for working with us and what that looks like as well.
- 1:45SPEAKER_01: There's six phases here that we're gonna go through to successfully shifting your team over to improved software.
- 1:51SPEAKER_01: The first one is buy-in.
- 1:53SPEAKER_01: And I think this is really important.
- 1:55SPEAKER_01: It's buy-in either for the team or buy-in from the business owner with ADHD, because sometimes this is a process the team wants to do and the owner isn't sure about it, or a system shifter that the owner wants to do and the team isn't sure about it.
- 2:11SPEAKER_00: Yeah, I think we've seen both.
- 2:13SPEAKER_00: Like I think often the team is a little gun shy about another software transition transition, and then also sometimes the owner is already overwhelmed and adding a complex system that's has the promise of simplifying things in theory, but you know, maybe they're not as tech savvy or I'd say we've had clients where the shift in systems has come from the business owner.
- 2:41SPEAKER_01: So we've had clients where the business owner wants to shift and the team are more reluctant.
- 2:48SPEAKER_00: Because we're dealing with ADHD business owners and often very excited about some new system that's gonna fix everything, you know.
- 2:54SPEAKER_01: And their team is often the ones who are like, we remember the summer of 2005.
- 2:59SPEAKER_01: It was hell, we barely survived.
- 3:02SPEAKER_01: Or they've worked in a different business.
- 3:04SPEAKER_01: Sometimes, you know, one of the things that I do is I'll em I'll interview the team as part of shifting and improving um their systems.
- 3:14SPEAKER_01: And sometimes the team will have stories of, well, I used to work in this kind of company.
- 3:21SPEAKER_01: And, you know, either they'll be like, We had that system, the same system we have now in the system in the company we had before, and it worked really well.
- 3:28SPEAKER_01: I just think people aren't using the system properly.
- 3:31SPEAKER_01: I hear that a lot, or we'll have situations where people say, We tried to shift systems before and it didn't work.
- 3:39SPEAKER_00: In fact, I was a nightmare we ended up doing overtime because we had to run two systems at once, and we ended up abandoning the new thing, and it was a huge waste of time and a huge amount of stress for everyone.
- 3:51SPEAKER_01: I even know people who are like, the system shift is the reason I got fired.
- 3:55SPEAKER_01: So it's an emotional thing, whether people like it or not.
- 3:58SPEAKER_01: I mean, I all I often say to people that, you know, I've had people in my offices kind of, you know, tear up when it comes to talking about tasks and systems and project management.
- 4:11SPEAKER_00: It's a little bit off what we're talking about today, but that's probably another thing with AI and automation and improving systems so that we can bring in AI and automation.
- 4:20SPEAKER_00: That's going to be a big elephant in the room.
- 4:22SPEAKER_01: Well, maybe that's another that's a second part to this episode is going into AI more in more detail because you know that is part of it.
- 4:31SPEAKER_01: Like we have clients who come in and say, right, it's time to add AI to my business, and that is the prime directive of these software updates.
- 4:39SPEAKER_00: Yeah, but I don't think we've had, and then I'm going to fire half the team, be part of that.
- 4:44SPEAKER_00: It's it's generally always my team's overworked.
- 4:47SPEAKER_00: They're doing a lot of things that are very, very automatable, that is, it's consuming a huge chunk of their time.
- 4:53SPEAKER_00: And I I want them to be putting the time into the parts that matter, the parts where a human touch is actually important.
- 4:58SPEAKER_00: You know, I think especially they're basically just interacting with their AI.
- 5:03SPEAKER_00: We could automate that part of it, and then we could just be dealing with the result and trying to humanize that better.
- 5:08SPEAKER_01: Yeah, I'm sure you guys have um had this experience where you get a piece of writing or a piece of output from a team member, or maybe from, you know, somebody's um you're working with a company and they send you something, and it's very obvious that that thing was made by AI.
- 5:26SPEAKER_01: Sometimes the problem that we're trying to solve with the system isn't uh that we don't use AI and it's time to use it, it's that the team is using AI badly and we need to improve it.
- 5:37SPEAKER_00: Yeah, or take that part off their hands.
- 5:39SPEAKER_00: I think that's the other thing that can be happening is sometimes they're using AI, but they're not.
- 5:42SPEAKER_01: It's all siloed, I think.
- 5:44SPEAKER_00: One, it's siloed, so no one can see what's going on.
- 5:48SPEAKER_00: But two, it actually needs a more thorough processing.
- 5:51SPEAKER_00: I think sometimes the issue is that what they're producing with the AI isn't good enough either.
- 5:55SPEAKER_00: And you actually want to get the prompt from them, clean it up, maybe create an automation where it's going through multiple steps with AI to target different things each time, and then produce a cleaner, less error-prone output, and then give it back to them and be like, cool.
- 6:09SPEAKER_00: Now you're the human layer, and I need you to catch where it's mucking up, where it's inconsistent.
- 6:15SPEAKER_00: I need you to remove all of the AI isms that I, for love no money, can get out of the AI that I can't get out of the AI's output.
- 6:23SPEAKER_01: Yeah, 100%.
- 6:25SPEAKER_01: And so this is kind of phase one is get buy-in.
- 6:28SPEAKER_01: Now we're gonna talk about how to get buy-in because I think the first thing you want to know is that you you do you don't have to get buy-in, but it's really frustrating when you're dragging a team or a CEO kicking and screaming to a new process.
- 6:45SPEAKER_01: What you'll often end up with is just non-compliance, like they won't use the thing that you've made, and you'll end up with in a position where you've spent.
- 6:54SPEAKER_01: I mean, I've worked with clients who spent$40,000 on something that nobody touched.
- 6:58SPEAKER_01: You know, sometimes and often that's kind of the one of the starting points of why they reach out to us is because the previous system was just a system.
- 7:10SPEAKER_01: It was just somebody going, oh, here's a bunch of stuff.
- 7:14SPEAKER_01: Just follow the instructions on this bunch of stuff and you'll do perfectly.
- 7:18SPEAKER_01: And the team or the CEO, it's kind of sometimes one and sometimes the other, will go, no, thank you.
- 7:24SPEAKER_01: I would rather use pen and paper.
- 7:26SPEAKER_01: I'm going to ignore this.
- 7:28SPEAKER_01: And there's it's it's very hard to solve that problem because you it's not that the person isn't good, it's just that they they can be very resistant.
- 7:39SPEAKER_01: And people often say, Well, you should just tell them to do it.
- 7:42SPEAKER_01: And that's true.
- 7:44SPEAKER_01: But in practice, at least my experience working with um with clients, is that it's a little bit harder than that if you've worked in an in an actual office.
- 7:52SPEAKER_01: You can't just come in and say, We're all using this, everyone get on board.
- 7:56SPEAKER_01: It's a lot harder to to get real compliance because you want people to become champions of the thing that you're building.
- 8:04SPEAKER_01: You want them to believe in it and sell it to not just the team that you have right now, but the future people that come in.
- 8:11SPEAKER_01: Oh, this is a great system.
- 8:12SPEAKER_01: It works like this.
- 8:13SPEAKER_01: Let me show you.
- 8:15SPEAKER_01: If everybody comes in and they go, this is a terrible system, we hate it, we use it as little as possible.
- 8:21SPEAKER_01: We're not using it in all these secret ways, we're not telling other people.
- 8:24SPEAKER_01: Um, and we're immediately getting you on board with the fact that this sucks as well.
- 8:28SPEAKER_01: That that's what you want to avoid.
- 8:30SPEAKER_01: And that's why we want to start with buy-in.
- 8:34SPEAKER_00: Yeah, that makes sense.
- 8:35SPEAKER_00: I imagine what's going on there a lot of the time is they know they're still on the hook for their deliverables.
- 8:40SPEAKER_00: And they know the system they're using might not be perfectly efficient, but it does work.
- 8:45SPEAKER_00: And what they're seeing is a system that involves a lot more data inputs and they don't really understand it yet.
- 8:51SPEAKER_00: And now they got to learn the new system on top of their current workloads.
- 8:55SPEAKER_01: Exactly.
- 8:56SPEAKER_01: And it's funny because, you know, we talk about being fractional COOs.
- 9:01SPEAKER_01: I think of us as a duo in that way because my job, you know, I was in university for HR and psychology.
- 9:08SPEAKER_01: My job is to get culture fit and get buy-in, and Robbie's job is to build the system.
- 9:14SPEAKER_01: And it's nice to have both because both are equally important.
- 9:18SPEAKER_01: And often when you just find somebody who's gonna do one thing, you can lose the other piece.
- 9:24SPEAKER_01: If we're all just gonna talk about culture and how we could do better, that's amazing, but it's not really gonna change anything about like what are we gonna do about AI right now?
- 9:33SPEAKER_01: But if you're also just getting a fix with no cultural shift, then you'll end up with non-compliance.
- 9:39SPEAKER_00: You can get the buy-in by finding the sort of the pain points of each of the team members, like you know, they hate the way the meeting's currently being handled or the way that they have to spend all their time communicating things back and forth, and you can sort of go, okay, well, this system's built so that you've got a single source of truth and you don't need to communicate back and forth because it's just going to be here and that's where it'll be recorded.
- 10:00SPEAKER_00: And if they've changed something, it'll be recorded here too.
- 10:03SPEAKER_00: And they think, oh, that's amazing.
- 10:04SPEAKER_00: But then if you don't design that system, then you didn't actually fulfill any of those promises.
- 10:10SPEAKER_01: Exactly, exactly.
- 10:12SPEAKER_01: And you know, what what I've done, and I did this particularly with that healthcare company, was interviewing, interviewing people and saying, hey, what do you want to get out of this system shift?
- 10:23SPEAKER_01: You know, let's not think about the CEO right now, let's not think about the whole team right now.
- 10:28SPEAKER_01: Let's just think about you.
- 10:29SPEAKER_01: Like, what do you want?
- 10:30SPEAKER_01: What's your directive in this business?
- 10:33SPEAKER_01: What do you want to get out of this shift?
- 10:35SPEAKER_01: And then that allows us to go, okay, well, let's not forget that this particular person really wanted it to be usable on their phones.
- 10:44SPEAKER_01: So let's make sure that that's possible with the new system.
- 10:48SPEAKER_01: Those little adjustments can make a big difference, and that gets us into the second phase, which is prototyping.
- 10:57SPEAKER_00: I think the theme of prototyping is going to be sort of minimal minimum incremental, yeah, minimum viable product, uh, minimum sort of incremental developments.
- 11:06SPEAKER_01: I like to call it minimum viable prototype.
- 11:08SPEAKER_01: And essentially what this means, and sometimes people are can surprised by just how basic a minimum viable prototype can be.
- 11:18SPEAKER_01: We're a big fan of Excel spreadsheets because a lot of times people know how to use an Excel spreadsheet.
- 11:23SPEAKER_01: And so it can be really helpful to provide a team member with a spreadsheet.
- 11:28SPEAKER_01: In fact, we've had team members go ahead and build their own spreadsheet and kind of shout out to the people who went and built their own minimum viable prototype, and we were able to build that into our systems.
- 11:39SPEAKER_00: It provides a lot of good information.
- 11:40SPEAKER_01: It does, it does.
- 11:41SPEAKER_01: So being able to go, okay, what do you want?
- 11:44SPEAKER_01: So, okay, I'll give you an example.
- 11:46SPEAKER_01: We have a healthcare company, we're in the prototyping phase right now with that company, and we've created Excel spreadsheets that have brought together a lot of different requirements that this new system, which is going to be in Microsoft, is going to need.
- 12:04SPEAKER_01: What if this was all in one spreadsheet and it doesn't have all the abilities now?
- 12:08SPEAKER_01: So people are saying they said, what about the Teams notifications?
- 12:12SPEAKER_01: If somebody inputs something into the spreadsheet, you don't get a Teams notification.
- 12:16SPEAKER_01: But in the future, with the new system that we're building, that won't be the case.
- 12:20SPEAKER_01: You will get a notification.
- 12:21SPEAKER_01: So this is the kind of stuff that people are starting to see.
- 12:24SPEAKER_01: But what they're also starting to see, along with, oh, this is what I want, they're also starting to see, oh, asynchronous tasks is a really helpful thing to have.
- 12:34SPEAKER_01: Because what they were doing before was just chatting back and forth in Teams.
- 12:37SPEAKER_01: I'm sure a lot of you guys have like a Teams chat or a WhatsApp chat or a Slack chat that you're artsing tasks back and forth in and not realizing that an asynchronous task system could be helpful.
- 12:50SPEAKER_01: But when you discuss, hey guys, do you want to get on like do you want to get on Notion?
- 12:53SPEAKER_01: Everyone's like, absolutely not.
- 12:55SPEAKER_01: I'd rather do anything else.
- 12:56SPEAKER_00: Yeah, and to be clear, the point of doing it in Sheets or Excel isn't obviously to build out all the features.
- 13:02SPEAKER_00: The point is just to collect that information about, oh, also I'm gonna need this column and this column and this column.
- 13:09SPEAKER_01: And and also for the team itself to build it.
- 13:11SPEAKER_01: So I had a meeting with a healthcare company, and then two days later she's like, Oh, this was so great that we duplicated the sheet for another another person on the team.
- 13:22SPEAKER_01: So now they are also doing it, and they were able to do that.
- 13:25SPEAKER_01: It was easy.
- 13:26SPEAKER_01: They know how to duplicate a sheet, they didn't have to sit on their hands and wait for us to do the next thing.
- 13:30SPEAKER_00: Yeah, you're not gonna have information not getting to you because they they know that there's a field missing, but they don't know that they should communicate that to you, or they don't know how complicated that is.
- 13:41SPEAKER_00: Whereas if it's a sheet, they just add the column and then you just get to see that information.
- 13:45SPEAKER_00: It's also the kind of information that you're gonna miss if you're just relying on the interviews.
- 13:49SPEAKER_00: So the interviews are great, but again, we've talked about the sort of brief gap issue.
- 13:52SPEAKER_00: So if the person, especially if the person you're talking to is the ADHD founder, there's gonna be a lot of little details that are missing.
- 13:58SPEAKER_00: They sort of we want this and we want this.
- 14:00SPEAKER_00: But when they actually try to implement it, you can sort of see, oh, okay, yeah, but these two things aren't working together, and we really need to pull that into a separate sheet.
- 14:07SPEAKER_01: Well, even, you know, like it's uh I'll interview the CEO, then I'll interview the CEO's team, and then we'll create prototypes.
- 14:15SPEAKER_01: And the prototype is always a surprise.
- 14:17SPEAKER_01: I often say to my team, you know, nothing survives contact with people.
- 14:21SPEAKER_01: You know, we'll put a put a put a spreadsheet together, put a put a basic notion system together, and immediately people are like, what about the recurring tasks?
- 14:29SPEAKER_01: What about this?
- 14:29SPEAKER_01: What about that?
- 14:30SPEAKER_01: But it gets buy-in in multiple different ways.
- 14:32SPEAKER_01: I think one people start to see, because not everyone can like, if you explain something to me, Robbie, you'll know this.
- 14:39SPEAKER_01: If you explain something to me, I can't really picture it often.
- 14:42SPEAKER_01: I'm like, I don't know, it sounds a lot.
- 14:44SPEAKER_00: But then once it's you're very play the first round and then I'll understand the rules.
- 14:49SPEAKER_01: Play the first round of the board game.
- 14:50SPEAKER_01: And so these prototypes are allowing us to play the first round of the board game or have the first pass at something, and have people go, Okay, I see all the things I want fixed, but also I see some of the things that could be better, even at that basic level.
- 15:06SPEAKER_00: They're starting to they're starting to catch the vision, they're they're seeing the potential.
- 15:11SPEAKER_00: It's also way easier for them to react.
- 15:13SPEAKER_00: Again, coming back to that brief gap episode that we did, it's way easier for them to see the gaps in a prototype in front of them than to think of all the gaps straight off the bat.
- 15:23SPEAKER_01: Exactly.
- 15:24SPEAKER_01: And I think it it's also about that co-creation idea.
- 15:27SPEAKER_01: The more people go, This is good, but I'd like it to have this.
- 15:30SPEAKER_01: And we go, Yeah, we can do that.
- 15:31SPEAKER_01: We often say, Imagine we have a magic wand and just tell us what you wish was there, because you'd be surprised what we can actually build.
- 15:37SPEAKER_01: Sometimes people aren't aware of what can be built.
- 15:40SPEAKER_01: The more the team does that, the more you then also get the buy-in.
- 15:44SPEAKER_01: Because now they're like, oh, it's gonna have that thing that I wanted that I've never really been able to describe until we started prototyping.
- 15:50SPEAKER_00: And if you haven't jumped into a system yet as well, all of those requests and sort of features that you need can now become part of what you're looking for when you're picking the system that you're eventually gonna end up in, making sure that the correct integrations and whatever else you need are there.
- 16:04SPEAKER_01: Yeah, exactly.
- 16:05SPEAKER_01: So, yeah, we love minimum viable prototyping.
- 16:08SPEAKER_01: And just a side note for those of you who are gonna do this yourself with the word prototype, rough draft, first draft, all of those words, put them everywhere in the system.
- 16:17SPEAKER_01: Really, really important thing that you don't want people to start thinking, and you'd be surprised how often this can happen, is that this is the solution.
- 16:26SPEAKER_01: You know, the person who goes, they've made a spreadsheet.
- 16:28SPEAKER_01: Oh my god.
- 16:29SPEAKER_01: So, you know, you want it to say prototype.
- 16:32SPEAKER_01: This is like we always make sure it says, you know, prototype.
- 16:35SPEAKER_01: This is a first draft.
- 16:36SPEAKER_01: Um, this is just a test.
- 16:38SPEAKER_01: Tell us what you don't like about it.
- 16:39SPEAKER_01: That's okay.
- 16:40SPEAKER_01: Like that's part of this process.
- 16:42SPEAKER_01: So we can all get on the same page.
- 16:43SPEAKER_00: Like the last column, just add more columns if you need it.
- 16:46SPEAKER_01: Exactly, right?
- 16:46SPEAKER_01: Like anything you can do.
- 16:48SPEAKER_01: So then we have, so we've talked about prototyping.
- 16:51SPEAKER_01: We've talked, I think, a little bit about iteration as part of that, because as people prototype, they'll we'll naturally iterate the prototype and change it and build it.
- 17:01SPEAKER_01: Like the spreadsheet you made for the healthcare provider now has an entirely different sheet for a different provider.
- 17:08SPEAKER_01: And then there was one or two sheets where we're like, okay, we're not going to do it.
- 17:13SPEAKER_00: I get the impression each one's setting up their own different fields because a bunch of them interact differently with sort of a slightly different set of clients.
- 17:20SPEAKER_01: Exactly.
- 17:21SPEAKER_01: Yeah.
- 17:21SPEAKER_01: So the iteration will happen on its own, generally speaking, especially when you give them a people a system that they can use.
- 17:29SPEAKER_01: But it's good to keep track of it and keep an eye on, okay, what's being built, what does it look like?
- 17:35SPEAKER_01: I like to call it like observing the flow of the river.
- 17:38SPEAKER_01: You want to start to see how this river of, you know, people and systems in the business is flowing and how they naturally get siloed and where it naturally goes so that you can iterate the prototype.
- 17:50SPEAKER_00: Yeah, I think iteration is also referring to actually once you've moved past that prototype phase into delivering it, you again you're trying to select what's the minimum, what's the most essential piece that we can get up and running that will actually start getting this used, even if it doesn't have every bell and whistle and every extra thing that we would like to track on top of it.
- 18:11SPEAKER_01: Yeah.
- 18:12SPEAKER_01: So once you've done iterating the prototype, then we've got to go in and say, okay, what's the first piece of the actual shift that we're going to build?
- 18:20SPEAKER_01: And, you know, this might feel like a lot for those of you who are like, oh my God.
- 18:24SPEAKER_01: There's a lot of systems.
- 18:25SPEAKER_01: But the reason is because at the same time as this is all happening, you should be running a successful business that's busy, that's got people in it, that's got events happening and clients happening, and it's growing.
- 18:38SPEAKER_01: And none of those things should be stopping because we're shifting systems.
- 18:42SPEAKER_01: And so that's why we're doing it in this way.
- 18:45SPEAKER_01: And so when we're talking about okay, what's the first thing we build, there's that balance between let's not build on the thing that everybody needs to use right now.
- 18:55SPEAKER_01: We have a catering client where they're doing, you know, events this week.
- 19:02SPEAKER_01: That's not where we want to go ahead and do the updates to their systems right now.
- 19:08SPEAKER_01: Things that are happening next month, that's a good that's a good place to do it.
- 19:12SPEAKER_01: That are happening next year.
- 19:13SPEAKER_01: I don't think anybody cares that much right now about improving the system.
- 19:17SPEAKER_01: So it's about finding that really good spot to make those updates.
- 19:21SPEAKER_00: Yeah, you want to get them used to using a new system, like for instance, pulling all of the tasks into one centralized location and out of the messaging apps.
- 19:30SPEAKER_00: If you're doing something like moving where their tasks get tracked, for instance, you definitely don't want to want to be doing that on what's happening this week.
- 19:39SPEAKER_00: So you want to go a little bit further back out.
- 19:40SPEAKER_00: We're gonna pull everyone's tasks, centralize them in this location.
- 19:43SPEAKER_00: This is the single source of truth.
- 19:45SPEAKER_00: We're gonna get it out of the messaging apps, all that sort of thing.
- 19:47SPEAKER_00: But we need to get used to this, and we need to sort of acknowledge like the active system, the active projects right now, keep doing things the way you're doing it.
- 19:55SPEAKER_00: Over here, we're gonna try this new system, we're gonna get used to it, we're all gonna get familiar, we're gonna run into any road bumps that we have, we're gonna troubleshoot any problems we have.
- 20:02SPEAKER_01: And this will become more relevant than the next phase after next that we'll talk about is about keeping, making sure your team is behind you.
- 20:09SPEAKER_01: When you switch systems, I can almost guarantee there's gonna be two or three people who are like, this system is great, and I'm an expert in the system, so I know how it could be improved.
- 20:19SPEAKER_01: And I think we should switch immediately today to the new system, and we should just, we should just all be able to figure it out from there.
- 20:27SPEAKER_01: There will be different levels of skill on your team.
- 20:30SPEAKER_01: Some people are gonna be like, I hate this, but okay, you know, like, and then there'll be people who are like, why isn't this AI layered immediately?
- 20:38SPEAKER_01: And so what you want to do is you do want to be aware that when the people who are very excited about the system and immediately know how to use it say, why don't we use it for the event that's happening tomorrow?
- 20:52SPEAKER_01: That isn't necessarily a good idea because there are other people on your team who might not be putting their hand up because they don't want to admit they don't know what's going on.
- 21:00SPEAKER_01: But if you made that shift immediately, they would be super lost and you would lose a lot of the buy-in that you've built and been working on.
- 21:07SPEAKER_01: I had that conversation with a client's uh team member this cookie.
- 21:12SPEAKER_00: Yeah, I think especially once you pull one thing out of sort of pen and paper into the system, they can see the benefits.
- 21:18SPEAKER_00: They're thinking, right, let's do this with everything immediately.
- 21:20SPEAKER_00: And you're going, no, no, no, let everyone get on board with this, let's make sure it's working properly, then we're gonna attack one more piece in, and then everyone's gonna get used to that, and then we're gonna take a new another couple of pieces and put them on attach them as well.
- 21:33SPEAKER_00: But we need to, if we just implement the entire thing in one go, it's gonna fall over because there's gonna be too many troubleshooting issues happening at once, and the complexity of the whole the system as a whole is gonna overwhelm all of the team members who needed who who haven't done this before, who haven't had a system like this, who aren't sure where to put everything, and they don't know how to navigate between the things, and they don't know you know how to sort a database, for instance.
- 22:00SPEAKER_01: Yeah, yeah.
- 22:01SPEAKER_01: Some people like some people I think that's the crazy thing about what we do for a job is we often say, like, can you share your screen and can you show us how to how you're doing, you know, this particular piece?
- 22:13SPEAKER_01: Or can you we spend a lot of time um backseat driving people's screens.
- 22:18SPEAKER_01: And so you do learn as part of that just to how some people are really comfortable with knowing where to click on things and people some people are completely lost.
- 22:27SPEAKER_01: And I would say, you know, I'm more on the lost side of a new system than you are, which is why I think we make a good team.
- 22:34SPEAKER_00: Yeah.
- 22:35SPEAKER_00: Your technical, your technically savvy team members won't always understand that there are going to be team members who aren't, and they might just get stuck in the wrong view of of a table, and now they're confused because they thought they were looking at a Kanban board and now they're looking at a calendar and they don't know are they on the wrong page?
- 22:55SPEAKER_00: No, they're on the right page, but it's still wrong, what's going on?
- 22:58SPEAKER_00: Yeah.
- 22:59SPEAKER_00: And those are all the issues you need to sort out before you start adding even more complexity.
- 23:04SPEAKER_01: Exactly.
- 23:04SPEAKER_01: And and yeah, I think that's worth worth mentioning and and to kind of speak to the ADHD side here, because obviously we uh do this with ADHD founders and their teams.
- 23:15SPEAKER_01: I'm very used to at this point working with clients who come to me and say, I have no system, I write things down on pieces of paper, and then later on I find those pieces of paper.
- 23:28SPEAKER_01: And that's my task list.
- 23:29SPEAKER_01: And taking them all the way through, like I have that client I was telling you about from the beginning of the year, all the way through to Buildbook.
- 23:37SPEAKER_01: Like when I first met him, his construction company had no there was no task list, there was no process in that way.
- 23:46SPEAKER_01: It was very much in the head.
- 23:47SPEAKER_01: There was no calendar, which was, you know, it was all just based on messaging and and one particular app that said, like, this is where you go to get the quote, and that was it.
- 23:57SPEAKER_01: So you can make huge shifts in a short period of time, but not all today.
- 24:03SPEAKER_00: Right.
- 24:03SPEAKER_00: Yeah, I'm guessing that didn't all happen overnight.
- 24:06SPEAKER_01: No, no, it was it was a step-by-step process.
- 24:08SPEAKER_01: In fact, the system that we ended up using, which was Build Book, came about because in the process of interviewing this client, what I found was that he had Build Book and been paying for it, but had abandoned it because it didn't feel like it was working.
- 24:24SPEAKER_01: The complexity of onboarding into that system had been so great that it just got left.
- 24:30SPEAKER_01: And it was only when we hired him somebody to help do some of the behind the scenes sort of admin work in Build Book that we were able to get the team onto Build Book in the way that we have it happening today.
- 24:44SPEAKER_00: I think that can be one of the costs of a more complicated system, is there's a little bit more of an admin burden, and it can be good to put that off onto an admin person rather than trying to push it onto all of your sort of guys on the field who are thinking, well, I was already sending a message and now I gotta go log into something, I gotta go back to my laptop, I gotta log in, I don't always have internet, and now I've got to go to three different form locations and put the data in the right place, and and so then you're actually like, okay, no, just send the information you're already sending, someone else will process it.
- 25:15SPEAKER_00: But there's gonna be a whole lot of efficiency gains on the back end for me, having it all going into the right place and being put in the right spot.
- 25:21SPEAKER_01: Yeah, sometimes what we find is that a new process like that does come with a new hire.
- 25:26SPEAKER_01: Sometimes that hire is an AI agent.
- 25:29SPEAKER_01: One of our clients hired an AI agent or several now, as uh, you know, to help with that process.
- 25:36SPEAKER_01: Yeah, they're if they're multiplying.
- 25:37SPEAKER_01: But yeah, sometimes it there, you know, sometimes for different clients it'll be an AI agent or it'll be a an assistant or it'll be a full-on project manager, but sometimes we do have to go in, and this is the benefits of having fractional COO.
- 25:50SPEAKER_01: We do that process.
- 25:51SPEAKER_01: Although this a I will say for this client, we did not help them with their AI agents.
- 25:56SPEAKER_01: They were very excited to start using those.
- 25:59SPEAKER_00: Yeah, that'll be an interesting one.
- 26:00SPEAKER_00: We're gonna try and find all the places to plug them in and have them handle sort of first drafts and pushing each piece through the process.
- 26:09SPEAKER_01: It can be very similar to hiring a person.
- 26:11SPEAKER_01: There's just, you know, maybe more editing in terms of, you know, you have to introduce them to the team, you have to make sure they're familiar with the systems and give them access to everything.
- 26:24SPEAKER_01: There's a lot of access.
- 26:25SPEAKER_01: People always underestimate the amount of access you have to give people and AI bots.
- 26:29SPEAKER_00: There's a lot of onboarding work, and there's also a whole lot of etiquette around how to talk to it.
- 26:34SPEAKER_01: Yes, talk to them.
- 26:35SPEAKER_01: Now, phase four, you want to build it and let it breathe.
- 26:40SPEAKER_01: There comes a time in the building phase where you have built it, and now there's probably gonna be a list of things that need to be changed, and people are gonna come in with improvements because there'll always be the people who I said like at the top of the class in this system shift who are like, We imagine we did this and we did that and we did that, and people at the bottom who are like, I understand what's happening finally.
- 27:08SPEAKER_01: So when everybody is kind of at a point where the reason we made this system improvement has sort of 80% been resolved, we do want to take a beat.
- 27:20SPEAKER_01: And for us, it's usually a couple of weeks, it's not it doesn't have to be very long, and just let it breathe.
- 27:26SPEAKER_01: Let people just use the system, have the system become part of their daily life without the stream of updates about the system.
- 27:34SPEAKER_00: Yeah, one, you're gonna burn them out with too many systems.
- 27:38SPEAKER_01: You could iterate forever.
- 27:40SPEAKER_01: We need to know when to pause.
- 27:42SPEAKER_00: Yeah, it's a good time to just turn around and check.
- 27:44SPEAKER_00: Are your team still behind you?
- 27:46SPEAKER_00: Yeah, or have they started, had did you lose them halfway down the track and now they're off back on pen and paper because to hell with this idea, you know, or one of them didn't come with you because, like we discussed, you know, they had a bad experience.
- 28:00SPEAKER_00: You know, maybe they've been with you the longest and they've seen this whole thing crash and burn twice before.
- 28:06SPEAKER_01: Seen this film before.
- 28:07SPEAKER_00: Yeah, and they're not gonna be sucking in this time.
- 28:10SPEAKER_01: Like, yeah, they're just watching.
- 28:12SPEAKER_01: Little did you know.
- 28:13SPEAKER_01: It is important if you think about it, like you know, you're going through you're going on an expedition, right?
- 28:18SPEAKER_01: At some point you have to stop and you have to check that all the members of your party are still there.
- 28:24SPEAKER_01: Yeah.
- 28:25SPEAKER_01: Do a head count.
- 28:26SPEAKER_01: Is anybody lagging behind?
- 28:27SPEAKER_01: Does anybody lose anything on the way?
- 28:29SPEAKER_01: Like, we do want to just check in.
- 28:31SPEAKER_01: And yeah, once you're in that let it breathe phase, then we can move to the make sure your team is behind you.
- 28:38SPEAKER_01: So, what I prefer when we're doing these kinds of builds is that as we're building the process, we have an instruction manual.
- 28:47SPEAKER_01: So we do have some writing about how to do this.
- 28:52SPEAKER_01: Although you and I have the same work on the same system that the best instruction manual is just a really well-designed system with lots of instructions in the system.
- 29:01SPEAKER_01: So when you look at the button and wonder if you should click it, it says, Click me if you are this person doing this thing, like that kind of level, as much as you can.
- 29:08SPEAKER_00: That's kind of a coding principle, is you don't want to be relying on documentation or even that much commenting.
- 29:13SPEAKER_00: You want it to be self-explanatory.
- 29:15SPEAKER_00: Use the use the names that actually just help you understand.
- 29:18SPEAKER_01: Exactly.
- 29:18SPEAKER_01: So self-explanatory with an instruction manual.
- 29:22SPEAKER_01: Now, at this point, sometimes people go, Okay, let's write a standard operating procedures document.
- 29:28SPEAKER_01: But it's it's a bit better to write one of those after you've gotten through the pause and make sure your team is still behind you phase.
- 29:36SPEAKER_01: Because what you might find is that, like if you were on an expedition and you forge ahead and you never look back to see if everybody's with you, you start creating a standard operating procedure for this process.
- 29:48SPEAKER_01: There's probably a few adjustments you're gonna have to make to cater to people who are still confused that you're gonna not include in that document.
- 29:58SPEAKER_00: Yeah, I think I mean, I think to say it simply, you want to troubleshoot all the issues out.
- 30:03SPEAKER_01: You want to iterate until you've got 80% of the issues.
- 30:06SPEAKER_01: So we're never gonna troubleshoot all the issues.
- 30:08SPEAKER_00: Yeah, and I think once you've once you've confirmed your team's behind you, they've handled it, check in with them, make sure they're ready to add a new layer of complexity, make sure they understand, like they can see.
- 30:20SPEAKER_00: We are probably talking about taking a month to sort of have them see, oh, this is actually working a lot better.
- 30:25SPEAKER_00: Like initially it's just friction, but then oh what it has actually been quite nice not having to have a meeting to get on the same page every every three days.
- 30:33SPEAKER_01: A long meeting in which everybody just verbally goes through each other's task lists.
- 30:37SPEAKER_00: I can see what's due for me today.
- 30:39SPEAKER_00: I I can go to one location and everything across all our different projects, I can see what I need to do today and tomorrow in my space, filtered with with everyone else filtered out.
- 30:48SPEAKER_00: Then you have the buy-in for the next phase, which is adding the extra complexity, and you and you're gonna repeat that process until you've got a system that's really working and doing everything that you want it to do.
- 30:58SPEAKER_00: And then I think at that point, Cheerry on Top is actually documenting some of the systems, this some of the standard operating procedures so that this doesn't end up being the system that worked really well for a while, and then that person left unexpectedly, and the whole thing kind of broke down, and no one really knew how to run it anymore.
- 31:17SPEAKER_01: Yeah, we don't want your systems champion to be the person where they're like, Oh, do you remember Jody?
- 31:22SPEAKER_01: Jody really knew what was going on.
- 31:25SPEAKER_01: Everything works so much smoother.
- 31:27SPEAKER_01: Yeah.
- 31:27SPEAKER_01: We want a something that the team can get onboarded to.
- 31:31SPEAKER_01: And what that is honestly keeps changing.
- 31:34SPEAKER_01: Maybe it's a series of videos.
- 31:36SPEAKER_01: We tend to build documents with pictures because then people can put those with into their AI, and their AI can act as a bit of an instruction manual.
- 31:47SPEAKER_01: So our standard operating procedures tend to be in that format.
- 31:50SPEAKER_01: But I know there's lots of different formats and whatever formats easiest for you guys to get it down and get it done.
- 31:56SPEAKER_01: So we have a team member, um, Christine, who will interview the key operators of the process once it's running and just ask, you know, hey, share your screen and walk me through what this process looks like looks like and how it works.
- 32:12SPEAKER_01: And then that will be turned into the standard operating procedure documents for the team.
- 32:19SPEAKER_01: So that's how we tend to run it.
- 32:21SPEAKER_01: But however you will find it easiest to do, and that's always changing these days.
- 32:27SPEAKER_01: You do want to make sure that you take a minute and sort of celebrate by creating a document that can be used again and again.
- 32:35SPEAKER_01: And it's always, always easy.
- 32:37SPEAKER_01: We have our own experience.
- 32:38SPEAKER_00: I was gonna say, I'm not sure your team will think it's a celebration to document their process.
- 32:42SPEAKER_01: Well, I think it's pretty cool.
- 32:44SPEAKER_01: Yeah.
- 32:45SPEAKER_00: I think that interviewing process is really effective because it catches all the little things again.
- 32:50SPEAKER_00: Like again, coming back to that sort of brief gap idea, I think there's sort of a similar thing when someone explains what they do.
- 32:55SPEAKER_00: There's a lot of little pieces that they're missing that they don't think about until later.
- 32:58SPEAKER_00: But if they're actually having to do it in front of someone and you're documenting it with uh with Loom or a video recording or whatever, that can get picked up.
- 33:05SPEAKER_00: So I think often a Loom video is a great first step, and then have someone else translate that into an actual document that is a lot easier to update because the next person who comes onto the job might need to make some updates, and updating a Loom video is not going to work very well.
- 33:17SPEAKER_01: Yeah, exactly.
- 33:18SPEAKER_01: So there's a whole variety of different ways to do this, but key point is don't forget to create the standard operating procedures because if you don't, all of the other phases that we've just discussed can just lie fallow two years from now.
- 33:35SPEAKER_01: Like right now, it feels like impossible that you're never not gonna be using the system.
- 33:40SPEAKER_01: But two years from now, if a key operator leaves, you may find yourself in a situation where no one understands this process again, and you have to go all the way through buy-in and prototyping and iterating and everything else.
- 33:52SPEAKER_00: Yeah, I was gonna say you probably won't have to like prototype it again.
- 33:56SPEAKER_00: Like the the existing system should be functional.
- 33:59SPEAKER_00: The the threat is more that okay, you might have to go through the whole process again if the system becomes so abandoned.
- 34:07SPEAKER_01: But I mean you're talking about Yeah, but think about it, right?
- 34:09SPEAKER_01: I have a client who used build book, didn't like it, didn't understand how it worked.
- 34:15SPEAKER_00: I think there's the there is the failure mode of we got halfway into this and I turned around and my team wasn't with me.
- 34:22SPEAKER_00: And they were they I had to go find them again.
- 34:25SPEAKER_00: And so now I'm back on the path that they're happy with, and we didn't go in that direction after all.
- 34:29SPEAKER_00: And I think that's sort of the buildbook example, maybe.
- 34:32SPEAKER_01: Actually, that one, if if I'm thinking about it, is more like um it was created and the CEO didn't buy into it, and so it was abandoned.
- 34:41SPEAKER_01: But your your uh example is also good.
- 34:43SPEAKER_00: Well, kind of same thing from the different direction, I guess.
- 34:46SPEAKER_00: Yeah, either way, some subset of the party had to go back and find the rest of them.
- 34:51SPEAKER_01: All of that is to say if you get to the top of the mountain that is improving your system, definitely make a note of exactly what that system improvement is and what that looks like.
- 35:00SPEAKER_00: I think the threat that we're talking about now is key operator leaves suddenly, a bunch of just do it by paper for now type systems come in to fill the gaps.
- 35:12SPEAKER_00: Someone new comes in, they don't understand how it used to be done, and the transition from the make it work in the meantime system to get back to there is complicated.
- 35:22SPEAKER_00: Yeah.
- 35:22SPEAKER_00: Because now we've got things in two different places, neither option is great.
- 35:26SPEAKER_00: And if we move, if we try to move back to the old system, there's a lot of data migration, a lot of things that are just over here on the we had to come together and make do in the meantime system.
- 35:38SPEAKER_00: And and so that that new system sort of ends up just kind of becoming legacy because yeah, it had fallen back to sort of the minimum viable solution, and now we're not at that sort of next level, more efficient, more useful system because we couldn't just plug a new person in and give them an instruction manual.
- 35:57SPEAKER_01: Yeah, yeah, 100%.
- 35:59SPEAKER_01: And if you've gotten to all of those pieces, then congratulations, you have successfully improved your systems.
- 36:05SPEAKER_01: And if you're listening to this and realizing, you know, wow, that is a lot of whether you've done it or not.
- 36:10SPEAKER_01: Yeah, it's a complicated process.
- 36:12SPEAKER_01: It takes a long time.
- 36:13SPEAKER_01: Like you're asking people to change their behavior.
- 36:17SPEAKER_01: Psychologists have argued for years about how to do this.
- 36:20SPEAKER_01: And as business owners, we're just like, yep, we can do it.
- 36:23SPEAKER_01: No worries, give us two months, you know.
- 36:26SPEAKER_01: So it is a complicated thing to do effectively.
- 36:31SPEAKER_01: It's not a hard thing to do ineffectively, but it's a complicated thing to do effectively.
- 36:35SPEAKER_00: I tend to opt for just creating a system that forces the people to do what I want.
- 36:39SPEAKER_01: Well, that's why you're my co-CO, because I do the systems of the people and you do the systems of the operations.
- 36:46SPEAKER_00: You definitely cover the blind the blind spots that I would not be able to And vice versa.
- 36:52SPEAKER_01: And vice versa.
- 36:53SPEAKER_01: It's good to have a team.
- 36:54SPEAKER_01: Thank you so much for listening to this episode of the ADHD Skills Lab.
- 36:58SPEAKER_01: If you liked it, leave us a five star review.
- 36:59SPEAKER_01: It helps other people learn more about us.
- 37:02SPEAKER_01: And thank you so much to our wonderful team for making us sound good, look good.
- 37:05SPEAKER_01: We couldn't do it without you.