MBA1044 How to Create a Team Handbook For Your Company

Hey. Oh. Welcome to the $100 MBA Show. Bite sized Business goodness every single day with our daily 10 minute business lessons for the real world. I'm your host, your coach, your teacher, Omar Zenholm. I'm also the co founder of the hundred dollar MBA, a complete business training and community online over at 100mba.net and in today's lesson you will learn how to create a team handbook for your company. A few weeks ago I attended the Running Remote conference in Bali. Had the pleasure and the honor of sharing the stage with some great speakers. I spoke about how to motivate your remote team. But at that conference I learned a ton from other founders from other companies. I got a lot of takeaways and one of the takeaways I want to share with you is from GitLab's co founder, Dmitry Zaborjic. I've been practicing that last name, but Dmitri is a great guy. I got to know him at the conference and his speech was all about Getlab's team handbook. And I want to share with you how you can create your own team handbook even if you have a small team. How you can do it with minimal work, get your team involved and how it can be a great recruitment tool for future hires for those who are thinking about working for you. A handbook can be extremely useful for somebody who's joining your team right from the start. They can basically search any term for any question they have and get answers immediately rather than asking somebody. They might be embarrassed or maybe they don't want to waste somebody's time, but sometimes they will ask somebody and I'll tell you how the handbook comes into play when they ask teammates. So instead of just going to conferences, learning and keeping all the learnings to myself, I want to share it with you because we're going to be creating our own team handbook at our team. So I'm super pumped about doing that for us and sharing with you the process on today's episode. So let's get into it. Let's get down to business. Today's episode of the $100 MBA show is supported by Podia. Podia helps thousands of creators earn money from their passion. It's an all in one digital storefront that you can sell courses, memberships and digital downloads in one place. It's the most creator friendly platform on the market with zero transaction fees and a super friendly 24.7life support team no matter what plane you're on. So they're gonna take care of you even if you're just getting started. What's great about Podia is that it eliminates all the technical headaches. It takes care of every aspect of selling your course or membership or digital download. If you've got video courses, they do the video hosting for you. If you want an easy way to charge your members on a reoccurring basis for a membership, Podia takes care of it. You want a secure way for people to download your products. When they pay for them, they take care of that too. They also offer free migrations on their shaker plan. Best of all, Podia puts their money where their mouth is. They have a 30 day free trial with no credit card required. So if you don't love it, you don't pay a penny. If you're looking to start a online course, sell any kind of digital product or start a membership site, check them out and support the show by going to podia.com mba that's p o d I-a.com mb so at the Running Remote conference, Dmitry from GetLab, the co founder of GetLab, shared the story behind how they built their team handbook. And he talked about how, you know, sharing information about how a company does something, whether it's how many leave days you have, do you have maternity leave? What's the process? If I want to go on vacation, if there is an emergency I have to attend to, who do I speak to? All that kind of procedural stuff is quite easy to discuss and share with others when your team is small, when you have 1, 2, 3, 4, 5 people on your team. But as you start growing from five to 10 people, it starts to get harder and harder. And GitLab is growing. They have 300 team members and counting. So when somebody joins, they need a central place for them to go. If they have questions somewhere they can find answers. Enter the team handbook. So they started creating this handbook, but instead of having somebody in charge or a team of in charge creating a handbook and then disseminating it to the team, they made it a collaborative effort. They created a simple site, a wiki. Actually, if you're not familiar with the term wiki, it's basically a site that other people can edit, not just the admin, just like Wikipedia. So they created this wiki and they gave access to everybody on the team to edit it. So it became a running document. It's always in draft. He even said that at the speech, you know, our team handbook, even though it's established and it's well known, it's still in draft. Things change. What you see in the handbook today may not be there tomorrow. And it's not the responsibility of one person or the CEO to write this handbook. The whole team writes the handbook. And what happens is when somebody asks a question, say for example, a new hire asks a question, how many days do I have for maternity leave? Somebody on the team might have that answer because they went on maternity leave. And they will write that answer. They will actually add it to the handbook and then refer that answer that's in the handbook that they just wrote to the person that just asked it in Slack or in their communication tool. So that way there's a record of that answer and a reference to the answer. And as the days went on, as the years went on, that handbook got bigger and bigger and bigger. In fact, if you printed out this handbook, it would be over a thousand pages. But what's so great about it is that there's a search bar and you could just search for anything and find your answers. And if it's not there, you can add it. If you are part of GitLab, this handbook has made a lot of waves and a lot of people know GitLab for this handbook. In fact, when you type GitLab in Google, the first thing that comes up as a suggestion is GitLab handbook. So how can you create one for yourself? Well, I'm creating one for our team. Well, I should say we are creating for our team because again, I'm not going to be writing it myself. The whole team's going to be writing it and contributing to it, editing it, changing it. So the first thing you need to do is get your technology straight. Number one, the easiest way to do this is to create a WordPress website and just choose a theme that has some sort of help desk or knowledge base theme. Sort of like what you would go to if you're looking for tutorials for a product. You could buy a theme or there's some free themes out there. You could just search Google for knowledge base or help desk theme. This is going to be the easiest way for you to do this because normally a help desk or knowledge base theme or website will have a search bar on the homepage and people can search for terms, search for topics, and then you can list the topics or the categories on the homepage. This is going to be like set up automatically because the nature of this theme. Now, if you're not familiar with WordPress, it's pretty straightforward. We recommend WP Engine. You get 20% off if you go to wpeng.inmba and use coupon code WPE20OFF, you can install WordPress in about five minutes and find a theme in their directory for free. Or, or you can buy one. Where we recommend is ThemeForest. ThemeForest is a great way to buy premium WordPress themes. So once you install your theme, you get your WordPress site set up. It's a knowledge base now. Now you need to add some articles. So I would recommend by writing the first article, any piece of information you think would be helpful. It could be like your values, your company name, your company's values, and that could be your first article. Now once you have your first article up, you now need some contributors. You need people that can write new posts or new articles for this new team handbook. So you could just literally make everybody on your team a user. They don't have to be admin, they just have to be user where they have edit and read access. This is very simple to do on WordPress in the settings page. And if you need any help, the friendly folks at WP Engine can help you out. And from there I write a second article, but this time I would video capture it to do a screen capture using QuickTime or whatever screen capture software you use on your computer. So you can share with your team how this is done. They log into the WordPress site, show them how to create a new article, how to publish it, done deal. So you can install this website on a subdomain. So for example, with us, webinar ninja.com, we are going to host this in our subdomain of handbook.webinar ninja.com and this site is going to be public. This is the beauty of the handbook. You can write a little blurb in the beginning of the handbook on the homepage that, hey, this is always in draft. And you can take a look at what GitLab writes. And it's very simple. Say, hey, this is a running document that we create as a team. But this is what we're all about. This is our handbook. These are our rules. This is what to expect if you are thinking about working for us or working with us is what I should say. So. So when people are searching your business, when they see a job opening and they're doing a little bit of homework, they know what to expect and it gets them excited to work for your team. Now, GitLab is not the only people that do this. There are plenty of companies that have public handbooks. You could check out Basecamp's public handbook. Their handbook is hosted on GitHub. It's not really a public website, so to speak, but you still can read it. But I really love GitLab's open creation, open collaboration with the team. That model is great and it just doesn't make you feel like you have the burden of writing this whole thing by yourself. The whole team cultivates this handbook together. I got more on creating a team handbook for your company. But before that, let me give love to today's sponsor. Building online courses, memberships and digital downloads is a great way to earn money by sharing your knowledge with others. But a lot of these tools out there are so complicated that it's a headache just to get started. Podia eliminates all the hassles. It handles your sales page, your email marketing, your payment processing, your content hosting and delivery all in one gorgeous designed package. It gets out of your way and makes it easy to create and sell. Best of all, unlike the competition, Podia takes zero and we mean zero transaction fee. So you actually keep what you earn. I love what Putty offers. The ease to sell your courses, your products and your memberships while looking gorgeous. And it's super simple to get started. Their customer support, top notch and they believe in their products so much that they give you the first 30 days totally for free. There's no commitment and there's no credit card required. Just try it and if you love it, just hang on. If you don't, you don't pay a dime. So there's no excuses. It's never been easier to get started and make money from your passion. Join over 10,000 creators and start selling today with a 30 day free trial at Podia. Just go to podia.commba to get this offer again. Go to podia.commba that's Podia P O D I A.com MBA to wrap up today's lesson, one of the most important things you're going to have to do when you start creating this team handbook is you got to get your team in the habit of of contributing and announcing. If you just say, hey, we're creating this team handbook. Here's a few articles, here's your access to edit. This is what you're supposed to do and you just leave it and never touch it again and never talk about it again, you're asking for trouble. What you need to do is reinforce the fact that you need to be contributing and announcing. So every time you add to the handbook, you gotta ask them, hey, please announce it in the chat, announce it in our, you know, team collaboration software and it can happen organically or you can actually give them a nudge. So say for example, one of your colleagues is asking for vacation leave and they are applying for leave. Say, hey, can you add this procedure in the handbook before you go on leave? And make sure you announce it. So it's like a just in time contribution to the handbook. You do the same when you think of something. When you have a procedure that you want to add to the handbook, add it, announce it, make it clear to the team that it's everybody's job to, to create this handbook together. This is awesome because it creates a sense of unity and also creates a sense that, hey, this is our company, this is our team, and everybody's responsible for creating a great environment and a great handbook. One thing I want to add is that once you start having a few articles, 5, 10, 15 articles, you may want to start creating some categories. Categories are very easy to create in WordPress and that way on your homepage of your handbook, you, you could see different categories you could search for or you can browse through. And one last thing, if anybody ever asks you a question and the answer's in the handbook, well, if you don't know the answers in the handbook, check the handbook first and then refer to the handbook. So instead of just giving them the answer, like if a developer asks, what's the procedure for submitting code? Instead of just giving the developer the answer, say, hey, check the handbook. It's in there. I wouldn't even give them a link. I would just tell them to go and check so they can get used to searching for answers in the handbook. You can follow up and say, hey, if you're having trouble finding the answer, let me know. But it should be pretty simple. That way you kind of give them an out that, hey, if you still are confused and need to help, I can give you an answer and help you out. But you want again, get them in the habit of going to the handbook, because what will happen is that they'll find their answer, but maybe it's not exactly what they're looking for. Maybe they need more information and they'll get back to you and say, hey, this is what I found in the handbook. Actually what I'm looking for is this information. You say, oh, okay, that's missing in the handbook. Great, your answer is so and so. Add that answer to the handbook. Well, there you have it. That's today's lesson on creating a great team handbook for your company. I want to thank Dmitri from GitLab for that great advice. Shout out to you, my man. Great speech at running remote and great work with GitLab, your team, and your team Handbook. Thanks for the inspiration and the great idea for us to implement it in our company. Thank you so much for listening to the 100 RBA Show. If you haven't hit subscribe, make sure you hit subscribe now so you don't miss an episode by hitting subscribe. You get all our episodes automatically. That way you don't miss a beat. Before I go, I want to leave you with this. Admin can sometimes be boring. You probably think, oh, team Handbook. That's. That's a lot of work and that's a lot of writing, and that's just not sexy. This is what I love about this concept. There's so little writing that you have to do. Everybody pitches in, so it's not, you know, a laborious task. And as your team grows, as your business changes, this is going to be a running document that changes and updates, and different people will add their contribution. I want to emphasize, don't worry about being perfect. Don't worry about having the perfect document. This is a draft, and it's always going to be a draft. And there may be a few typos, but that's okay. The benefits of this handbook way outweighs the few typos. All right, I'll check you in tomorrow's episode Q and A Wednesdays, where we answer your question right here on the show. I'll check you then. Take care.