Sunday, October 30, 2011

Components of a knowledge share solution

Both at work and at home i've been studying our current toolkit for sharing knowledge. At work I'm supporting our software development, at home I'm looking at a ways to share knowledge to support lifelong education of persons with cognitive disabilities, including formal public education and home schooling. Naturally I'm looking at similar technologies in both environments.

I've summarized a few of the components I'm thinking about in a table. I compared best of breed solutions to the best (not free!) suite I know of and to Google's offerings.

Function

Best of breed

Atlassian Confluence

Google

commentary, notices

Wordpress

yes

Blogger

Q&A

StackExchange

no

no

collaborative hypertext document

TWiki?

yes

Sites

PDF, other

FTP/HTTP server

yes

Docs, Share

Calendar/event

Google Calendar

no

Google Calendar

Social, networking

Facebook

no

G+

Subscribe/notify

RSS

RSS

?

Looking at this solution set it's clear that each has its advantages and weaknesses.

Atlassian Confluence is the best integrated knowledge sharing and collaboration solution I know of. It's not at all free, but it's inexpensive for 10 or fewer users and anonymous users can have read only access. I give Atlassian extra marks for actually publishing an easily discoverable price list. Unfortunately I don't think I can get Confluence running at Dreamhost, my net hosting provider.

Google, like Atlassian, is free for a small number of users and provides high performance anonymous access. Sadly, Sites is a great disappointment. On the other hand, I'm not impressed with any of the currently available open source wiki solutions. In many ways FrontPage 98 was better.

Lastly the best of breed solutions have advantages in terms of data freedom and ease of switching providers or changing knowledge base ownership. An integrated approach can also leverage StackExchange -- the net's best technology for question/answer based information sharing. Likewise a Facebook Page can engage customers and provide a secondary notification solution in addition to RSS/Twitter.

Any thoughts? Comments are most welcome.

PS. I've been looking at collaboration technologies for about 20 years -- starting with BBS software and a long string of innovative solutions. The functional list would have had answers 20 years ago. What's different is that the audience today is vastly larger.

No comments: