I am excited to learn about Atlassian Products looking for any free tools and Product Manager communities.
Hi @Pratima Mangena,
It depends a little on where you want to go deeper. Getting comfortable with the tools, improving your product discovery practice, and taking responsibility for how a team uses Atlassian are different learning needs.
There’s a fair bit wrapped up in your question, so forgive the wall of text. Hopefully this helps you choose a useful starting point.
1. Start with the part of the ecosystem that matches the work you want to do.
For most Product Managers, I’d initially concentrate on Jira Product Discovery, Jira, and Confluence. There’s plenty to learn within those three without trying to cover the entire Atlassian catalogue. The free learning paths on Atlassian Learning are a good foundation.
Since you’ve posted in the Product Discovery area, I’d probably begin there. If you’re joining a team that already works heavily in Jira, though, learning that team’s existing setup may be more immediately useful.
2. For deeper product management learning, spend some time with Atlassian’s Product Discovery Handbook.
I like suggesting people reading this with a question (or set of questions) from their own work in mind.
For example: The prioritisation chapter is can be pretty useful if you want to cover scoring methods, but also the judgment involved in balancing customer requests, usability, reliability, and longer-term investment. When you practise this in Product Discovery, you'll want to keep the reasoning behind each score visible. An impact score of “4” tells a someone very little unless they understand the affected customers, the expected benefit, and the evidence supporting it. Discuss effort and uncertainty with engineering and design early.
Likewise, the roadmapping chapter is worth reading before spending too much time making a roadmap look all fancy or polished. Ultimately its about trying to be clear about what is being explored, what is prioritised, and what the team has actually committed to delivering. A Now / Next / Later view can help with uncertain work; genuine deadlines still need to be visible and understood.
3. Use the Atlassian community for discussion as well as troubleshooting.
Choose sessions by the problem you want to solve. An administration session and a product discovery session may both mention Jira, but they will teach very different things.
When asking for advice, include your context and what you’ve already tried. For example: “We receive feedback from support and sales, but we’re struggling to distinguish repeated requests from separate customer needs. How are you handling that in Product Discovery?”
That gives people enough detail to offer advice you can use. When you try a suggestion, return and share what happened as i find that those follow-up conversations can be a great source of learning.
Once you understand the core workflow, you can branch out according to your needs. Atlassian’s feedback and insights guide shows, for example, how its own Product Discovery team uses Jira Service Management to receive feedback and then brings relevant insights into Product Discovery. That is useful if managing incoming requests becomes a problem for your team.
There is also a free Rovo learning path covering finding information and creating or improving content across Atlassian apps.
Hope this helps!
Hello @Pratima Mangena
One practical addition to Hamza's answer: Set up an Atlassian Cloud site for hands-on learning. Jira Product Discovery is free for up to 3 creators, and Jira and Confluence for up to 10 users.
https://www.atlassian.com/software/free
Collect and prioritize ideas in Jira Product Discovery, link one to Jira delivery work, and document decisions in Confluence—all without a paid subscription. This way you can test without paying.
Best,
Arek🤠🧙♂️
It looks like you're new here. Sign in or register to get started.
