You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
As Confluence users, you know the situation: You've created a brand-new page and now you need to get your team involved to have them contribute or give feedback.
You're faced with a few options. You could:
With so many ways to get your team's attention, which one should you use?
In this 3.5 min video below, we outline the best ways to get your team involved and engaged in Confluence and when to use which feature. Heads up: The handy 'Share' button isn't always the best choice!
🎥 Check it out:
We also dive into each of these tips below 👇
The Share button sits in the top right-hand corner of every Confluence page, and is the most obvious choice to share content. It's easy: click on Share, enter the team members (or groups) you want to inform, add a message, and hit send.
Using the Share button makes sense in two situations:
In both cases, your aim is to notify your team members that they should take action: either read or edit the page.
So how does this differ from the other options?
Every time you want to engage your coworkers in a conversation about a page and encourage feedback and comments but not have them edit, then the Share button is not your best choice. Here's why.
When you share a page, think about that experience from the perspective of your team. The team member receives a message with your thoughts, questions or instructions about how or what they should provide feedback on. But when they want to provide that feedback – how or where should they do so?
They need to find a way to respond to your message on their own. It doesn't make sense to reply to the email notification, so they have to take an approach that feels best for them in that moment:
Without some kind of direction, you're looking at a mixed bag of feedback methods which won't work well for you or for your team.
So, when asking for feedback, this is what you should do: Create a comment on the page that contains your message and @-mention the teammates you want to involve. They'll still receive a notification, but now they can also respond to your instructions in the right way. What's more, other team members who later read the comments will better understand what was discussed and which decisions were made.
Check out this article for more best practices around commenting and feedback.
Sharing a page or commenting with an @-mention is a very asynchronous way of getting coworkers involved due to the reaction time.
Before determining whether a Slack message is the way to go, it's important to understand the difference between synchronous and asynchronous communication – and the gray area in between.
In between purely synchronous or asynchronous communication is a gray area, or rather a spectrum between the two extremes. The best example here is Slack.
Slack is actually an asynchronous communication tool, but it's often used in a synchronous way when users send messages and expect the recipients to answer right away, or if messages are sent back and forth quickly.
When you need to involve your team members more quickly, use a channel like Slack. But key word here is 'need' as this shouldn't be your share option by default.
⚠️ Beware: If your Slack messages contain too much information, you can easily find yourself in long, threaded conversations where feedback and decisions are easily lost in Slack.
If you decide to take the synchronous route by sharing in Slack, you should still create a Confluence page with more details and encourage any interaction or feedback to be left on that page. Slack should be seen as the more urgent notification channel, not as the primary medium for conversation or discussion.
How do you literally get everyone on the same page? These are just some of the best practices and conventions that our team at K15t follows, but we'd love to hear how your team does it!
If you liked this article, you can read the complete version on Rock the Docs, our guide for technical documentation in Confluence. We also have plenty more Confluence best practices to share in the guide. Check it out 👉