Jon Silvers, Audience and Communications Marketing

We receive emails now and again from new customers who ask us to recommend strategies for rolling out Confluence to their users. User adoption can be a problem with just about any new technology, even if it's one as simple as a wiki. You know wikis can improve collaboration, productivity and communication, but how do you get your team to see the light? I read several articles today from different authors that help identify some of the problems and suggest some strategies for introducing social software into the organisation.

At Atlassian, Jonathan started a page on this topic, patterns of wiki adoption, but we could use your feedback on it. Share your experiences of wiki adoption with us. I'll be adding the links above to this page. (One note: You have to create an account on this site in order to view the page)

I also recommend reading how other Confluence customers were able to rollout a wiki in their organisations in our case studies. (Got a case study you'd like to share, please let us know.) Finally, please feel free to comment on our blogs with other suggestions, resources, or ideas you've found helpful in your organisation.


Tags: wiki, wikis

2 Comment(s)

I have just installed Confluence and my biggest problem is Where Do I Start? I want to create a new site for Sarbanes Oxley within our company. I am not sure how to start it. I've read several documentation and guides but still I can't seem to "start it". Any help with this is greatly appreciated.

By Linda Antonelli at October 17, 2006 4:36 AM

The key with a wiki is to provide a central platform where people can easily create and share content and store files. With all wikis we recommend imposing minimum structure or rules. The best approach is to start something and evolve it over time.

In general I'd recommend:

- educating your users about the capabilities of Confluence;
- being as liberal as possible with permissions;
- creating a space for each project and team/department; and finally
- staying away from page templates, especially in the early days of the products use;
- ensure you users are aware of the Confluence docs:

http://confluence.atlassian.com/x/8hIC

- leave the rest up to them.

If you are looking for consistency, I'd evolve that over time as well. I highly recommend not attempting to over-engineer the wiki in the first 3 months. Find your best practices over time. By combining your own thoughts on best practices and by letting your users show you what their best practices you will be much further down the road to having an operating and functioning knowledge management product that is highly valuable than if you were to try to craft something from scratch and try to empose these practices on users from the outset. The more comfortable your users are with the system and their own use cases the more likely they are to participate in the development of best practices.

One of Confluence's main features is that it is highly flexible and that you don't have to get it right the first time. Once you have Confluence up and running, you can fine tune how Confluence is structured. If you wish to segregate your existing space, you can create a new space and move an existing page and all its child pages in a single operation
to a new space. All existing links will be automatically updated within Confluence.

There is an interesting page outlining the various wiki adoption patterns that have been observed amongst our users which you can see here:

http://confluence.atlassian.com/display/PAT/Patterns+of+Wiki+Adoption

If you need assistance with educating your users in regards to Confluence functionality then I'd recommend considering undertaking one of our Atlassian Training modules focussed on educating new users about Confluence. These modules cost $USD 1,500 and are delivered by a professional trainer at a mutually convenient time via teleconference and online presentation tools. If you are interested in formal training please do let us know. You can learn more about our training services here:

http://www.atlassian.com/support/training.jsp

Alternatively you may wish to engage one of our partners to assist with
design and implementation. We have a number of official Atlassian
Partners who are also able to assist with implementation and
customisation requirements. If you are interested in engaging an
official Atlassian Partner, please see the Atlassian Partners Space:

http://confluence.atlassian.com/display/APW/Partner+Wiki+Home

I'd recommend speaking either Adaptivist or Euan Semple both companies
are wiki experts.

http://www.adaptavist.com

http://confluence.atlassian.com/display/EUAN/Euan%27s+Work+Wiki

By Noam Field at November 17, 2006 1:52 PM

Post a comment





Remember personal info?

Type the characters you see in the picture above.