Last week, I attended a fantastic tech comm conference – Write the Docs Prague 2018. Hosted for the fifth time in the beautiful city of Prague, WTD allowed me to meet, chat, and share the experience with the fellow tech writers, information architects, and information developers from all over the world. Exciting!
Write the Docs is one of the most prominent technical communication conferences that brings people of the documentation development field together, promotes sharing of ideas, as well as encourages professional development.
I cannot but share the gist of 3 talks that boosted my motivation and inspired me at this year’s conference in Prague. Continue reading
Nowadays, public speaking is a crucial skill, which can help you greatly in communicating your ideas to various audiences, be it your team members, customers, or a group of people interested in educational camp on Information Development. Whether you like public speaking or not, chances are you will need it, and when the time comes, it’s better to be prepared with a good neat presentation and the accompanying story than read text from slides, or, what’s worse, mumble words hoping to end it all fast as can be. If the last words strike a chord with you, then the book Show and Tell: How Everybody Can Make Extraordinary Presentations by Dan Roam may be just for you. Continue reading
When creating diagrams, you may overlook some tiny, but crucial drawing details. And only after the review, you understand how important these details are. In this article, I will explain some of the most common mistakes when creating diagrams and how to escape them.
A well-drawn diagram communicates a very clear and direct message. You, as an Information Developer, can explain to users the workflow, interrelationship among components, or data exchange through visual assets. Diagrams are not just about cool shapes and trendy colors, but also about the meaning—text. In this article, I will share some important rules how to phrase, format, and position the text in a diagram to make it look more distinct and professional.
How on earth can anyone make sense of this technical review (see figure #1), apply mysterious comments, and deliver a valuable visual?
Figure #1 (Click to enlarge)
For an experienced Information Developer impossible becomes possible 🙂 How? During the technical review, pay attention how your SME corrects the following elements: