Here are seven common mistakes made by organizations using Confluence for collaborative knowledge management and documentation – and how to avoid them.
The following list applies to Confluence – Atlassian’s collaboration platform and enterprise wiki – but may be relevant for other platforms and content management tools, too. The same issues keep cropping up – so let’s find out how to fix them.
1) Excessive Access Restrictions
After setting up a collaboration platform, many admins take steps to restrict user access. If multiple target groups are using the platform heavily, these restrictions may be necessary. But when you’re just starting out with a knowledge platform, intranet or documentation management system like Atlassian Confluence, you must actively encourage your users to keep reading and contributing to your content. Don’t leave them out in the cold.
Excessive restrictions may result in some users inadvertently being unable to view content that their colleagues can access at will – to name just one potential source of friction. People will start feeling excluded and become frustrated – the opposite of what you want to achieve.
2) Multiple Users Sharing One Account
Some Confluence admins think it’s a good idea to give casual users a generic user account, such as “Support Agent”, that’s valid for multiple users or groups. They reckon this approach saves ‘precious’ Confluence user licenses and is easier to administer, due to the lower number of users.
But this strategy entails security risks due to shared passwords – and it impedes collaboration, too. We want to encourage Confluence users to become regular and active participants – not just casual visitors. And if a user makes a key contribution to the organization’s Atlassian knowledge platform, that user deserves – and will appreciate – personal credit for their efforts.
Generic accounts make your users practically anonymous. Before long, they’ll start acting that way, too – and so will other users: “Oh, another edit from a random support agent. Don’t know, don’t care.”
You can almost guarantee that generic user accounts will hinder collaboration. It’s impossible to trace who has made edits or authored newly created pages. Transparency is one of Confluence’s unique selling points – but by using generic accounts, that advantage is completely negated.
What’s more, Confluence’s social features – such as likes, and favorite pages and spaces – are rendered almost useless. Users are unable to express their personal preferences and interests.
3) Disabling the Comments Feature
Collaboration means communication – and collaboration platforms such as Atlassian Confluence enable human beings to interact with ease. And written text is the simplest way of sharing your thoughts online quickly and effectively.
By default, Confluence allows users to leave comments on each page or blog post, so they can share feedback with authors and editors. If a discussion develops below an article or Confluence page, it’s a sign that the content asset is worth talking about. And even more critical comments can be seen as an invitation to improve your content.
If you disable this functionality, you’ll destroy the most important social interaction feature of your collaboration platform.
4) Neglecting Confluence Updates and Performance
Users demand – and deserve – a highly available, secure and up-to-date system. Your platform needs a fast and responsive user interface that’s fun to work with (and waiting for a page to load is no fun at all). If everything’s running smoothly, word will soon spread – and before you know it, you’ll have legions of enthusiastic Confluence users interacting with your platform.
New systems should be sleek, easy-to-use and – of course – faster than the previous solution. Confluence certainly fulfills the first two criteria, but it’s down to the administrator to ensure exceptional system performance and security at all times.
5) Putting Everything on One Page
Your Confluence users should all be ‘on the same page’ – but that doesn’t mean you need to post all of your documentation on a single page with thousands of lines of content.
A few enterprise wikis, such as Confluence, provide out-of-the-box content management functionality that allows you to organize content into defined collections called spaces. Within a space, you can define as many pages and subpages as you like.
This allows knowledge workers to create content in the same way that we process knowledge in our brains – in trees (or pyramids), similar to chapters and sections of a book.
If pages are too long, and readers need to keep scrolling to assimilate all the content, they’ll soon lose the motivation to keep reading. Lengthy pages also hinder the commenting process – it’s very difficult to leave a comment on a phrase that appears 10,000 pixels away. In addition, large content assets cannot be reused properly.
6) Working Offline, and Copying/Pasting into the Editor
For people like me who work with Confluence every day, it’s hard to understand why some casual Confluence users think it’s more efficient to “check out” content from the knowledge base, copy it to their computer’s word processor, then paste their edited version back into Confluence before hitting “Save”. If, for instance, you’re editing a page or blog post during a long plane journey with no internet access, this approach makes sense – but if you’re at your desktop, it’s just illogical.
If you keep the page in edit mode during editing, other users cannot work on that page concurrently. But if you don’t ‘lock’ the page while editing content externally, other users might update it – and merging back external changes is no fun. And even if you’re able to merge it all together, rich formatted content pasted from Microsoft Word etc. often contains a great deal of formatting clutter. This could result in awkward editor behavior and misleading styles.
7) Storing Content as an Attachment
It’s easy to import content from a Word document – but it’s even easier to attach that document to a page. In fact, Confluence handles attachments very smoothly. You can even display the contents of a Word or PDF document on a page, and the Confluence search function indexes text within those attachments. But shoveling documents from one system to another can indicate a lack of a defined content strategy.
This ‘piggyback’ approach of storing content in attachments contradicts the way Confluence has been designed. It wasn’t primarily intended to be a document or asset management system – first and foremost, it’s a collaboration platform and wiki where authors create and manage native Confluence content (i.e. pages and blog posts).
Confluence is a great collaboration platform and wiki, but it takes more than a great tool to ensure successful knowledge management. Remember that it depends on the people who use it and how much they love their collaboration platform, and how they can benefit from the content provided there. This is vital to making your collaboration platform a success, and motivating users to contribute and share their knowledge.