[picodguyo]

Hard disagree here. In practice, corporate wikis are always graveyards of outdated and incomplete information. The process usually looks like this:

1. Someone is excited about a new project and creates a wiki page with a lot of aspirational introductory content and a sketch of the rest of the page with TBD everywhere

2. Author gets busy on other things, leaves the company, or the project quickly diverges from the original vision

3. The original page stays in the wiki, adding negative value

[Dudeman112]

Documenting is like exercising or eating healthy: doing it an average of once per month isn't worth crap.

It's not a problem with documenting stuff, it's a problem with corporations. Somehow very few companies have technical writers whose main job is keeping their docs healthy.

[Aeolun]

I think this strongly depends on how much time everyone spends on the wiki and how much love it is given in the first place.

I’ve had companies where it is exactly as you say. Which is especially frustrating because a search for the term you need yields 19 graveyard pages and 1 actual result.

But also companies where the wiki was a bastion of well kept and up to date information.

What I think it mostly comes down to is structuring. If you have little wiki fiefdoms, where every project gets it’s own page, and nobody gets to edit other projects, then you quickly end up with huge heaps of garbage.

If there is one space that the entire company has access to, which is well organized, it’s much easier to get rid of (or restore) information.