Monthly Archives - June 2013

Editing versus Writing

All editors are writers but all writers aren’t editors.

I am quite sure most editors will agree with what I said above. Editing is different from writing and it is much more than proof-reading or reviewing. Those who don’t agree with that opinion, may be actually editing the content under the garb of reviewing and it’s time they start calling themselves Editors. With time, experience and bigger responsibilities, writers are poised to assume the role of an editor. It begins with prolonged exposure to a particular genre of writing, subject matter and the writing style followed. Obviously, when you know your content’s context in and out, you become an authority and can visualize the result of the smallest variations in tone and verbiage. With that, comes the attitude required to become an editor. You start looking at “drafts” and start making “edits” to make the copies read better and explain everything precisely and correctly. You begin to identify and remove the excesses. You look at documents from readers’ perspectives. You are the biggest critic.

Let’s try to answer this – How do you plan your editing?
I think you have to be pretty sure about the expected outcome. You try and match the content drafts with your visualization, make edits, rephrase, paraphrase, reorganize to get an edited version. An editor essentially intends to ensure the following:

  • Correctness of information
  • Accuracy of language
  • Logical flow of information
  • Ability to grab and sustain readers’ attention
  • Conciseness of content
  • Adherence to style guidelines

A point of caution for wannabe editors is that you should respect a writer’s style of writing and expression if it doesn’t come in the way of delivering the right quality. All of us know that we can say one thing in so many ways. However, some editors may want to stick only to their style of writing. This can hamper creativity and leave the writers with little motivation to do something new.

On the other hand, writers need to study the edits, make notes, ask questions, and prepare a personal review checklist. Using the checklist would help reduce the number of editorial changes that writers see in their future drafts.

Editing is also Mentoring
Editing is at best a feedback mechanism for writers. It tells them how to put it better and make it pleasure-to-read. When editors explain their edits either by entering descriptive comments within documents or explaining verbally while being respectful, they are bound to influence the writers positively and they are likelier to see rewarding results soon.translation english to french

Read more...

Who can become a Technical Writer?

An important question for aspiring Technical Writers – What does it take to make a good Technical Writer? The available answers could resemble a job description saying: Mastery in English Language is absolutely mandatory, Expertise in word processing and documentation tools is required, Exposure to HTML, XML and DITA is preferred and so on.

Let us find out who can become a technical writer, in a simpler manner…

The job of technical writer involves donning many roles and therefore it obviously requires a mixed bag of skills. Besides being good at written English, a technical writer has to be a conversationalist, a technology and innovation enthusiast, people-oriented and an end-user advocate.

As a conversationalist, it becomes easier for a technical writer to strike casual conversations with product designers and developers, which is the easiest way to understand the needs that must be catered by the product. On the other side, if the technical writer gets to interact with the customers or end users, the conversation skills might be handy in capturing their expectations. At times, the user documentation starts when the product or application development is mid-way where some screens are ready, some aren’t, while a number of them need to be modified according to change requests. In such scenarios, it is important to communicate with developers, testers, and architects to understand the flow of application and the functionality for various pages.

Being a technology enthusiast helps the technical writers by making them inclined to take interest in the technological advancements, evolution of products driven by the demands of future, and understanding the business logic of seemingly complex products. It pays to be able to understand the business logic, information flow or sequences depicted in flowcharts, data flow diagrams or UML diagrams.

Working in collaboration with people from different backgrounds, functions and with varying skillsets, makes humanity as the most common team bonding factor. A technical writer may do well to reason out with most people, understand and respect their constraints, be assertive yet wear a calm and cheerful demeanor. The writer must be seen as a team player and people- oriented.

Last but the most significant role is that of a user advocate. Whenever we see a change in layout of a portal or an e-commerce website, a lot of it is driven by user behavior or consumer feedback. As end-user advocates, technical writers empathize with the end-users and look at the products from the users’ perspectives. It helps them visualize the user scenarios, the expectations and of course, they might bump into some exceptions. All of this can go back towards product enhancement and continuous improvement initiatives. So, it reaches a point where Technical Writers not only create and develop product documentation but they also act as product evangelists.

If you have the above mentioned traits, you surely qualify for a technical writer job. You can either get in touch to get associated with Ascezen Consulting Pvt. Ltd. as a Technical Writer/Information Developer/Content Writer or get enrolled for a training program that helps to acquire the required skillset.youtube language translator

Read more...