Enterprise wikis are where documents go to die. Enterprise wikis are 'WORN' - write once, read never. (And edit/refactor even less often than never.)
If I want to know what the spec was six months ago before someone changed it, I'll go check the wiki.
There's little motivation to keep them up-to-date. They are usually sold to companies on the basis of feature lists rather than getting the simple shit right. I can't edit Confluence in text/plain any more.
I'm a Wikipedia admin. We actually know how to use a wiki and there's at least some motivation to make shit presentable because even minor topics are going to have a couple hundred readers each month. There's no such motivation in enterprise wiki-land. I can write a long and detailed document, put it up on the wiki and people still won't read it.
However... its no worse than Word documents rotting away for 10+ years.
Enterprise Wikis, while the project is active, are usually kept up to date decently. When the projects die down a bit and enters "maintenance mode", thats when the real trouble begins.
But the update problem happens exactly the same with Word Documents and classical media.
Also, to ing hell with Confluence. Piece of . But its still easier than emailing Word Documents to everyone and getting lost between the versions.
If I want to know what the spec was six months ago before someone changed it, I'll go check the wiki.
There's little motivation to keep them up-to-date. They are usually sold to companies on the basis of feature lists rather than getting the simple shit right. I can't edit Confluence in text/plain any more.
I'm a Wikipedia admin. We actually know how to use a wiki and there's at least some motivation to make shit presentable because even minor topics are going to have a couple hundred readers each month. There's no such motivation in enterprise wiki-land. I can write a long and detailed document, put it up on the wiki and people still won't read it.