grow your wiki
When ThreadMode is allowed to continue for too long, it becomes unwieldy. There is no coherent expression of the page's topic, instead readers have to dig through the whole thread and distill the valuable information out of it. The result is ThreadMess.
The page looks like a discussion thread, consisting of chronological submissions of responses. Valuable information is fragmented across the page within the responses and there isn't consensus from the community about facts and opinions. It is difficult for a casual reader to discern any clear, useful information from the page.
Reorganise the page into a single document, grouping related information together and replacing the signed, conversational remarks with unsigned objective prose.
One effective process for refactoring a ThreadMode page to a DocumentMode page is:
There is a danger in refactoring ThreadMode that the bias of the editor can (consciously or unconsciously) sneak into the resulting page. Often, the best person to refactor a ThreadMode discussion is someone who has no interest in, or opinion on the matter being discussed.
Wikipatterns.com is sponsored by Atlassian Software, creators of JIRA, Confluence, Bamboo and Crowd
Designed by Headshift Ltd
The anti-pattern is not the Discussion, also known as ThreadMode. It's more that the page is never converted from the discussion. Wikipedia pushes the discussion to separate pages but it's still important to have the Discussion. This is a Pattern, not Anti-Pattern.
CommunityWiki is trying an experiment currently called PageMaintainer. http://www.communitywiki.org/en/PageMaintainer
I've renamed this page, because ThreadMode itself is a useful adoption pattern: it's only when ThreadMode is allowed to run wild that it becomes an AntiPattern. I got the name ThreadMess off Meatball Wiki, it seems to fit.