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
Problem-solving as a team is a problem I am desperately trying to solve.
And reading Matt's session description, I'm sure I'm not alone in this adventure. Collaboration games often turn into Hunger games with only one who survives to keep the faith in Confluence collab.
I passed the 1000-pages-created mark, and I'm still learning how to create better content flow for my team and fully engage them in the process. Each time I start a new Confluence project, I think:
Do I see the bigger picture?
Is that structure good for the entire team?
How often my team is using Confluence, and are there any tools impacting their usability?
How to reach out for feedback and be sure it's being noticed?
K15t are a bunch of bright people who are always searching for a better collaboration flow (thank you, guys!), and I am always excited to hear about their achievements (and steal a few unicorn stickers, but that's another topic). 💙
Except for sharing my excitement about Matt Reiner's upcoming talk, I'm asking you: what's your best practice when you want to engage your team in a Confluence activity?