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.

> On the other hand, a number of businesses still pass around Word Documents like the internet hasn't been invented yet. Tell me this, which is easier to collaborate on. A Group-Blog hosted on Wordpress? Or the 20 copies of a Word document that your office is passing around by email?

You won't find in me a staunch defender of collaboration via Word documents (or of Word in general). However, the fact that Wordpress and Word share a relatively small use case doesn't mean Wordpress is a viable Word replacement, otherwise I'd point out that you could just as well setup a private Git repo and collaborate that way.