Barron Home Services waited too long to build a central database for their processes. When they finally did, they had to retrofit everything and spent extra hours scaling roles. The founder says process documentation is easy to skip but essential before you grow.
Tell me a little bit about some of the things that you shouldn't have done. I want to hear about a specific example. What was the valuable lesson you learned from it?
A lot of the missteps that I've experienced are usually involve waiting too long. For example, we have had ideas on how to create a central database for processes to be stored and to be edited. But we waited too long. We had to catch up and have people spend time versus creating a system. And it's funny, a process for capturing processes is important. Those are the things that you don't think about. And then when you think about em, you're like, how we're probably okay. And then you get six months down the road and you go, crap. We need to scale that position by three people, right? How are we going to do that? And we didn't do it quick enough. We didn't have a process in place to scale the process. Looking back, that was one thing that I definitely wish I could have done.