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.
When you are new to the screencasting topic, starting working on your first screencast is a pretty challenging task. We’d wish that it was as easy as just recording the screen. However, fortunately, “I’ve done the procedure million times and I won’t screw it up!” – say no professional anyone. The good movies we see on the big screen are that good because nothing was done on the fly. The amount of time that people spend before the cameras actually start rolling is tremendous. Of course, we are not in Hollywood here, but why should we set for worse?
As a newbie myself, I have some fresh knowledge (and many hours of research), so I tried to summarize some tips, which will make your first experience with screencasting a smoother ride.
The question we all have – so, where do I begin? Continue reading
Using MadCap Flare, a help authoring tool, can be cool and unbearable at the same time. Those InfoDevs who deal with it on a regular basis will definitely understand what I mean. The more I work with this tool, the more I learn about its capabilities and pitfalls. The work on multiple print outputs and the HTML5 target makes the challenge even more exciting. Previously, I shared some issues I encountered with possible solutions for them (See MadCap Flare: pain points and solutions). In this article, I have prepared another portion of troubles to be considered. So, Ready Steady Go!
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.
As the IT industry changes introducing new trends and searching to propose more value to a user, technical communication should adapt as well. Technical communicators start searching for better ways to present information and predict all pains to be resolved by the documentation.
One way of doing so is to look for some useful practices outside of technical communication domain. In this article, I would like to briefly introduce a visual practice of empathy mapping that can be adopted into technical communication.
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:
MadCap Flare. We, Technical Communicators, use it daily. But do we really use it to its full potential? Or, maybe it has some hidden capabilities or mysterious forces we may have no idea about? Let’s follow this bumpy journey and find out together! Continue reading