And me without mod points today. Mod this up!
At a prior gig, I introduced the IT manager to a wiki. It was free software which ran on a Windows server (they were an MS shop). At first, he didn't see the value in it. I started putting stuff in there. He'd come ask me something. Have you checked the wiki? Uhh ... oh ... yeah ... there's that info. He quickly saw the value in it and started using it as well.
Fast forward a few months. We hired some more IT folks. We quickly discovered what was poorly- and well-organized. It became a rite of passage for new folks to hit the wiki to find stuff and, if something wasn't there, someone with more experience would help them write it up. New folks quickly came to see the value in it and contribute to it. Stuff got doc'ed, widely, and well-used.
Fast forward a few years. I'm at a new gig. I'm trying to learn my way around the infrastructure and the coding standards. Oh, go ask so-and-so about that. Are there no docs? Nah, just go ask that super-busy person who is juggling the jobs of three people.
We had a wiki (mediawiki, no less) but it wasn't getting used. I used it. I wrote stuff up. More new hires, interns, etc. They're being told "oh, check his wiki page; he's got a ton of stuff linked from there." They start doing the same. It's become a running joke. Can anyone tell me how to do such-and-such? Yeah, I have a page about that; try not to act surprised. After about a month, they're not surprised; they're laughing along with everyone else.
If only one person in the organization knows how to do that task, that task has Bus Factor = 1 (only one person needs to get hit by a bus, or otherwise rendered unavailable, before your organization suffers). A good wiki, where it's easy to write clear docs, and search them 'cuz plain text, can quickly take any task to Bus Factor = infinite. If you want your organization to thrive, you need the Bus Factor as high as possible on everything.
Anytime I have to wrestle with how to do something, I doc it on the wiki. If I need to do it again, next week, I might remember how to do it. After a couple months, it's good thing I doc'ed it. Eagleson's Law says that any code you wrote, but haven't touched for at least 6 months, might as well be written by someone else. It's been flushed from your short-term memory. If you have a mortgage and car payments, cut that number in half. If you have a significant other, cut it in half. For each kid, cut it in half. Pretty soon, you're lucky if you can keep stuff in short-term memory for a week at a time. Spending 5 minutes putting it on a wiki page, which you can find when you need it, will save you a lot of "wrestling."