ExploreGalaxyMy PathSettingsGive Feedback

New here?

A quick look at how MySkillGap works. Close it any time.

Business ToolsFree tier available

Confluence

The team wiki used by product and engineering organisations to document decisions, processes, and technical specifications.

What it is

About Confluence

Confluence (Atlassian) is the standard documentation and knowledge management tool in software product organisations, particularly those already using Jira. It functions as a structured wiki: teams create "spaces" per product, team, or project, with nested pages for meeting notes, decision records, technical specifications, runbooks, and onboarding guides. Pages support rich content including code blocks, macros, embedded Jira issue lists, and diagrams, and have a version history that supports audit and review workflows. The core use case is maintaining a single source of truth that survives team changes. A well-maintained Confluence space means a new engineer joining the team can understand the architecture without scheduling a week of 1:1s. A UX designer can write a product requirements document in Confluence and embed live Jira issues so stakeholders always see the current implementation status without asking. Teams that treat Confluence as a living document — updating pages after post-mortems, decisions, and spec changes — build the organisational memory that prevents the same problems being solved twice.

What you can do with it

Capabilities

1

Write a product requirements document with embedded user stories and link it to a Jira epic so the spec and implementation stay connected

2

Create a team runbook for an incident response process — step-by-step instructions that on-call engineers can follow under pressure

3

Record an architecture decision record (ADR) with the context, options considered, decision made, and consequences — creating an auditable history of why the system is built the way it is

4

Set up a team space with a home page, meeting notes template, and onboarding checklist so new starters have structured context from day one

5

Use Confluence's page restrictions to make a draft spec visible to reviewers only until it is approved for team-wide distribution

How to learn it

Learning Resources

Atlassian University's free Confluence Fundamentals course at university.atlassian.com

Atlassian's Team Playbook at atlassian.com/team-playbook — covers the meeting notes, decision logs, and retrospective formats teams use in Confluence

The free Confluence tier supports real use — create a personal space to document a hobby project and practise the page hierarchy and template system

"Docs for Developers" by Jared Bhatti et al. — a strong reference for technical writing that lives in wikis like Confluence

Pro Tip

The most common Confluence failure is pages that go stale. Add a "Last reviewed" date to any page containing process or architecture information, and set a calendar reminder to review it quarterly. A stale Confluence page is worse than no documentation — it sends people down the wrong path with false confidence.