Structuring knowledge base & sharing Atlassian news

Question

Hi Atlassian Community!

Our team at DONOS, an Atlassian Solutions Partner, is on a mission to level up our internal knowledge sharing and client demos. We're building a centralized knowledge base in Confluence, aiming to include a well-organized bibliography of Loom demos showcasing our expertise.

We're also looking for creative and effective ways to keep our team informed and engaged with the latest Atlassian news and updates. We currently have weekly casual calls and an internal "updates" rubric, but we're keen to explore more dynamic approaches.

As we structure this, we'd love to hear from your experiences and best practices, especially from fellow Atlassian Champions and those working within the partner ecosystem:

Regarding our KB & demo bibliography:

how do you structure your internal Atlassian knowledge base in Confluence to make it easily navigable and truly useful for your team? Any advice on top-level spaces, page hierarchies, and linking between them?

for those using Loom for demos, how do you organize and index your video library? What key information do you include alongside the video links to make them easily discoverable and understandable? (e.g., tagging, descriptions, links to related Confluence pages).

Regarding Atlassian news sharing:

what fun and effective methods have you found for sharing Atlassian news and updates with your teams beyond just reading announcements? We're open to ideas that foster discussion and understanding of the implications for our work and our clients.

Any insights, tips, or examples you can share would be incredibly valuable as we build this out.

Thanks in advance for your help and wisdom!

Dave LIAO · Answer

We're also looking for creative and effective ways to keep our team informed and engaged with the latest Atlassian news and updates.

@Susanna Babayan - Who counts as "our team"? Got that answer? Good!

What is the archetype, or persona, of these teammates? Finance people? Developers? HR? Think of a few of these personas, and craft a deliverable (blog post, Loom, etc.) directed for each.

Not everyone needs every feature, or is interested in learning about all the newest features. Think about what features your teammates have historically used, or asked for.

🫠 Obviously ACCs like us ARE interested in reading the manuals and knowing about the latest product drops from Atlassian. 😉

Dave LIAO · Answer

LOVE the idea of incentivizing your user base to "catch" features that aren't yet present in internal docs! 🙏

Esther Strom · Answer

Hi, @Susanna Babayan . At my previous company, we had a space called Atlassian Products. We used folders to organize; one for each product. We would include a separate page for each video/article, and have an index page in each folder with the child pages macro to keep the index up to date.

We had a separate folder for product updates (we were on managed releases, so we had more time to produce our content, but more content to produce than if we'd been on continuous release.) We had a page of changes per product for each release with a table of contents header to make it easy to navigate the pages. Each time a new release came out, we'd split the content from the previous release into standard video/article pages to live under their products (possibly replacing existing pages if it's a change in functionality rather than new features.)

We also gamified things a bit - the first three people to report a new feature that we hadn't yet documented would get a small prize.

Something we tried for a while that was fun was doing a live Jira Jeopardy quiz a few weeks after each release. It would cover some older stuff, but most of the clues were about the most recent release. For the people who actually read/watched our updates, they could win a prize if they played, and people who didn't follow the updates could learn about the changes in a different format.