Atlassian has added, cultivated, and managed a successful internal Q&A community for nearly a year. During that time, we've seen some innovative user hacks that take Confluence Questions beyond the basic "ask questions, get answers" model. These hacks challenge the way we measure the success of our own Q&A community, and have inspired us to take the product in new directions. Learn how we use Confluence Questions at Atlassian, and how our own experiences guide product development.

1. #atlassian

2. Measuring the Success of an Internal
Q&A Community
Sam Tardif • Team Lead • Atlassian • @samtardif

3. Insert title here

15. Measuring the success of an
internal Q&A community

16. Measuring the success of an
internal Q&A community

18. Learnings

19. Learnings Use cases

20. Learnings Use cases Measures

21. VOTES ANSWERS COMMENTS QUESTIONS ACCEPTED

22. VOTES ANSWERS COMMENTS QUESTIONS ACCEPTED

23. questions per day

24. 4.8 questions per day

25. questions answered

26. 75% questions answered

27. participants

28. 957 participants

29. answers per question

30. 3.5 answers per question

33. What do you want
to ask Mike at the
All Staff?

35. Hey X, how do I do
this?

36. What should we
name our level 9
meeting rooms?

40. What’s everyone’s thoughts
on X?

42. I have an idea!

45. Ideation
Polls
Targeted
Questions
Collector
Questions
Discussions

47. Engagement!

48. Engagement! Success?

49. Engagement! Success? Expertise?

50. Empowering you

51. Empowering you

53. -Uptake problem
-Recruit evangelists
-Make use of “Announce CQ”

54. -Need more experts
-Watch “unanswered”
- Promote sharing

55. -Discoverability problem
-Questions List Macro
-Dashboard hack

56. -You want at least 1:1
-Follow topics when joining
-Follow a topic after asking

58. Thank you!
Sam Tardif • Team Lead • Atlassian • @samtardif