The Unified Modeling Language (UML) comprises a wide range of diagrams and is not just used in software development because it looks so pretty; it makes it possible to create completely different diagrams that still draw in everyone related to one and the same project. Our diagramming tool draw.io covers the whole range of UML diagrams. In this blog article, we’ll show you three valuable tips on how your diagrams will keep everyone clear and excited!
Category Archives: draw.io
“I 🧡draw.io” #2: How to create UX Diagrams in Confluence and Jira
The user – the unknown entity? If you don’t know your users, you will not meet their needs. To avoid a worst-case scenario, UX teams dedicate themselves to the user journey in all its details, develop an understanding of the target group, its needs and desires, and design the touchpoints based on this. This is where good visualization can help. With draw.io, you and your team can create user flow diagrams that depict the user journey and provide you with a solid basis for decision-making.
“I 🧡draw.io” #1: Clever Flowcharts and Process diagrams in Confluence
Complex projects in particular absolutely need visualizations – the risk is too great that something will go wrong, which will have an impact on all subsequent project steps. Flowcharts are a good way to remedy the situation. In our “I 🧡 draw.io” series, we provide tips on how you can use draw.io to quickly create diagrams, mockups, maps, etc. and lay them out in such a way that they can be read and understood by all team members or external stakeholders.
Seibert Media is Coming to America!
Today is German-American Day, and as a German company expanding into the American market, this is a great day to tell you our motivations and plans! This article contains information straight from our CEO Sebastian, who has moved to Boston with his family to personally oversee our efforts on the other side of the Atlantic Ocean.
draw.io – What Does the Chevrolet Corvette Have to Do with Diagramming?
Diagrams can be used for many different use cases. One of these is Root Cause Analysis, or simply said: finding out where something went wrong. If only Chevrolet had applied it in the early 90’s, they would have saved a lot of time and money when the engines in the original Corvette kept self-destructing…