It was a busy week for us. Amidst the lockdown and the pandemic, we managed to see the doctor adn got our medical certificates done. Then, over the weekend, we traveled to our hometown. I did all the planning, packing, and traveling to and from the hospital in the work breaks. This helped me manage the work, meetings, and other priorities. But the writer’s brain continued to work as usual,
What should I look for to construct better sentences? Let us find out…
I transform complex
technical information into
some simple, usable chunks
of actionable items. I help
people do wonderful things.
There exist some common threads for micropoetry and technical communication, after all.
In most cases, all you need to do is progressively improve the things under the skin, rather than get a new skin.
As I continue to choose a (better) combination of tools and methodologies, I continue to steer farther away from the focus on the content. We have complicated the process of creating and managing that content. What’s the way out?
As a seeker of information, I am like every other “user” or “audience” – I am like YOU, dear reader. I prefer to take the shortest or quickest path to the resolution. Much like you, I get petrified when I can’t find the shortest route. Much like you, I get petrified when I see unorganized or insufficient information. It’s as simple as that. This puts a lot of responsibility on the shoulders of technical communicators and user experience (UX) designers. Sadly, there is still no guarantee that we, the information seekers, would access the right information tidbit at the right time; or even if we do, we get to use it correctly.
My first book on technical communication is available for pre-orders on Amazon. Secure your copy today and save 20%. The book releases on 6 June 2017. Credits: Book Cover: Mayukh and Vijay Nandula Foreword: Jitendra Sivamani Editors: Arun Dash and Sanjeev Patra
Both project the book to different sets of readers. A book blurb SHOULD NOT contain the conclusion because it is a sales pitch, while a synopsis is a 200-word version of the book itself. Here’s the elaborate version.
Although I don’t regard technical writing and instructional designing different, I do acknowledge that the tools and methodologies both use are quite different.