Why not wikify Documentum documentation? Say that three times fast. When you're done, try to answer the question. Why shouldn't the experiences and revelations of Documentum developers be assimilated? If you can't think of a strong reason why not, ask Mark Lewis (Lewis_Mark@emc.com), the president of EMC Software, what his might be.

Wikifying Documentum isn't my idea; it belongs to  Craig Randall who leads EMC's Content Management and Archiving Architecture group. He's sure that a wiki makes sense.

Frankly, it's hard to argue with the Wikinomics, We Are Smarter Than Me  model. The biggest danger, I think, would be a shortage of contributions from knowledgeable participants, and EMC should be able to manage for that by encouraging its best and brightest  employees to help build the knowledgebase.

And sure, there is the documentation that comes with each release. And, there are developer user groups, but they're not the same as a wiki and they rarely attract top talent. In fact, I've seen just plain wrong answers posted and accepted, no questions asked.

And those wrong answers, sometimes they become gospel among the less experienced, (or less intelligent) developers; there's a communal problem to that. Projects get delayed, canceled or they just plain fail. Management searches for cheaper/easier to use solutions (a la Sharepoint). And jobs, they go away or they don't pay as well. And that's bad for everyone.

Call Mr. Lewis. Tell him to wikify Documentum now!