Property Management is hard until you build systems like this

Every year I take the entire month of June off. No Slack, no email, no phone calls, and nobody on my team checks in with me. 4 years running now and nothing catches fire. I'm Peter Lohmann. I run a property management company in Columbus, Ohio. 720 doors, 35 employees, and about $3.4 million in revenue per year. For years, I took pride in being the most important person in the building. But if the company can't run without you, you don't have a business. You own a job. I'm an engineer, so I rebuilt mine like a machine and took the jobs with my name on them from about 40 down to 4. It runs on 3 systems, and I'll show you all 3 on screen so you can build them yourself. For years, there were 3 reasons this company couldn't run without me, and each one of these systems takes one of them off the table. One, I was the only person who could see the whole business at once. Two, every task ultimately landed on me. And three, I was the answer to almost every question anyone on the team had. So let me walk you through all 3, and I'll put each one on screen as we go. The first one is the scorecard. It's what used to make me the only person who could see the whole business at once. It's a spreadsheet, nothing fancy. 8 to 12 of your most important numbers, and every number sits right next to its goal so you can tell at a glance whether you're on or off it. Next to that, the trailing 13 weeks, so you're reading the trend. We also document on the spreadsheet who Who's responsible for that metric? We update it every week, and the entire leadership team reads it together in our weekly meeting. That weekly read is where the leadership team runs the business. If a number is off its goal, we see it that week, talk about it that week, and somebody owns getting it back on track. Nobody waits for quarterly review to find out something slipped a month ago. The test for what earns a spot on the scorecard is simple: these are the numbers you'd want to know if you were stranded on a desert island. and could know only a handful of things about your business and nothing else about your company. If it doesn't clear that bar, it doesn't belong on the scorecard. To give you a feel for it, a few of the numbers on mine are median time to turn, total occupancy, how many work orders have been sitting open past 30 days, our client and tenant satisfaction scores, and team happiness. Your list will look different than mine, and that's fine. The win is that the whole team steers by the same numbers, each one sitting right next to its goal. Before we had this, nobody was aligned on what mattered or even what their goals were. Every person in every department was chasing whatever they personally thought was the most important, and a lot of the time these priorities pulled against each other. The only one with the full picture was me, and everyone else was making decisions half-blind, seeing only their own little corner of the business. One more thing on the scorecard. Mine has grown to 18 rows over the years because once you have one, you want to put everything on it. You don't need 18. Start with 8 to 12 and only add a row when it earns the spot. System 2, the task map. The second system is the task map. It's the one that gets the tasks off my plate and gave each one an owner. It's a simple table. I really like simple solutions. One row for every single task the company does, who owns it, what triggers it, and a link to the page that shows exactly how it's done. It runs to hundreds of rows and it's not the most exciting thing in the world to look at, but it might be the single most useful document I've ever built for my business. Because it's the one place you can see who does what across the entire company in a single view. As an example, one row might be a maintenance work order coming in, and the trigger is the request landing in our system. The owner automatically assigns it to a specific coordinator by name, and the link goes to the page that walks through exactly how we handle that kind of request step by step. Now multiply that by every single thing the company does, and that's the task map. Before it existed, nobody knew who did what. You You'd end up with 2 people both thinking they own the same task, or even worse, a task that nobody owns. And it just became a big mess. Stuff gets dropped. You hear, that's not my job. And everybody does the same thing a little differently. So the quality was all over the place. It was chaos. And you can't take a day off with that kind of chaos in your business, let alone a month. Real accountability is what lets you leave. If every task has exactly one owner and a written way to do it, the work doesn't stop just because you're not there to chase it. And over time, the goal is to keep driving down the number of rows that have your name in the owner column. It works, and I can prove it with one number. When I first built the task map, I had about 40 tasks with my name on them as the owner. 40. Today I have 4: filing our corporate taxes, managing my COO, approving the annual budget, and the truly escalated things like lawsuits and regulatory problems— the calls only an owner can make. That's it. Every other task this company does has somebody else's name next to it, a real owner, and I sleep Well at night knowing it's all being taken care of. Getting from 40 tasks down to 4 is the biggest reason I can step away at all. And it's the thing people ask me about the most. So I sat down and listed every box that had to be checked before I could vanish for a month. It's a free checklist. The link's in the description. Take it and build your own. There's one more system, the one that finally got all this outta my head and onto a page where anyone could use it. The 3rd system is the company wiki, and it's what finally stopped me from being the answer to every question that anyone had. It's a full Notion build-out with every piece of reference information you need to do any job here. It's like the souped-up digital version of an employee handbook combined with like a company wiki. Everything is there from how to submit a credit card receipt to how to handle a tenant lockout. Before Notion, every one of those questions came straight to me all day long. That's the pattern I needed to break as soon as possible. If the owner's head is the only place answers live, the business stops the second they walk out the door. This notion replaced dozens of physical binders, and these binders failed for the reasons everyone will recognize. They were out of date just about instantly, and no one ever actually pulled them off the shelf to reference them. Nobody opens up a binder to figure out how to do their job. On top of that, they were a nightmare to keep current. I'd be up late the night before a new hire's first day updating and printing dozens of pages so they'd have everything they needed for their first day. That same first day page for a new hire now takes about 2 minutes to build out in Notion. When someone comes up to me with a question, most of the time I just answer with a link to the right page. And if they say the answer isn't in Notion, I have 'em sit down right next to me while we build the page in real time. There's no better feeling. The gap gets filled once by the person who hit it, and it doesn't come back as a question again. It stays current too, because everyone on the team is responsible for keeping their part of Notion up to date. The wiki is the backbone of the whole business, and I'm really proud of it. There's a bonus that falls out with all of this. Once everything you do is written down in one place, AI gets useful almost by accident. Anyone on the team can ask Notion AI a question and get a straight answer back without pinging their manager or searching all over the hundreds of pages that we have in Notion. And because the task map lists literally everything the company does, you can go right down and pick off the jobs you want to hand off to an AI agent, and you've already got their instructions. That's a whole video on its own. So let me know in the comments if you want me to make one for you. The real unlock here though is the mindset and the month off is proof. I've shown you 3 systems now. All 3 had to exist, but the hardest change wasn't any of them. It was in my head. For years, I took real pride in how hard I worked and how important I was to the business. I was the guy who knew how to do everything and touched everything. So building a company that didn't need me felt wrong. It felt like admitting that I was lazy. I worried that my clients would be upset that I wasn't the one handling them personally anymore. I worried that my team would resent me for stepping back while they were grinding. None of that turned out to be true. The change that I had to make was seeing that my job was to hand the work to my team and get out of the way. I used to think being the most important person in the building was a win. It's not. A company that runs fine without me in the room is worth more than being the guy that everyone depends on. When I finally brought the idea to my team, they were glad. They were excited for me. They'd watched me build this company from the start, and they figured I'd earned a real vacation. So we tried it. Every June now, I leave for the entire month. On my way out the door on the last day of May, I tell my COO the exact same 3 things word for word every year. There are only 3 reasons to contact me in June. 1, if you quit. 2, if the office building burns down. And 3, if something happens that stops us from being able to operate as a business, like if the Division of Real Estate comes in and shuts us down. Everything else waits until I'm back. Now, I'll be honest, the first June wasn't totally clean. We had some problems. Our health insurance renewed right in the middle of the month, and I got an emergency call from my COO to sign the paperwork so that nobody lost their coverage. A couple of other small things came up that month, and I cleaned it all up my first week back in July. And then because I'm an engineer, I went back and figured out what caused each of them and fixed the system so it couldn't happen again. That was 3 years ago. Every June since then has been completely clean. No calls, no emails. I don't even check Slack. I don't even stop by the office. And that's the point. The month off was never the goal. It's the clearest evidence I have that the system holds. Those 3 systems are what make the month off possible. Building all 3 from scratch is a handful, so I'm gonna be working on that for one of my next videos.