Confluence is one of the most widely used Atlassian tools, and somehow also one of the most misunderstood.

Most teams start with good intentions. Document decisions. Capture requirements. Share knowledge. A few months later, Confluence is full of outdated pages, duplicate docs, and content no one trusts or reads anymore.

So teams stop using it properly. Or worse, they keep using it badly.

In this session, we’ll explore how agile teams can use Confluence as a true source of truth, not just a dumping ground for documents. We’ll focus on practical, real-world approaches that support day-to-day delivery without turning documentation into overhead.

What we’ll cover:

• Why Confluence turns chaotic for most agile teams

• What information actually deserves to live in Confluence

• Structuring spaces and pages to support ongoing delivery

• Using templates for requirements, decisions, and retrospectives

• How to keep content lightweight, current, and connected to Jira

• Common Confluence anti-patterns and how to fix them

This session is not about writing more documentation. It’s about writing the right documentation, in the right place, for the right reason.

Who should attend?

• Agile teams using Confluence alongside Jira

• Jira admins and Atlassian practitioners

• Product managers, scrum masters, and tech leads

• Anyone tired of searching Confluence and thinking “this doesn’t help”

Expect practical guidance, honest examples, and a few knowing laughs along the way.

And because serious conversations about documentation are best handled with a full stomach, we’ll wrap up the session with good food and relaxed community networking.