Tribal knowledge and process building
Hi, I see SMB founders and buyers here, on other forums, and in the real world talking about the risks and downsides of undocumented (or poorly documented) processes creating key-man and tribal knowledge problems. But, I also see many of the same folks not following through on solutions, or following through in "band-aid" ways that stop the immediate bleeding but don't have long-term legs. I've spent the last 20 years developing, optimizing, and codifying processes for companies of all sizes, but I would really prefer to focus on SMBs where the effort can show real results rather than just gathering coffee rings on somebody's desk or checking a spreadsheet box. But, it's a tough task to connect with SMB owners who are actually serious building processes that give up some control and can scale. So, to the SMB owners in process-driven niches here, how do you view key-man and tribal knowledge risks in your operation? Do you actually struggle with the idea of that knowledge walking out the door or keeping you from taking a sick day now and then? Or, is it mostly just low-intent internet complaining from tired owners who are venting rather than expressing a real desire for change? If you had a genuine desire to develop codified, maintainable, documented, scalable processes, how would you do it? Would you figure it out on your own, would you prefer to engage somebody like me who's been around the block, or would you pursue something else? If you'd likely engage a consultant or a fractional, how would you find the right candidate? Thanks!