Iancho Dimitrov

A picture is worth a thousand words, they say – but unfortunately, it is not always the case. And this is even more valid for diagrams. If done right, they are a treasure – but we’ve all seen and suffered from spaghetti diagrams and ones bringing additional confusion rather than providing clarity and adding value.

The diagrams are a key element of the “language” we use in the software world. We use them to better explain architectures, data models, processes, and many other concepts. Through diagrams, we communicate with other IT people, business people, external stakeholders, and clients. We create diagrams for documentation, presentations, and proposals, we often do it ad-hoc on whiteboards during meetings and brainstorming discussions. Nevertheless, it’s a fact that very few of us have been trained on how to create effective diagrams. As a result, creating a diagram is a “pain” for many and what comes out is not always excellent, to say the least.

Join this session to level up your skills for creating effective diagrams. I’ll share 7 characteristics of a good diagram plus 7 practical tips and a checklist you can start applying immediately. Each of these – is presented with examples. Together we will go through the process of “refactoring” an architecture diagram and I will also share a step-by-step process for creating one from scratch – putting into practice all these principles and tips.