Rod Boothby, Innovation Creators blogger, writes that organisations should consider implementing a Read/Write Intranet, which is precisely what many of our customers have done using Confluence. We also have a case study of how Confluence customer, RedAnt, uses a wiki as their extranet.
Before working at Atlassian, my previous employers' intranets were collections of file servers. Content was lost, misplaced, difficult to find, difficult to share, and difficult to version. At Atlassian, our intranet is the wiki. Productivity is a quantum leap ahead of the file server(s) model. We can continue to share files, of course, and even comment on the files uploaded. But really the benefit has come from being able to share and develop content faster and more effectively... not to mention all the other wiki benefits like versioning, full search, collaboration, transparency, etc.
Check out Read/Write Intranet blog and while you're there, please vote for Confluence! :)
2 Comment(s)
Hi Jon,
Thank you very much for the link.
I was planning on following up this poll with two additional polls. The first would be focused directly on enterprise class wikis. I want to ask visitors what features they think are most important to an enterprise wiki. however, I first need to develop a fairly good list. What features do you think have really helped to drive Confluence's success is the market?
Thanks again for the link,
Rod
By Rod Boothby at January 16, 2007 8:47 AM
Atlassian users, please feel free to add your $.02 to this list...
Rod,
The features I hear customers cite as why they selected Confluence include spaces, permissions around each space and page, tons of plugins(extend product's functionality), the product's usability (WYSIWYG editor, information architecture, etc.), our fantastic Support team (not a feature but very important if you're going to invest money in a product like ours), the ability to change the theme for the entire wiki or each space, the ability to host the app themselves, and the cost. From there it differs from user to user (e.g., some users like the RSS, others use the wiki to blog too, etc). Now that we have some customers with 50,000+ users, scalability for performance and high availability becomes vital, thus in 2.3 we introduced clustering.
By Jon Silvers at January 16, 2007 9:57 AM