New Year Resolutions: 5 Things to Start in Confluence

[#1]

The New Year is the perfect time to reset how we work in Confluence. In my last article, I wrote about the habits we need to stop doing - the ones that make Confluence messy, unreliable, or underused. This time, let’s flip the perspective. Here are five simple things you can start doing in Confluence to make it a trusted hub and a tool your team actually enjoys using.

1. Start treating Confluence as a Knowledge Hub

Confluence works best when it connects information, not just stores it. Pages that explain context, decisions, and next steps are far more useful than isolated documents.

When creating content, start by answering a few simple questions: why this page exists, who it is for, and how it should be used. Over time, this approach turns your spaces into places people return to, not places they open only when they are stuck.

---

2. Start keeping conversations where the content lives

Decisions, feedback, and clarifications lose value when they stay in email inboxes. When discussions happen directly on the page, context stays intact and knowledge remains visible to the whole team.

Encouraging comments and inline feedback helps future readers understand not only what was decided, but also why.

---

3. Start reviewing and maintaining content regularly

Trust in Confluence grows when people know the information is current. Regular content reviews do not need to be complex or time-consuming.

For example, you could use the Approvals for Confluence marketplace app to add a simple section review or a one-stage approval for important pages. This helps teams confirm that content has been checked and is still valid, without adding unnecessary process overhead.

Clear signals such as review status or approval history help users understand whether content is ready to use, still evolving, or no longer relevant.

---

4. Start acknowledging contributions and engagement

When people comment, suggest changes, or keep pages updated, it matters. A short response or acknowledgement encourages further participation and signals that collaboration is welcome.

Over time, this creates a healthier culture around documentation, where Confluence feels like a shared space rather than a publishing platform for a few.

---

5. Start using clear ownership and simple workflows

Pages without ownership often become outdated quietly. Assigning responsibility, even informally, helps ensure content stays relevant and maintained.

For more complex content, the Workflows for Confluence marketplace app can be used to build multi-stage workflows with approvals and expiration rules - for example, triggering a review when a page is edited or after a certain date. This brings clarity and consistency without relying on manual reminders.

---

Final Thoughts

Small changes in habits can transform the way teams see and use Confluence. If 2026 is the year you want Confluence to become more than just a document store, these five resolutions are a good place to begin.

Do you have any Atlassian resolutions or good habits you want to maintain this year? Tell me in the comments - we can all share, and keep each other accountable.

[Stavros_Rougas_EasyApps]

Trust in Confluence grows when people know the information is current. Regular content reviews do not need to be complex or time-consuming.

I so agree @Yulia Lenina (AppFox).

Confluence doesn't need to be perfect, but it needs to be relatively up to date, if not it's not part of a single source of truth (often along with Jira).

It is not about one thing. A bunch of smaller things add up to better managed content. I've thought about this a lot, and struggled with it, it's the basis for our app Space Content Manager.