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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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!):
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!
Samie Kaufman - Your Gal at Gliffy
Marketing @ Gliffy
12 accepted answers