Confluence For Teams - Part: 2 / 14

Introduction

This is a part 2 of a 14 part free cartoon-based course, Making Confluence Work, that I created for my Learn By Cartoon site back in 2017. The course is now entirely free, and runs for 1.5 hours, split into 14 parts of 5 - 10 minutes. Although there have been some cosmetic changes to Confluence since, this content is still relevant for teams.

<< 1. Dashboard Concepts & Navigation - | - 3. Your Profile & Email Settings >>

Why Confluence Site (Instance) Design Can Fail:

Many organisations get this fundamental pillar of Confluence completely wrong. There is usually one of two possible wrong paths taken:

• The most common wrong path ends up with the organisation having literally hundreds of individual Confluence Spaces. This spreads out your organisation's information far too thin. It results in users having to carry out multiple very broad searches, returning miniscule amounts of actual information. This becomes infuriating to users, and your entire Confluence instance can fail. I've seen Spaces containing just one or two pages when a company follows this path. Totally useless design for team working...
• The next most common wrong path is to create only a few Spaces. This 'stuffs' all the information from multiple teams or departments inside a few very large Spaces, usually at department level. This is the sort of thinking more in tune with a very basic SharePoint instance, used for document control. But Confluence is not SharePoint - it's a team working tool more than a document management tool (although it can be used for document control it's not a SharePoint replacement for companies of any great size or complexity).