Hi everyone!
I’ve been working with Jira’s Custom Onboarding feature recently, and one thing that stood out is how effective it is at helping new users understand not just how to use Jira, but how it’s used within the organization by a specific role.
In many organizations I’ve worked with, new users often struggle with:
Unlike Jira, where onboarding can now be guided and structured, Confluence onboarding often relies on static documentation or peer-knowledge-sharing.
I’m curious how others are approaching this today:
It feels like there’s an opportunity to bring some of the same onboarding patterns from Jira into Confluence, especially as organizations scale.
Would be great to hear how others are solving this on Confluence side.
@Stavros_Rougas_EasyApps I'm not sure.
Tagging @Dominic Williamson who was one of the Product Managers on the Jira onboarding feature and might know the answer to your question.
I'm quite curious myself.
@Artem Taranenko I built apps for Confluence. There is a way to build an onboarding feature for a Confluence app so it makes sense that Atlassian would create it for Confluence given already exists for Jira. I didn't know about Jira custom boarding.
A great example of customer first thinking. Adding new features is not necessarily the key. Jira and Confluence are powerful, more powerful than most alternatives, but bloody complicated/overwhelming for new users.
re Confluence, users run back to the Office silo, bad for team, but in short term safer and easier for them. Having to move between edit and publish modes is a cognitive switch, understandably it is hard to get used to, it was for me.
@Dominic Williamson I'm wondering if you might have any thoughts for the good of this conversation?