Ep 242 | Get Started Building Your Knowledge Base with Roxanne Fry
If you're spending all your time directing people on where information is, training your team, or just struggling to figure out what the tasks the employee that just left did, then this episode is for you. Documenting the way things are done inside your organization doesn't just protect you when someone leaves, it helps to streamline onboarding and ensures that your team is doing critical tasks in the same way.
What you'll learn:
→ what is a knowledge base?
→ how to get started with creating one.
→ how often you should be reviewing your knowledge base.
→ creating your knowledge base champion
Want to skip ahead? Here are key takeaways:
[6:36] A knowledge base is a central location where you house all of the information people inside your organization, or your board, may need. This includes things like passwords, processes for repeateded tasks, event logistics, and more. It keeps things out of post-it notes, personal notebooks, and inside our own heads. This is an electronic document that is constantly evolving and being added to, but has the most current information.
[11:20] Creating a knowledge base takes time. First – start with new roles you're hiring for. Or maybe you have someone thats's about to take an extended vacation or retire. Document those elements first. Have them put their tasks down on paper. Then have someone that doesn't do that task read the instructions and see if they can execute.
[17:46] Keeping it up to date can be overwhelming. Any time you have a a major staff member transition its a good time to review those tasks. Otherwise, break it into sections and review one section quarterly. That way you know your entire knowledge base gets reviewed roughly once a year.
[22:54] Create a team culture around utilizing your knowledge base. It takes consistency to ensure this stays up to date. It can be helpful to have a chamption in the team that manages it and keeps everyone on track.
Founder, RoxStar Solutions
Roxanne Fry is the founder and CEO of RoxStar Solutions LLC. As a process improvement solutionist, she helps nonprofits leverage technology tools to streamline their day-to-day business operations and maximize the use of their CRM. Roxanne is a certified Salesforce Administrator with extensive nonprofit C-Suite experience. Learn more at https://roxstarsolutions.com
Download our Tech Checklist
How to Evaluate New Technology You Might Need and Technology You're Currently Using.
We love creating the podcast. If you like what you learned here please give us a tip and help us offset our production costs.
When you leave a review it helps this podcast get in front of other nonprofits that could use the support. If you liked what you heard here, please leave us a review.
[Sami Bedell-Mulhern] Hey, it's time for another episode of the digital marketing therapy podcast today as we continue to work through January and our systems and operations, I'm so excited to have my dear friend, Roxanne Frey here to talk about creating a knowledge base. And this in big picture is kind of where everything lives for your organization. So we're going to share what it is go a little bit more in depth into what goes into it, why it's important and how it can help you streamline your day to day processes, but also manage when you're onboarding new employees. If somebody's taking a long vacation, you have unexpected turnover, you don't have to worry about what are the steps? What are we supposed to be doing? Who's supposed to be doing what right everything is all in one place. And that is the power of a knowledge base. So if you have one that you haven't touched in a while this is a great episode for you. If you don't have one and you have no idea where to get started. This is a great episode for you as well.
Roxanne Fry is the founder and CEO of Rockstar solutions LLC. And as a process improvement solutionist. She helps nonprofits leverage technology tools to streamline their day to day business operations and maximize the use of their CRM. Roxane is a certified Salesforce administrator with extensive profit or extensive nonprofit C suite experience. I work with Roxanne almost every day and I'm so excited to finally have gotten her to say yes to be on the podcast was a great conversation. So I really hope you'll take a listen. I know that systems and operations aren't always the most fun when it comes to our organizations. But they're critical and allowing us to continue to do the work that we do, increase our impact and continue moving forward to serve the communities that we serve. So give it a listen. Let me know what you think.
Before we get into it, this episode is brought to you by our January freebie this year, we're giving away a new tool every single month. And this one is all about technology. When it comes to understanding the tech that you need to support your organization, we've created a tech Checklist to help you evaluate new tools that you're going to bring in to your organization. And also to be able to track the tools that you're currently using and how much it costs and how and when they renew right. So they can help you understand big picture, what tools you have that are supporting your organization, what things need to integrate with each other, and make better decisions quicker and make the research less frustrating when it comes to bringing a new software or technology into your organization. You can download the tech checklist at our website at https://thefirstclick.net/resources or in any of the show notes from the January episodes. I hope that you enjoy it and download it and get to work figuring out what tech is going to be the best to solve the problem that you need solving. Let's get into the episode.
[Intro] You're listening to the digital marketing therapy podcast. I'm your host, Sami Bedell-Mulhern. Each month we dive deep into a digital marketing or fundraising strategy that you can implement in your organization. Each week, you'll hear from guest experts, nonprofits, and myself on best practices, tips and resources to help you raise more money online and reach your organizational goals.
[Sami Bedell-Mulhern] Hello, hello everyone. Join me in welcoming Roxanne fry to the podcast. Roxanne, thank you for being here.
[Roxanne Fry] I am so thrilled to be here one of my favorite topics. Yay. Um,
[Sami Bedell-Mulhern]I have known you for a long time. And I'm so excited to finally have you on the podcast. It's been a bit. So I'm excited to have you here to talk about systems and operations and all the things that we don't want to think about. But things that are super critical to our long term success for organizations. So why systems? Why operations? Why is this something that you've loved kind of geeking out on and building a business around?
[Roxanne Fry] Well, there's so many things going on within a nonprofit we want to serve, our customers want to serve our donors. And so many times we are bogged down by the what are called back office tasks and projects, if we can do those better. And by better, I mean both more efficiently and more effectively, then we have more time and more resources to serve the people that we're here to serve. So that's why I love to dive into operations and streamlining and databases. Because there's so many opportunities, especially if you have someone help you stop, you know, step back and take a big picture view of what's happening and really questioning. Why are you doing that? Why are you doing it that way? Tell me more about that. How long have you done it that way? So that's what I love to dig into.
[Sami Bedell-Mulhern] I love that you said you know sometimes it takes a third party to kind of help you do that because I know we've both worked on off with Bas or had other people come into our business and there's so many things that we just do that we don't even really realize that there is a process. It's just our own process. But when it comes to communicating that or if we take a vacation or whatnot, people, it's not intuitive to everyone else.
[Roxanne Fry] Exactly, exactly. I mean, it could be anything from, I have a nonprofit I work with who I adore, they inherited an accounting process from a previous person who had been there for many years and done great things. But I was the one who stopped to say, why, why do you print this whole thing out on pink paper? Why do you print out the bank statement that's already there in front of you electronically? So how can we, you know, step back and say, Is there a reason for buying paper? We love pink paper? If there is great if there's not, why are we buying pink paper? Or if there's a way to why are we printing something that's already electronic? Right, let's do the editing. Let's do the markings. Let's do everything in a PDF editor, rather than trading more papers that someone needs to file and then someone needs to destroy in seven years, according to the document retention policy. So I love digging in to say why I feel like a toddler, sometimes. I'm the first one that comes in and just asks why, why tell me more?
[Sami Bedell-Mulhern] Yep, we need that though. Okay, so today, we're talking about knowledge bases specifically. So it doesn't matter where your housing your data, it doesn't matter where your CRM is like, this is not like a tech tool specific podcast, which is why I'm so excited about this topic. But could you kind of share what a knowledge base is and how it can kind of help organize all of this stuff that you you've just been mentioning? Yes,
[Roxanne Fry] a knowledge base is really a one stop shop for information, resources, and tools that every employee can go to. You can even have a knowledge base for your board members so that they don't need to keep track of all of the different documents, we share that they can be in a secure location that they can access at any time that's searchable. And the whole goal really is that the team your staff team, stops reading things on sticky notes, like necessarily passwords, but processes. A lot of people keep notebooks beside them. And if you have 510 15, staff members or more, think about how much information is spread across these notepads and sticky notes all over the place. So if you can get all that information in one place that's searchable that everyone has access to, according to their what they should have within the organization. You can streamline onboarding, you can streamline stored in your donors, all of the things that some people keep up here can be into a platform so that things can just run smoother and without as much effort.
[Sami Bedell-Mulhern] Yeah, and this goes beyond like you might have an employee handbook, which is something that would go into your knowledge base. But this goes into literally like what you said, how do we? What's our donor stewardship process? Like? I think one of the examples you shared with me a long time ago was like, even just the process of what happens when a donation comes in, like, who takes the cheque? Who deposits it, like all of those things? Like it's every single thing that you do in your organization, right?
[Roxanne Fry] Yes, absolutely. So just to touch on this really quickly, when I say knowledge base, I'm thinking electronic, right. So you could have a big binder, you don't want that because everyone has to go to wherever the big binder is, and it takes a lot to update. So knowledge base should be electronic, like I said, searchable. So some platforms could be Google site, si te those are free. If your nonprofit that has the Google Suite available to you. You could also use notion, which is actually pretty easy to use as well, very versatile. So when information goes in there, yes, it makes it easier. I usually I'd love to start and say when I'm talking to a nonprofit, okay, tell me what happens when a check comes in the door. And usually the list off are about four steps. But then when I dig deeper, and so a whole link between here and here, something has to have happened. And then we hear oh, there's this that happens. And this person touches that. And here's what happens. So there's two things that I identified there. First of all, is Can any of those steps be eliminated or streamlined? And the second is, let's make that a succinct description of steps bullet points. If This Then That. Here's, here's what we do. And that was literally walking through, you know, do you scan the check? Where is it saved? How does the person entered into their database? Can they just pull up in the PDF and then mark down on the PDF? What happens? If it's a credit card? What happens if it's a reoccurring gift? Because a lot of our team members know this, or they've developed a process, but if they were to, you know, the old hit by the bus theory if unfortunately, I got sick or they had to leave for a family emergency, and no one knows the process that team members either going to have a really long backlog of projects During a time that you're not communicating with your normal processes to your donors and your clients, or someone picks it up does it and it has to be corrected, because 10 steps were best. We all have the greatest heart for the nonprofits that we serve. So, you know, if you can take the time, and I highly encourage nonprofits to take the time, we say we don't have the time to do this, but we have to do it is to just stop, take a breath. And by that, I mean, let's start talking through all of these steps. They often do tie to CRM or to other processes that you're doing. But let's get them documented for the future. And for now.
[Sami Bedell-Mulhern] Yeah, well, and what does I mean? So if we're got to this point in the episode, and we are like, okay, yeah, we don't have that in place. But the thought of doing everything all at once, feels kind of overwhelming, right? There's lots of different things that happen in our organization. So is there an area where you recommend maybe we start or like, does this have to be done all in one shot? Can we do it over a period of time? Like, how can we make this something that's that is manageable, and kind of supports our organization without without all the overwhelm?
[Roxanne Fry] Right, it would be a lot to just try to document everything, when within a couple of weeks, that's just not feasible. And you probably don't have the mindset to do that, I would first look to see if you have any positions that are transitioning, meaning are you about to hire a new person, are you creating a new position? Is someone getting ready to retire or they're going on a three week vacation, whatever that looks like, look at that and see, is this a critical part of what we do? More than likely it is if you have a staff member covering it, then take the time to ask that person to write down. I mean, it's worth the investment, have them write down what they're doing. The next check to make sure that what's being documented is helpful to a person who doesn't know anything, is to literally have another person who doesn't know anything, sit down with the person who wrote the instructions, and just let them follow the instructions. And if they get to a part where they're like, I don't know how to get from here to here, we realized we're missing instructions. So have the person who has all that knowledge, dig deeper and put in more steps. That's a process that sometimes can take multiple refinements. If you can get the majority captured, then just keep refining. Maybe once every two weeks have a complete stranger within your organization, walk through the process. So that's one piece I would look at, if you don't have any step transitions at all anticipated or that recently happened, then we're looking at what are the most critical pieces of your organization that maybe there's a lot of steps, and only one person knows, because we talked about cross training. But I mean, we're humans, we can't retain everything about someone else's job. Well, we're also doing our own job, right? Like, that just doesn't happen. So I would look at the jobs that only one person really knows how to do this. And no one else really has any insight that would help carry them through a day of doing that. And then start start there. So you also might want to look at donor stewardship and depositing checks and all of that type of thing. But those are the two biggest scenarios, I was looking at changing staff, and the situation where only one person knows it.
[Sami Bedell-Mulhern] Oh, that's such that's such good stuff. And I think too, one other thing that I'll add to that is a tip that was told to me was to video, record yourself doing the task, even something like how I go through my email and what I work on right away versus what gets sent, you know, whatever, even just really recording yourself doing something, right, can pull out the things that you do inherently that you don't think about, that you do as part of your process.
[Roxanne Fry] Yes, so if you're screen recording with a transcription service, that's the best because you literally talk through what you're doing. The other thing is I'm thinking about recording, you know, you're clicking here, you're clicking there, I would be cautious about putting things into a knowledge base that are easily learnable or bookable if that's where he's easily able to Google because the word now and I say I say this mostly with Microsoft products as an example, word if you don't know how to do mail merge. Now that doesn't need to go into the knowledge base. That's a skill that anybody can learn by watching a few videos. But I would not necessarily go through the process of click Mail Merge click letters, click this. You could put best practices is to click edit individual documents, check and make sure but really kind of look at putting into the knowledge base what is unique, perhaps to your organization, how you do things. Everyone uses the mail merge functionality at the same All right, there's nothing really unique about that process in itself, here's how to run labels. So just kind of try to make that distinction as well.
[Sami Bedell-Mulhern] Okay, so we've talked through how to kind of what a knowledge base is, what types of things need to be in there to kind of where to start with it. But one of the things that I know all of my ops people will will care about is the number of people that have their hands in editing this and putting the actual finished product into the knowledge base. So do you want to have like a main point person who's responsible for creating all of the content but for managing how it goes in and, and the editing so that things don't get muddied? Or is this just like a true group effort, and everybody just kind of has free rein to make changes? No, it's
[Roxanne Fry] not a free for all. Definitely designate one person is the owner, and another person is the backup. If you have everyone editing, you just quickly lose control over even how things are phrased. So for example, don't put in your knowledge base, then Sammy does this and then Roxanne does this. And then it goes back to Sammy, instead use positions or roles. So you might say, the gift processor does this shares it with the accountant or the bookkeeper. Otherwise, you will quickly have an out of date, knowledge base, because even if people don't leave, they might change positions. And then it's become chaos within your Knowledgebase. So you definitely do want to focus on roles and positions versus people. And then having one person in charge and someone as backup, I would also have staff members, you could collect this in a Google Doc, if you want everyone add their own procedures to a Google Doc. And then the person in charge can you know, paste it into notion or Google site, whatever that looks like. And again, I always recommend bullet points, not paragraphs. Unfortunately, we have a limited attention span these days. So anything that you can put in bullets and headings, we all know that that's easier to read.
[Sami Bedell-Mulhern] Yeah, no, that's a super good tip. And I love that and I knew that's what your answer was going to be. Because because I think I agree, like, you know, we all have our own little, we all have our we all own our own work, but it needs to be consistent for the sake of the organization inside that knowledge base. So once we kind of start to put things in here, because you did mention, you know, maybe roles change, or you might add new positions and whatnot, how often should we be hopping into our existing knowledge base to kind of review it and edit it and kind of cleaned up some of our systems.
[Roxanne Fry] I would say anytime you have a major staff transition, such as operations person, or maybe the person who's handling all of your gift entry into your database, your gift receding, that's always a good time to review. Other than that, I would probably break it into sections. Let's say you break it into department, maybe development and operations, you know, Client Services. Other things in review, one of those quarterly is that means each one's being reviewed once a year, kind of like when you say you cleaned zones in your house today, overwhelmed with doing it all at one time. So that would be the best practice is to, you know, keep in touch with that. And then anytime there's a transition, that would be the best time to have someone who doesn't do it normally sit down with the person who does it, make sure that all of the directions are, you know, up to date. Other things that change to you know, might be that your board requests a different type of report that you can save in your, obviously in your database, but maybe they want to present it in a certain way. Or the reason that they want it. That's the other thing that's helpful in a knowledge base is not just here's what we do. But here's why we do it. So that if someone new comes in, they might say that's the dumbest thing I've ever seen. Why are we doing it that way? An explanation might include because of the state law or because of, you know, conflict issue that's arisen before or something like that, then at least you know, and then you can address Oh, did the law change? Did the circumstance change, but if you don't know why someone's doing something, your documentation really lacks an entire dimension to it.
[Sami Bedell-Mulhern] Yeah, it's like you, when we talk about the data that you collect for your organization, it tells a story. So if you're not collecting the data to tell the story you need, you're not going to be able to make decisions based off of off of that. So would you also then, on the tech and software side of things, for example, add in this, you know, we chose this tool because, you know, integrates with this the cost XYZ, like would you make sure to put all those qualifiers that kind of stuff in there too.
[Roxanne Fry] I would put bullet points in there because let's say someone new comes in like That's the craziest database I've ever have seen, and then they go to pick something else, right. But if you put in the just bullet points of you know, it does this, it does this, it does this in priority, because not every software platform is a silver bullet for what you need. So you have to prioritize what's really important because this new database might do X, Y, and Z. But those aren't nearly as important as a, b, and c are to that specific organization. So I think that's a, it's a really good point of things that can go in the database. Another thing I'm just going to raise I know some organization have SOPs, standard operating procedures, documented in Word docs, or even in Google Docs. So the challenge that I've seen with those is, you might have 47, different SOPs. And while you can link from one Google doc to another, it's not as easy in Word, you can link but you're not able to see how things interact as as a whole. Right? So when you see things in a Google site, and it looks kind of like a website, right? It's an old intranet for those who know that word. And it's just becomes easier because people are much used to materials to viewing things that way and go, Oh, here's my department, here's this, especially if things cross over by department and functionality within the organization. So if you have, you know, 1520 47 SOPs, it's awesome that you're documenting all of this, but to see it more concisely, and it's a big picture, you really might want to consider getting it into a Google site or notion, or whatever the case may be. No,
[Sami Bedell-Mulhern] I love that too. Because if you have too many Google Docs, you get lost in where you were and how to get, you know, you don't have like that nice table of contents that you can kind of just go back and forth and see.
[Roxanne Fry] Exactly, exactly, yeah, it just seems to make editing easier, right? If you have everything in one place versus in, you know, so many different Google Docs or Word docs. And granted, you could put everything into a Google Doc. But you're scrolling an awful lot to get to where you need versus being able to click a navigation bar that you create based on the information that you have in your, in your knowledge base. Well, so like, let's
[Sami Bedell-Mulhern] let's talk about usability and user experience and kind of team culture around a knowledge base, because it's great to put it all together. But if nobody's utilizing it, wasted effort, right? So for people that are listening to this, and they're just like, well, we've tried doing that nobody used it like, how, how can we encourage our teams to always continue to reference this? How can we make it easy for people to find it? Like how can we kind of create that team culture around knowledge base is where everything is, and you should care about it as much as everyone else, because it just helps everybody do their job better? Because they kind of know how what they're doing is impacting other departments or other staff members?
[Roxanne Fry] That's a great question. I think that the person can either be the person who manages it, or someone else on the team who's kind of a rah, rah cheerleader person to get people on board with using this is that whenever they're asked a question, say, you know, here, I'm happy to help. Here it is in our knowledge base, just give them the link, right? And then they can go there, they might at the same time, go, oh, I went to that link. And this is outdated, like, great. Let's update it. So it's a it's a wonderful way to keep that in front of people. It's also extremely helpful during staff onboarding, could be for board onboarding, as well. versus you know, everybody learns different. Some people learn better face to face, some people will like watching a video some people don't like reading, but it's a great resource to point your new hires to, like here is our, you know, employee manual. Here's the board roster link to Dropbox perhaps. And someone might say, Well, why do I need to put a link to Dropbox? I can't, can I just go to Dropbox. And the point, again, is that you don't have to search three different places I don't have to search, figure out where it is in Dropbox, I can just go to my knowledge base and go, Oh, here's the current roster for the board. Here's their bios, whatever I may need, it helps your grant writers, everybody. But if you can start to encourage people to say, Yeah, here it is. Here's the password for the guest Wi Fi. I mean, it takes some discipline, because it would be so easy to just say, here's the password. But if you start pointing out what's actually in the knowledge base that people can find it really helpful. Ein, oh my gosh, how many times do you look for the EIN right? So you can have a sticky on your computer with the EIN then you're risking typing it in every time potentially making a mistake, or it can be on your homepage on your knowledge base. That is maybe your Maybe that's your homepage or your browser and you just click there, double click the EIN and paste it wherever you need to do again, eliminating the possibility of human error and making sure some place where everyone can reference it if they need it.
[Sami Bedell-Mulhern] So well and what I love about that is if if you're pushing everybody to the knowledge base, and you have a team environment where it is being edited and taken care of, then you also know that your team is working off of the most current and accurate information, right? It's not a PDF that somebody downloaded onto their desktop that has been changed five times. So because that's where they always go, they're using and sending out older information.
[Roxanne Fry] Exactly, I think it can be really overwhelming sometimes just to say, Okay, I'm gonna build a knowledge base, and I have to review it quarterly, and I have to keep everything perfectly up to date, I think we all just have to realize that it is an evolving tool, it will live and grow with in your organization. But it's, if it's considered the most up to date, that gets rid of, oh, I sent them the old PDF that talks about our services, and we don't offer the program that's a PDF anymore. Right. So it this ties into so many different things like consistently naming your document so that when you link to it, you know, per board roster, whatever that looks like, you're pointing to the most up to date version, and everyone knows exactly where to look, look at for that.
[Sami Bedell-Mulhern] Yeah, and so I think it takes us as employees of our organizations to start to just maybe challenge your staff what document to things that you did this week, and then just kind of build it from there, right? Like, it can be a slow, slow roll, but can make make a big difference. Right, you could
[Roxanne Fry] even make it a part of your standing agenda for your team meeting, that everyone is in charge of documenting, like, is it to two processes a week, or even one, and then they come to the staff meeting, and they report on which processes they documented and submitted to the knowledge base manager, I'm gonna call that person, the manager. And then there's, there's becomes accountability with that. And accounting, like an accounting department, they often have a lot of checklists, here's what we do every month, right? That can be in the knowledge base easily. If you needed to, you could print the checklist and check them off if you want. Or you could, you know, screen capture, change it to PDF and check them off every month, or whatever that looks like. You could have one rolling pdf of all the checklists for the whole year showing that you did them in one PDF. So accounting is a great place to start because they live in checklists, whereas development directors, that department is more kind of going with the flow, they don't have a standard checklist for a lot of things, because each donor is different. And history is different things like that. But there are still processes in development that can and should be captured in a knowledge base, especially regarding stewardship. Here's why we do this. Here's what we do. And here's why we do this.
[Sami Bedell-Mulhern] Okay, so one of the last things that I want to touch on here, because I think, hopefully, this will convince you that you need to put this into practice, is because you brought up team meetings and like, you know, let's work on one process at a time or what have you. I'm sure you've had this experience with your with your clients, where it's like, hey, everybody worked on a process, you come together, and you talk about it. And they're like what you're doing that I was doing that or I'm doing this, you're doing that way. So like, as you're kind of putting this together, it can be a really big time saver for you in the long run, right? Because not only are you protecting yourself with staff turnover, or illness or vacations, you can also kind of streamline maybe some of your systems that you didn't realize were being done in so many different ways were by more people than they need to
[Roxanne Fry] write that not only that point. But along the same line is if you're documenting everything that this person does, and then your organization grows to the point where they need help in that departments, they hire another coordinator, right? It's easy to say, Okay, here's what this person's doing. Let's take these portions out and move them to this other person's job description. Yeah, it just makes so much sense to be able to do that rather than guessing. And going well, this is too much as too little. What is it? No one even knows what that person does. Right? You have the processes documented, you can see exactly what they're they're doing for sure. And then also, like you mentioned, duplication of effort, and also how things take team together. So Person A may say, Well, here's what I do. And here's where I end. And the next person's like, oh, hold it. If you'd have done this part a little different. My job starting here would have been so much easier. Can we make that adjustment, and there's small tweaks that can make the workflow as a whole each piece of it go together much more smoothly. The whole goal of having a knowledge base is to help your team ease frustration. So they're not constantly searching for something or wondering why something comes to them the way it does. Well, that's part of the process. Should we change the process? And also just you're creating more time you're saving time to spend that time with the people that you want to serve your donors and your clients.
[Sami Bedell-Mulhern] That's so good. Well, I'm a huge fan of knowledge base. It's on it's something I'm currently working on in my business. And I know that we work on some clients together and in the ones that have these things set up, it's so much easier to kind of function and work, especially as you're bringing in consultants for certain things or hiring staff, I think it's such a critical thing. So I hope that this has inspired you to start working on it. Or if you have one that's kind of collecting dust somewhere on a shelf that you can go back to take a look at it and review it. Ruxin as people are kind of starting to build these out, is there any kind of last words of wisdom or you don't know what you don't know, that we might want to think about? As we go down
[Roxanne Fry] this process? My number one recommendation is to start, if you put it off until the circumstances are right, or you have someone dedicated to do it, or you have two weeks of the time, free time, in the summer, that won't happen. I do have a knowledge base for myself, which is really, really helpful. I have different versions of my bio that I want for different things, I have all kinds of different things that are captured in my own personal knowledge base for my business. So just start picking areas, like I said, look at those couple of examples of staff transitioning the person who knows the position that only one person knows, get started, you know, at least start you can always add into it. You know, what do they say, you know, you're never going to reach perfection really shoot for good? Or great, and then you can improve down the line. But get started. That's my number one recommendation.
[Sami Bedell-Mulhern] Yeah. And I think you could probably Google knowledge base examples, and some other people's will show up if you if you want some examples, right?
[Roxanne Fry] You can. There's a lot of articles out there about what to include in a knowledge base. So that might expand a little bit and just what I've been able to share in the short time. But keep in mind, what are the goals you want to streamline, make things more accessible, make it easy on your staff and serve your clients that don't have there's more so if you focus on that, you'll start to find processes. It's amazing how many processes you'll find once you start digging in?
[Sami Bedell-Mulhern] Well, Roxanne, if people want to connect with you get to know you more of the services that you offer? How do people do that?
[Roxanne Fry] My website address is rocks star solutions.com. And I know Sammy can share that when she says this online. But LinkedIn, you can find me at just at Roxanne Frye, and my email, everything is there. So I'd love to hear from you. If you have questions about how this would look, what does this mean for your organization where to start? I'm happy to help. Yep.
[Sami Bedell-Mulhern] And we'll have all of that linked up in the show notes at https://thefirstclick.net/242 to make it easy for you to connect with Roxanne I highly recommend that you do because she's amazing. Roxanne, thank you so much for being here today. Thank
[Roxanne Fry] you, Sami, this was so much fun. I geek out on this topic. And I love helping nonprofits in this area. Thank you.
[Sami Bedell-Mulhern] Big shout out. And thank you again to Roxanne for joining me on this episode. You know, I love the action steps that she gave you in the way that she made it super easy for you to know, where do you start? What projects do you start on? Who do you start this project with who's in charge all the things that makes it easy to just kind of get going and like she said near the end just get started. It can be an overwhelming project, but baby steps a little bit at a time and you'll be well on your way to getting all of your processes set up and ready to go. So again, the tools that she mentioned some other resources, you can go to https://thefirstclick.net/242 to check all of those out. For now, thank you so much for spending a little bit of time with me and letting us come into your world for these trainings. You can subscribe wherever you listen to podcasts or on YouTube so you don't miss out on a single episode. And we do have bonus episodes that are continuing to come out throughout 2024. So I hope you'll check them out for my friends who have podcasts as well with additional resources that can support you and your organization. So subscribe and leave us a review while you're there, if it makes sense so that we can really get out there in front of more and more nonprofits that could really use some help with their marketing and their systems in order to increase their impact. Thank you so much for listening, and I'll see you in the next one.