Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Should this Confluence Page Have a Diagram? (Exclusive Tips + Webinar Sneak Peek!)

Hi Community!

I’ve been working on a webinar with Gliffy’s Director of Engineering, Mike Sample, and wanted to share a sneak peek and some tips here. Our webinar, How to Diagram Your Way to Better Work: the Gliffy Guide, is not your standard product demo or thought leadership piece. It’s got three actionable, easy-to-do exercises that will help your work flow more smoothly.

Even if you don’t have a diagramming tool or have a different app for making diagrams, you’re welcome to join and will find these helpful! You can sign up here. >>


So, on to your sneak peek: Exercise 1 from this webinar has Confluence written alllll over it. It’s about how to identify when and where your team would benefit from a new diagram.

Here are my top tips for determining whether an SOP, wiki page, or workspace would benefit from a diagram (and where you should add a diagram, if so!):

  1. Are users in your space frequently visiting the page? Check page stats to make sure you’re prioritizing improvements to a page that your team is referencing often. Here are instructions for finding that info in Cloud and Server/Data Center.
  2. Is that page packed with text? If yes, your reader could probably use a break with either a helpful image or diagram.
  3. Scan the text for instructions with words like If...then, or next. This is the right place for a flowchart.
  4. See a numbered list? That’s a good spot for a flowchart, too!
  5. Do your instructions or workspaces reference multiple people or roles across your company? Consider an org chart. You can easily link to one or add one to the page.
  6. How about a specific place? Maybe add a rough map or drawing to show where that supply closet is or where to take a broken laptop.
  7. You might also be able to see search queries in your site insights. This can give you more ideas of what information your users are looking for — great questions to address with a diagram.


As I was writing this post, I realized I should probably follow my own advice. So, here’s a helpful diagram describing the list above. 😉 


Even if you skimmed that numbered list list (like your users might be doing with a long confluence page), an eye-catching diagram can quickly break information down and improve understanding. Cool, right?

Want more ideas for how diagrams can help your team? Sign up for our webinar and we’ll see you next week!




Log in or Sign up to comment
AUG Leaders

Atlassian Community Events