It’s one of these moments when you find out that self-organized teams really kick-ass. I just stumbled into a room where I thought to enter a co-working area for draw.io with our team here in Wiesbaden, Germany. Instead of Inga and Diana I met a crowd of people:
I was pretty impressed. They would practice a workshop that is due in the next days with a couple of co-workers. And they had created a cheat sheet for them the memorize the “power moves” that set draw.io apart from the competing solutions we see for Atlassian Confluence and JIRA. I have always struggled to learn, that there are still people out there who do one of the following mistakes (in my humble opinion):
- Using vsdx diagrams
A lot of legacy projects and traditional customers have a lot of vsdx files. And although they have suffered through the pain of version conflicts, difficulties to share diagrams and the lack of collaborative support in their internal processes with vsdx, they keep on using it. How come? Why don’t they see what is possible with an integrated fully versioned and audit- and certification-compliant solution?
- Using the old solution
There is this old solution from Gliffy that used to be the first ever marketplace add-on heavily endorsed by Atlassian itself. A lot of growth was most likely directly caused by Atlassian’s marketing for it. And while it’s an “okay”ish solution, it did not mature and grow in features and possibilities in the last years (at all). I no longer understand, when I see customers adopt it over draw.io. Fortunately we do not see this happen often any more. If you’re new to this, you may enjoy our comparision page for Confluence Cloud diagramming solutions.
I was always asking myself how we could educate people not to fall for this easily. Education was one of the things of our list. Now in this training I saw this cheat sheet that really leads the way:
Thanks team. You rock!