Logical thinking is high on the list of qualities expected from any Information Developer. But what exactly is “being logical”? If my writing is seemingly clear and makes sense to anyone who reviewed it, am I thinking logically? My layman’s definition of “logical” used to be “making sense”, but recently the book “Logic made easy” has come my way and added a lot to my understanding. Continue reading
Reception of your content largely depends on the first impression that it creates for your audience. Within milliseconds of interaction with your document, your users decide whether this is an instruction that is likely to help them work or make their head hurt.
Discover a few simple illustrated tips on how to style your content in a modern and light way!
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
Imagine that you need to create a mobile help but you have no clue how to start or what to do. No worries, my tips will help you make your first steps on this bumpy journey. ☺
When writing documentation, target audience is one of the first things on mind of an information developer. Audience determines what deliverable to choose, as well as what style and tone to apply to it. Wrong idea of the target audience’s needs may result in total failure of documentation. Therefore, a good information developer should be aware of every possible target user. Having deep knowledge of the product, understanding the aim of the documentation and the audience – their needs, possibilities, desires, and preferences, results in a masterpiece documentation.
So, how do we know what our target user wants? The answer is research! And I did a little research of my own on one of the most fast-growing generations in history. Millennials. So, let’s have a closer look at them and try to do our best to meet their expectations.
What if a Technical Communicator without localization experience was commissioned a localization task? What if they accepted without being familiar with the localization guidelines? What if they failed? There are no definite answers to these questions, but the one, which is for sure certain, is that certain guidelines are to be followed. So, let’s take a look at what major problems and potential pitfalls may come up on the way of a Technical Communicator challenged to complete a task in which they haven’t gained enough experience yet.
I was going to write this post much earlier. However, each time I got down to it, I was either distracted by whatever I saw in my timelines or just seemed not to have enough inspiration to kick-start the process.
Some people call it a creative block, some – a lack of inspiration, others blame laziness or a habit to procrastinate till the very last night before the deadline. No matter what it is, for an information developer such a non-creative state may sound like a nightmare, as we need bright ideas and resourcefulness like a breath of fresh air. But if you happen to feel unproductive at times, there are some tricks which may help you to find your muse again.