During a recent online conversation, someone requested for a list of questions I would typically ask to a subject matter expert (SME) to prepare technical documentation for a topic. Of course, the parameters may vary, but there is still a list of questions that apply across all sizes or complexities of projects. In this post, I share with you the list of questions that I shared with them…
Vinish Garg recently posted on the content’s role in Disruption. In his post, he shared what the experts had to say on the role that content has to play/currently plays. Here’s my opinion: What is Disruption? Let me first take you back in time. This started when the marketing and branding industry opened the corporate gates to the world of consumers. And, by opening the gates, I mean it transformed
Information communication is a cyclical process, much like the usual purchase decisions that you take. So, if we can wear the shoes of our users and understand their requirements, we can write better documents or even project the information-communication more effectively. In this blog post, I try to find those effective checkpoints using the purchase-decision analogy. We will take daily-life examples, such as using mobile applications to searching for “mobile
In this post, I take a closer look at the localization project in which my team and I assisted. I take cues from this project, and the similar ones that I have done previously, to discuss the top-three points for localization. This post is special to me, because it has helped me unfold those chapters of my life, which I had come to forget. If you are new to localization,
The fact that I am a marketing graduate has had a considerable impact on the way I handle product documentation. I largely take things from the user’s perspective: Unlike the way a technical grad would handle documentation, I mostly like seeing it from the eyes of a marketer. While I was recently busy answering the “what’s-in-it-for-me” question (during the product documentation for an upcoming release), I stumbled upon this strange
Last month, I got a chance to read from some of my old books. I am a marketing graduate. So, while I read some random pages from the marketing domain, I could see that the learning matched to technical communication as well. But, how could the lessons on branding teach anything about technical communication? In this post, I try to explore this question to help improve my understanding.
This post is about progressive reduction, which is what I’ve recently read about. From what I have gleaned, progressive reduction is about those gradual changes (mostly reduction) in the UI elements that relate to your time-lapsed incremental cognition of a product. In other words, progressive reduction is in continuously adapting the UI elements of your product based on the gradual improvement in its usability. Read the full post.
The bent towards information design is on account of its applicability – A picture, as they say, is worth a thousand words. The use of graphics minimizes the use of content. Rather, it squeezes the underlying message of the content into a graphics. Despite the usually observed bent of mind, I believe that the key elements of Information Design and Technical Communication are the same. Here’s how…
Redundancy is inseparable. But, it is still important to make mutual sense. Your reader wants to search for content that resolves the purpose of the search. But, that sadly isn’t always on our list of goals. This article tries to see the possible definition and cause of redundancy, and suggest the probable solutions to resolve or avoid it. Click here to read the full article. Note: The stub contains the
Premise In the regular classes on Business Economics, during my graduation, I learned about certain concepts that still apply. Two of such concepts, Buyers and Users, are applicable in technical communication to a great extent. Can those concepts lend any insights to us? Do we prepare our documentation considering the buyers or users? Or, do we concentrate on merely describing the features? The discussion follows in this post. Observation The