Aspects of Technical Writing that nobody knows or cares about

Most people I tell I’m a Technical Writer think it’s interesting, funny or weird.

I don’t really fit the profile – I’m a young, savvy, experienced professional & I’ve been in the field for +10 years.

When I tell them what I do for a living, most people think I’m a translator. They can’t really get the bigger picture of what Technical Writing entails.

  • Did you know?

Most Technical Writers not only write manuals, but write manuals while concurrently updating departments about what other departments are doing and help to keep a good BALANCE OF INFORMATION supply within a company.

  • Did you know?

Technical Writing duties often range from the merely banal, to CRM, data retention and training services while on-going work is taking place – as AN ADDED BENEFIT.

  • Did you know?

There are lots of fallacies about what Technical Writers do. Most people don’t know what challenges Technical Writing involves so they assume that the only task is at the computer, whereas most of the work is done while CROSS-REFERENCING BETWEEN MIGRATING VERSIONS, PEOPLE AND PRODUCTS.

  • Did you know?

As a rule, most Technical Writers know an average of over 50 software solutions and can implement them for your documentation?

  • Did you know?

When a Technical Writer says he’s working from home he’s probably producing more than if he was working in the office; He’ll probably finish the document sooner at home, but odds are against him if he’s running around from department to department.

  • Did you know?

Technical Writing as well as Social Media DO play a part in StartUp strategy and money raising efforts in the same way; both challenge the user to see what is really happening while covering up all the buggy stuff nobody wants to relate to (Huh? Yes I’m not joking).

  • Did you know?

The average Technical Writer has a considerably higher than average IQ in relation to the general population.

  • Did you know?

Most Technical documentation is written from the middle towards the introduction and the end (outwards)?

  • Did you know?

Not everyone can be a Technical Writer.

  • Did you know?

The average manual can take from a few days to a few months to write.

Questions & Input are Welcome!

One thought on “Aspects of Technical Writing that nobody knows or cares about

  1. My two cents from my experience as User Experience professional working with technical writers:
    a/ if a technical writer has a hard time explaining it/documenting it – the functionality is probably over complicated. AKA – should be simplified before it gets to the end users
    b/ technical writers supporting Product managers and UX professionals have a critical role in helping define the on screen strings and terminology of an application/solution/product. Especially when the product is targeting an and English speaking country and the PM, UX prof is not a native-English-speaker.
    This often makes the end solution easier to understand, and therefore more usable to the end users (e.g. minimizing the need to ask for help, etc.)

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: