Adobe RoboHelp 7 is more stable with 7.01 release

When RoboHelp6 was introduced, there wasn’t much to get excited about. User defined variables was the only major addition. However, Adobe RoboHelp 7 changed the way people work with Help Authoring Tools. Packed with a new MDI interface, support for over 35 languages, removal of kadov tags and several other enhancements, it was a dream that many Technical Communicators would have seen. 

As they say, “all that glitters is not Gold”. RoboHelp 7 has had some serious issues which stopped many Technical Communicators, including me, to upgrade from RoboHelp X5, or RoboHelp 6 to RH7 such as:

  • Search does not work properly in CHM output generated in complex asian languages.
  • When an X5 Project is upgraded to RoboHelp 7.0 some topics may remain empty in certain scenarios.
  • Browse sequence doesn’t get auto generated via TOC on importing complex Frame maker file.
  • If style sheet is accessed by clicking Format | Styles, then after style sheet creation changes to the styles could not be made successfully in the first attempt. The dialog has to be reopened to make changes.
  • Any formatting changes to a paragraph could not be saved as a paragraph style on the fly using Formatting toolbar.
  • Search does not work properly in CHM output generated in few languages.
  • When an X5 project is upgraded to RoboHelp 7.0 topic files-names might get converted to Title Case.
  • Images with Text wrapping applied do not appear in Printed Documentation output.
  • DHTML effects applied on styles do not get automatically updated without opening the topic.
  • Security vulnerability related to cross-site scripting attacks in WebHelp and FlashHelp Single Source Layouts has been fixed.
  • Frame Maker style with DHTML effects when mapped to a RoboHelp style do not retain DHTML effects on mapping.
  • While renaming a Snippet or a UDV, the Topics opened in the editor may get saved without a prompt.
  • While viewing content in Mozilla Firefox, some of the TOC Books may not open until any topic is opened manually. Additionally the default topic is not shown if it is under some book.
  • In certain scenarios hotspots created on Shed files are missing in the FlashHelp output for RoboHelp for Word.
  • Conditional Build Tags when applied differently in multiple cells of a table do not appear properly in output.
  • Previewing of an unsaved topic results in saving the topic without giving any prompt.
  • HTML topics may not get generated if a structured Frame Maker file is imported or added to a RoboHelp project.
  • In case of multiple cross reference markers applied to paragraphs each linked to different sources in a FrameMaker file, the hyperlinks are not formed on importing or linking the file to RoboHelp project.
  • Inserting image with path more than 120 characters do not work properly.

With the availability of a patch (RoboHelp 7.0.1), the bugs seems to be cleared making it more stable and worthy of a thorough review. Even the notorious RoboHelp Cross-Site Scripting issue is solved. More information about the patch is available at the official Adobe TechComm blog:

http://blogs.adobe.com/techcomm/2008/02/details_about_adobe_robohelp_701_the_update.html

Trackback

Trackback URL for this entry is:
http://helpguru.wordpress.com/2008/02/26/adobe-robohelp-7-is-more-stable-with-701-release

New Delhi World Book Fair

What: The 18th New Delhi World Book Fair
When: 2-10 Feb 2008 (Daily 11.00 a.m to 8.00 p.m)
Where: Hall No: 1-6 and 8 to 14, Pragati Maidan, New Delhi

Bookworms in New Delhi, once again, have the opportunity to go through their everlasting quest for books and educational resources they have always longed for. The ‘18th New Delhi World Book Fair’, organized by National Book Trust (NBT), India is already in its full swing.

The 18th New Delhi World Book Fair has 1,343 participants, including 41 from 22 overseas countries including international bodies such a ILO, WHO, UNICEF, European Union, etc and is spread over 45,500 square metres area covering nearly 2,500 book stalls.

Russia, the guest of honor this year, has a special hall (Hall No: 7D) where over 80 Russian publishers are displaying their latest publications, as well as organizing panel discussions, literary programs and special activities for children.

A special note for people (like me!) who are learning Japanese: The Japan Foundation (Tokyo), famous for Japanese Language Proficiency Test (日本語能力試験, nihongo nōryoku shiken) certifications and course material, is also one of the publishers participating in the 18th New Delhi World Book Fair. They are located at Hall No9 (Stand No: 2). Go, grab some Nihongo text!

The whole book fair is spread across several halls, some booked exclusively for English publishers. Technical Communicators may be interested in visiting Hall No 8 and 9 as they are reserved only for foreign publishers and may contains some good books related to Technical Writing.  Parents can visit Hall 7B for Children’s Pavilion. The hall location details are as follows:

  • Hall No. 1F & IR: English Language Publishers
  • Hall No. IF: Publishers of Books on Social Sciences and Humanities
  • Hall No. 2: English Language Publishers
  • Hall No. 3: English Language Publishers
  • Hall No. 4: English Language Publishers
  • Hall No. 5: English Language Publishers
  • Hall No. 6: Distributors of Book in English
  • Hall No. 8&9: Foreign Publishers
  • Hall No. 10: Publishers of Educational Books
  • Hall No. 11: Publishers of Books and Educational Aids for Children
  • Hall No. 12: Indian Regional Language Publishers
  • Hall No. 12A: Hindi Language Publishers and Distributors
  • Hall No. 14: Publishers of Books on Science & Technology

Hall No. 7 is a special one:

  • Hall No. 7B: Youth and Children’s Pavilion
  • Hall No. 7D: Display by Russia (Guest of Honor)
  • Hall No. 7E: Books on and by Gandhi

Special Facilities

  • Telephone and Posts Telegraph: Public telephone booths are located at convenient points throughout the Fair ground. A Post Office located in Hall No. 19 provides STD/ISD phone and fax services in addition to normal postal services.
  • Banks: The State Bank of India, Central Bank of India and Canara Bank provide complete banking services at their branches in Hall No. 19. These banks also deal in foreign exchange.
  • Restaurants and Cafeteria: There are restaurants, kiosks, snack counters and cafeteria all over the Fair ground.

Book Hunt with me!

I’d be going on a book hunt on its last weekend i.e. Sat’ Feb 09, 2008. If you are interested to join me in this treasure hunt, just write a comment in this post.

Trackback

Trackback URL for this entry is: http://helpguru.wordpress.com/2008/02/08/new-delhi-world-book-fair.

 

Freelancing Opportunities in Technical Communication

There exists a number of freelancing opportunities for Technical Communicators. However, most people are simply not aware of the trend and challenges one faces in freelance technical writing.

A presentation titled “Freelancing Opportunities in Technical Communication” was presented by Gurpreet Singh in May 2005 for STC India Chapter meeting held in New Delhi. The presentation slides can be downloaded from this link:

http://www.stc-india.org/learningsessions/DelSessions/sessions_del.htm

Trackback

Trackback URL for this entry is: http://helpguru.wordpress.com/2008/01/30/freelancing-opportunities-in-technical-communication.

Tools used by Technical Writers

Broadly speaking, tools used by technical writers can be divided into these four categories:

1. Writing Related Tools

2. Help Authoring Tools (HATs)

3. Graphic Related Tools

4. Presentation Related Tools

Writing Related Tools:

Help Authoring Tools:

Graphics Related Tools:

Presentation Related Tools:

However, for beginners, Macromedia Robohelp and Adobe Framemaker are quite essential to learn. Do not assume that by learning few tools one can become a technical writer. It is just a myth! Tools and Processes are two different things. You have to learn both, and I would say that tools are not as important as processes are.

Take a simple case study. One has to write a user manual for a simple application such as Notepad. What S/He requires to know first, the process of writing a user manual or working with Word/Framemaker/Latex/InDesign or any other writing software?

Tools can be easily learned and most technical writers have cracked these tools in less than a week’s time. Processes, however, takes a lot of time and are much important than the tools.

Remember, this is not programming where tools have high importance!

Trackback

Trackback URL for this entry is:
http://helpguru.wordpress.com/2008/01/30/tools-used-by-technical-writers.

 

Business Value of Technical Communication

Business value and self-esteem are the two major factors of growth/decline of any industry/profession. Technical Writers have described the value of technical communication through the viewpoint of the End User or through their self-esteem. Howver, they often forget that there still exists a business side to technical documentation. In  this article, Gurpreet Singh explains the focus on the business value proposition of technical communication.

Let us view the whole thing in terms of monetary value addition to the company and their clients (end users). Companies have different departments and each department has different viewpoint, different needs and hence they see things differently from each other.

I will take customer support department to illustrate the real value in terms of hard, cold cash, a technical communicator brings in for a company and for their clients (external customer for us). I will call the company Customer1, and their client (end users) as Customer2. I will *try* to project the business value of a technical communicator through a troubleshooting guide, as seen by Customer1 and Customer2.

Let us view a simple case of a trouble-shooting guide. The same guide that provides answers to the queries of Customer2 and hence provides value to them. Wait! They provide value to all the parties involved and not just the external customer.

Let us go in a little bit of details here. Suppose that Customer1 is a company that provides extremely complicated software platform to customer2 and this software platform comes with free customer support. Now when the user base of Customer1 grows, the number of support queries also grows.

Due to this growth, the number of support personnel also grows. This expansion costs Customer1 money in terms of salaries, training, retirement benefits and other benefits give to the employees of Customer1.

Moreover, a major part of the queries coming to Customer1 from Customer2 are of exactly similar nature. This is because the Customer2 is actually made up of few hundreds or perhaps few thousand end users and which through a query whenever they pass a little bump in the software platform.

Going by the industry standards, a customer support personnel on an average will get a CTC of $ 50,000/annum. That is the money the company i.e. Customer1 will spend on him/her for 160*12= 1920 billable hours, which comes to around $26 per hour. Lets us suppose that a query, whether be it email or phone, takes approximately 15 minutes to get solved. A person-hour will solve four queries, which means that the approximate cost of solving a customer query will be 26/4= $ 6.5.

Now a technical communicator comes in to the scene to create a trouble-shooting guide for the complex software that will contain the most commonly asked question regarding the software. The troubleshooting guide, when completed will contain few hundred common queries and their solutions. I have heard, from many, that a well-written trouble-shooting guide can provide a reduction of 30-50% in the support related queries.

Let us assume that Customer1 gets about 1,000 support calls everyday. This is not hard to imagine if few hundred thousand people are using Customer1 products. The daily cost of providing support to these 1,000 queries will come at a cool tag of $6,500/day. Extrapolated, this becomes $26,000/month and $ 31,2000 per year.

A simple 30% reduction in the support calls would bring the support cost down by $93,600/annum!

If Customer1 gets more than 1000 queries a day, or the average CTC of a support person is more than $50,000/annum, or if it takes more than 15 minutes to answer each query, or if the reduction is more than 30%, then the money saved would be much more.

Remember, money saved is money earned. If you are reducing company-running cost, you are providing value for your service, which is the motto of any person working for a company.

That was the monetary benefit gained by Customer1. We have not talked about Customer2 yet. This troubleshooting guide will also provide value in terms of hard, cold cash to the Customer2.

Let us assume that the average turnaround time of getting an answer to a developers query at Customer2 is 15 minutes. This can be a call to customer support department of Customer1 or a small chat with his senior.

Assuming that Customer2 spends  $80,000/annum on his employees, this comes to about $42/hour or about $10 per 15 minutes of work (cost per query). Let us also assume that a Customer2 generates 100 such queries each day. This is not difficult to imagine if few thousand developers are working in Customer2 on the software platform developed by Customer1.

Therefore, for 100 such queries each day, Customer2 is spending $1,000/day, or $22,000/month, or $26,4000/annum. A fifteen minutes turnaround time is very difficult to achieve, even in best companies in the world. Therefore, this figure might be much bigger than this.

By having a troubleshooting guide, developers can just search the guide to solve the query on their own. This may take a little over 5-7 minutes instead of earlier time lag of 15 minutes that will bring a cool 60% reduction in the non-billable time. This means a net saving of $15,8400/annum for the Customer2.

If Customer2 generates more than 100 queries a day, or the average CTC of an employee of Customer2 is more than $80,000/annum, or if it takes more than 15 minutes to resolve a query, or if the reduction is more than 60%, then the money saved would be much more than this.

We discussed just one of the deliverables a technical communicator works on. If we discuss training material,  marketing collateral, proposals, and other significant material technical communicator develops, and about the total cost of ownership, we can easily understand and let them understand the value of technical communication and technical communicators.

Trackback

Trackback URL for this entry is: http://helpguru.wordpress.com/2008/01/30/business-value-of-technical-communication.

How to charge (in freelancing)?

Writers working on a freelance basis often face difficulty in deciding the method to provide a quote to their clients. Whether they should charge on the basis of pages, assignment, or, hour et al. Gurpreet Singh describes a few payment methods used by freelancers to decide the payment method suitable for their freelance writing assignments.

Freelance writers, many times in their career, wonder about the method they should use for their writing assignments. While it seems an easy and good way to use one particular method for all types of writing assignments, the variety of projects having different requirements make it almost impossible to use a standard payment method.

Several factors need to be considered while quoting for a freelance project. The following factors play a role in determining the suitable payment type for a freelance writing assignment:

  • Type of work – editing, proofreading, writing, and so on
  • Amount of work or effort – two hours, five days, two weeks, and so on
  • Type of work arrangement – client site, home, or office

Freelancers frequently use either of the following options to quote a project:
⇒ Hourly wages
⇒ Page wise bid
⇒ Monthly salary
⇒ Fixed bid (by project)

Hourly wages

The most common method used by freelancers (worldwide) is to quote an hourly wage. This type of quote is suitable for newbie freelancers. In this method, you are paid based on the number of hours you put in for an assignment. It simply means that you are paid for what you work and not a penny less or more.

Nevertheless, the output should be within a certain range from the employer’s prospective. If you take more time to finish a small amount of work, slowly but surely you will start losing contracts.

This system is popular in countries such as US, UK, and so on. A word of caution here! If there is travel included in the project then the hourly bid is extremely difficult to calculate. Suppose your work involves going to the employer’s client site and if the site is divided into several subsites, then the hourly bid is extremely difficult to calculate due to the involvement of factors such as travel time, travel expenses, and availability of client resources.

Page wise bid

Employers worldwide prefer this type of payment for content development, however this is the most difficult to provide. In this strategy the number of pages is multiplied by a fixed constant. For example, a company that wants to have 10 pages of content on its recent medical product would prefer a quotation based on the number of pages.

You can compute the bid for these kinds of projects easily only if you have worked on similar projects and know the amount of time and effort that need to be put in. However, if you are new to the domain, company, or type of project, this method would not be suitable as it takes experience to determine the actual time required to do a particular job.

You can, of course, ask others for a time estimate for similar projects but other’s experience really does not help, because in most cases time is inversely proportional to. An experienced person spends lesser time on similar kind of projects. Even though there are exceptions it is advisable to opt for other pricing methods if you have not worked on similar projects.

You can quote a page wise bid for tasks such as editing, proofreading, translation, and so on as there is a limitation on the work or pages. Even in such projects, it takes lesser time to review non-technical content than highly technical content. So propose bids based on the type of content.

Monthly salary

If a project extends for months or years, it is better to ask for a monthly salary like the regular employees. There are projects that run for 2-3 years, so a monthly salary is the best option. Page wise or hourly bids do no work in such situation due to the extent of the project. This is especially true for web portals that contain thousands of pages of content and research assignments.

Fixed bid

This bid is a combination of several methods and most sought after by employers across the globe. Employers prefer a fixed quotation on the documentation project that cannot be estimated by page length.

Suppose you are proposing a page wise bid for a project where there are 10 illustrations in some pages and one or no illustrations in some other pages. It is not in the interest of clients and writers to provide a uniform per page bid. Therefore, you can quote a bid for the entire project. Most of the experienced freelancers prefer this type of bid.

Apart from a few rare instances, almost every client prefers a fixed amount for the project, so that they are relived from the uncertainty involved in the cost of the project.

This practice has its own advantages and disadvantages, depending upon several factors. If you are experienced then this option provides a better opportunity as you can charge the client more than the usual hourly bid rates. However, if you are inexperienced and cannot determine the scope of the project, you eventually work more for less money most of the time.

Suppose you estimated that it would take a month to write a few white papers on a highly technical topic and quoted a good price for that. Unfortunately, the project was more difficult than you estimates and it took two months to complete the project. You finally worked for two months for the same price.

While estimating take into account at least 25 percent buffer time. In the beginning, freelancers often provide a deadline of the minimum possible days. However, factors like sudden illness, internet connectivity, power failures, unavailability of core data, and other unknown but significant factors make it nearly impossible to stick to strict deadline.

Therefore, it is always a wise decision to include a 25 percent buffer time to the deadline. Every client would be happy to get the work done before the deadline and this extra time ensures that you deliver the work before the deadline.

Each method has its own Ying and Yang components and it is up to you to follow any method depending upon your choice and condition.

Happy Freelancing!

About the Article

This article originally appeared in Vol I, Issue 4 (Sep-Oct 2006) issue of MITWA News, the newsletter of MITWA mailing list. It is reprinted here with slight modifications.

Trackback URL for this entry is: http://helpguru.wordpress.com/2008/01/29/how-to-charge-in-freelancing.

 

Documentation Productivity Metrics

Overview 

The simple definition for metrics would be the methods or procedures used by companies to judge success and/or failure of their work standards by the scientific measurement of data usually gathered from specific tasks, such as production, testing, documentation and so on.

If we look at documentation, which is a complex task that includes several subtasks such as writing, editing, reviewing and so on, we can gather the common errors in each of the processes to remove them from the entire documentation cycle. This error removal automatically improves the overall performance of the organization/individual involved in the creation of documentation.

Quality vs. Productivity Metrics

Quality metrics, as suggested by their name, are metrics of the statistics regarding the quality aspect of documentation. Productivity metrics are more concerned with the productivity or the rate of production of words rather than the quality aspect.

These two are quite different from each other as they map two distinct areas of the documentation sector: namely, quality and quantity. Each organization/individual already works with some kind of metrics, whether they know it or not. There is a complete subject devoted to the processes used to gather and analyze such statistics with the name of Operation Research (OR).

OR is a very interesting field and is a must for people who are interested in the usage and benefits of metrics of any kind, not just documentation. The power of these statistical analyses can only be visualized correctly if you create one real-time analysis of your own organization.

Documentation Metrics Formula

Now, coming back to the original subject of quality and quantity (aka productivity) in documentation, we use these metrics all the time. If you estimate, based on your previous experience, that a user manual will take x number of hours, then that data has come (indirectly) from your productivity metrics.

If you write down your experience with different projects, such as user a manual of this kind, will take x1 hours per page, the installation guide of y type will take x2 hours to complete, the help file of c type will take x3 hours and so on, then it will constitute a simple documentation productivity metric for you.

This metric simply reflects how soon the work will be finished depending upon the complexity of the task. This is a global method used for estimation of all kind of projects, and we can apply it to documentation projects also.

Benefits (or The Catch!)

The benefits of such productivity metrics are incredible. Let’s say that you are working as an independent consultant like me and get a request for providing quotes for several different kinds of projects every month. One method is to analyze the kind of project and then place a bid based on your experience.

This can be quite dangerous, particularly if you are inexperienced, as estimation can very easily go to values much less than the actual time needed to complete the project. Even experienced consultants often make mistakes in estimating the efforts required for a document. This means that you will work more for the same money due to the faulty estimation. So this method is not scientific enough to be applied to projects, as the error margin is quite high.

On the other hand, let’s say that you create productivity metrics for yourself based on different aspects of documentation and your working speed. You can estimate the time needed to complete a project scientifically by the use of this productivity metric, which you already created in the past.

Yes, a considerable amount of time is needed to first record the data, analyze the statistics and create the metrics, but it is a wise decision that you can make for reducing the forthcoming work in the form of estimates for different projects.

Quality Metrics & Reading Scores

Talking about the quality metrics, it is simply a measure of how useful the document is for the intended audience. Please note that I used the word “intended” audience here, as a document scoring high on your quality metrics for IT managers may fall below the passing mark for say 12th grade students. Each quality metric is limited by the audience it refers to. So in most companies, the generation of different quality metrics for different audiences is common.

The quality metric is usually based on a number of different aspects of documentation such as:

  1. Readability of the overall document (Flesch reading ease)
  2. Grade level required to read the document (Flesch-Kincaid grade level)
  3. Time required by a typical audience subset to read and understand the content of document
  4. Usability in terms of problem-solving techniques
  5. Number of editing cycles required to finalize the document
  6. Spelling/typo errors
  7. Time spent in hours to complete the document from scratch
  8. Human resources required in the preparation of the documents
  9. Compliance with style guides such as MMOS, APA, MLA, Harvard, and so on

So if your intended audience is normal people, you must achieve at least a score of 50 or above in the Flesch reading score. In the Flesch reading score, the scores usually denote the complexity of the documentation and what grade education is required to read and understand the component of documentation. The values are as follows):

Flesch Reading Score

So, if you are writing user manuals for 12th grade students, then you must make your documents less complex by using simple words instead of complex ones, producing a Flesch reading score of 35-50, preferably above 40.

I see many listserv messages that have a Flesch score of less than 15, which is not good for the average reader. By using difficult words, the messages are not highly effective since few may understand the content. It might be good to check the reading ease of your posts or documents for the reader’s benefit.

This entire post has a Flesch reading score of 46.7, which means that it can be understood by a majority of people who have a high school education. There are several other factors that you can put into quality metrics, but for now these points will guide you to search for more complex methods to be used in such metrics.

About the Article

This article originally appeared in Vol 9, Issue 4 (Oct 2005) issue of Directives, the newsletter of Management Special Interest Group (SIG) of Society of Technical Communicators (STC). It is reprinted here with slight modifications. Trackback URL for this entry is: http://helpguru.wordpress.com/2008/01/29/documentation-metrics.

 

Evolving Roles and Desired Qualities for Indian Technical Writers – A Glimpse into the Future

Prime Future Roles and Qualities of an Indian Technical Writer – Adaptable, Communication Expert, and Perfect Tool Master

Adaptable

Adaptability will become a necessity and NOT just a desired feature for Indian Technical Writers.

The prime role played by Technical Writers in future will be to become highly adaptable in terms of latest technologies, new tools, and even new cultures.

It was Charles Darwin who once said, “In the struggle for survival, the fittest wins out at the expense of their rivals because they succeed in adapting themselves best to their environment.”

Adaptation is indeed the prime factor contributing its share to the successful Indian Technical Writing industry. In the golden age of globalization, one cannot stick to a particular standard, language, or technology by personal choice. One has to be versatile enough to adapt to any new technology or guidelines for the sole purpose of producing meaningful content to the users of a particular region.

With strong competition rising from other countries, the day is not very far when the Indian Technical Writing industry will find it very difficult to survive primarily on the adaptability front.

The prime reason for the growth of the Technical Writing industry in India is the major cost difference in living. If Indians can perform the same quality of work, then the cost factor is what determines foreign clients to look for our services. Otherwise, corporates always try to give back to the local society more than anything else. If the cost of Indian Technical Writing services comes even closer to the overseas wages, then Indians will have real problems in getting any work from abroad.

Adaptability is the key to avoid any serious competition because Indian Technical Writers will face tough competition from several countries having similar or even lower living costs. There are many examples that can be put put forward to substantiate this theory.

The average working wages in Ghana – a country facing a civil war, is several times less than the wages of Indian professionals. This makes it even more beneficial to outsource work to Ghana instead of India. A lot of French companies have opened call centers and data entry centers in Ghana, as it provides an approximate 50 percent lower cost even by Indian standards. How long will it be before such small countries will pick up the Technical Writing profession?

China, another country with living costs much less than India, has made a mission to ‘English Literate’ its masses. A rough estimate is that by 2010, nearly 60 percent of its population will be able to speak Queen’s English as fluently as we Indians do. How long will the Chinese be away from making inroads into the Technical Writing profession?

Romania, a country with a large English-speaking population with living costs similar to that of India, has already made a global impact in the area of web-based content and the day is not far when they will seek to repeat this feat in the core Technical Writing industry.

The only way of managing competition from other countries is to become adaptable and to rise up the skill ladder. Because from what I know, Indian Technical Writing is based on three pillars of US, UK, and Canada and if any of these pillars moves away, the whole industry setup here will start shaking. After all, how many Indian Technical Writers work 100 percent for Indian markets and just for the Indian audience?

Communication Expert

Good Communication skills are the most desired feature for an Indian Technical Writer, but in the future, it will become an absolute necessity.

As Doug Firebaugh once said, “Communication is really all anyone ever gets paid for ultimately. If you cannot effectively communicate, then you will pay and not get paid.”

Today, the world is not as big as it used to be but has shrunk to a very small radius. Now, it really does not make an inch of a difference to an Indian Technical Writer whether the documentation is written for local or international markets. The outsourcing boom has placed the entire Indian Technical Writing Industry as an outsourcing based industry. But even today, the level of communication skills, both written or spoken, of many Indian Technical Writers is not adequate at the global level.

To face the high tides of tomorrow, we must prepare ourselves to be the best of the best – having excellent communication skills in both verbal and written media. People still don’t know the effect and power of good communication as many companies still lose good projects primarily due to poor communication. The proposals of even good companies are drafted so badly that the work is lost even if the companies are able to perform that work with utmost efficiency.

Even more important aspect of good communication is the localization for proper audience. With words like “prepone”, one can only create confusion in overseas minds as prepone is the product of the Hinglish (Indian English) lingo most of us are subjected to. Therefore, the future Technical Writer will evolve as a linguistic expert strong enough to create different sets of thoughts for different audiences.

In the words of Irish poet William Butler Yeats, “Think like a wise man but communicate in the language of the people.”

Unless we prepare ourselves as a professional society to increase the communication level of our members, we will face real tough times in the near future. The future calls us to have not only good, but also near perfect communication skills.

Perfect Tool Master

Acrobat, PageMaker, Framemaker, Word, PowerPoint, Excel, Quark Express, Visio, SnagIT, Robohelp, more and yet more tools.

This list can be easily made long enough to cover an entire page. With the evolution of Indian Technical Writing industry, there is an enormous growth in types and number of tools. Earlier, tools were not available for specific tasks but now the problem arises to choose the best tool out of so many different options available in the market.

With the increase in the number of tools in the market, the prime area of concern for Indian Technical Writers has shifted from “mastering a single tool” to becoming “Proficient” in several tools. The world is full of unique things and our clients happen to belong to that unique clan of people. What appeals to one may actually be disregarded by others, so to be an efficient Technical Writer of global competence, one must become proficient in all tools of the trade so that one can work according to the client needs and not by the tools one is just familiar with.

As new versions of tools are launched at very short intervals, it becomes difficult for the already load-struck Indian Technical Writers to learn even the new functions of the same tool, leave alone learning absolutely new tools. But this negligence of new technology in turn creates problems, as the new technology provides high efficiency, which is the requirement of the future Technical Writing industry.

Therefore, it has become essential for all Indian Technical Writers to become truly the “Perfect of the Perfects” by attaining a high level of proficiency in all kinds of Technical Writing tools available today.

So, as Indian Technical Writing professionals, unless we are more Adaptable, and become Communication Experts and Perfect Tool Masters, we will find it really hard to survive in the highly competitive world where the success and failure are separated by a thin line. In order to face the rising competition, we must act now to climb the skill ladder to remain high above the windy seas of global markets and secure a stable and peaceful place at the earliest.

In the words of Antoine de Saint, “Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.”

About the Article

This article originally appeared in Vol 9 (Dec 2004) issue of TechCraft, the monthly newsletter of TWI. It is reprinted here with slight modifications. Trackback URL for this entry is: http://helpguru.wordpress.com/2008/01/29/evolving-roles-and-desired-qualities-for-indian-technical-writers-a-glimpse-into-the-future.

 

Hello world!

Welcome to HelpGuru! You will soon find news, tutorials, tips & tricks, FAQ’s and much more related to the world of electronic & print help. Don’t forget to bookmark your very own resource bank!