Technical Writing - Things That Technical Writers Do During a Typical Day at the Office

Sometimes people who are considering technical writing as a career ask me what a typical day in the life of a technical writer looks like. "What kind of writing does a technical writer exactly do?" they ask.

I for example work for a software company and here is what I do in a typical year:

I write user manuals, system administration guides, installation guides, quick reference guides, release notes, help files.

Technical Writing - Things That Technical Writers Do During a Typical Day at the Office

Perhaps I should also mention that, while writing these products I also consult with various Subject Matter Experts (SMEs), sometimes through e-mail and other times on the phone or through teleconferences. In some years I even travel out-of-state to meet with those SMEs who work in far away offices.

Some technical writers working for software companies help with testing the product as well by both working as a tester and also by writing the scenarios that the testers use.

I also draw diagrams and illustrations to illustrate some of the guides I write.

Here is what you might be doing if you were a technical writer working for a video game company: playing with the games to get familiar with product and writing user manuals, describing how the game is played, the stages of the game, the characters involved, etc.

No two days are alike when you're a technical writer working out there in the real world. It's an exciting career full of interesting challenges and plenty of room to grow into with new skills while making a good living at it too.

Technical Writing - Things That Technical Writers Do During a Typical Day at the Office
Check For The New Release in Health, Fitness & Dieting Category of Books NOW!
Check What Are The Top Cooking Books in Last 90 Days Best Cheap Deal!
Check For Cookbooks Best Sellers 2012 Discount OFFER!
Check for Top 100 Most Popular Books People Are Buying Daily Price Update!
Check For 100 New Release & BestSeller Books For Your Collection

If you are interested to read more about what technical writing is all about and how it can help you earn a steady living, visit http://www.learntechnicalwriting.com You might be pleasantly surprised with what you'll find out. Join the thousands who are already helped and inspired by this information provided by a Fortune 500 Senior Technical Writer. Visit today and claim your free report "How Much Do Technical Writers Make?"

watch cell phone Best Price Niagara Cutter Ts109 T Slot Shank Best Buy Kichler 15504Bk 10 Gauge Low Voltage

Technical Writing - What's the Difference Between Copy Writing and Technical Documentation?

There are 4 different goals of writing, depending on the writer and assignment in question.

Direct Dealer Stores Zone
24 Hrs Best Seller Category
New Tags Get Cheapest Price Shopping
Benefit Buy Direct Directory
Inter Brand Search
My Shopping Centre
Online store Review Directory
Only New Release Products

Writers try to

1) sell
2) teach
3) move, or
4) administer others.

Technical Writing - What's the Difference Between Copy Writing and Technical Documentation?

And these goals give rise to the following 4 different types of writing:

1) Copy writing (sell)
2) Technical writing (teach)
3) Fiction/Creative writing (move)
4) Business writing (administer).

Copy writing tries to sell products and services, as the advertisement-legend David Ogilvie always (and rightfully) maintained. And I agree with him. Until and unless someone buys something, copy writing is not good for anything.

Technical writing, on the other hand, is an answer to the basic question of HOW.

But in order for technical writing to explain the "how" of anything, there first has to be a clear definition of its "WHAT" and "WHY". Without that pre-requisite step, your technical writing can easily get lost in the woods.

This is usually expressed as the principle of knowing who "the audience" is.

This is just another way of saying that unless a technical writer is sure of the PURPOSE behind the document, that is, the manner in which the users will use the document to PERFORM certain tasks, then just explaining how something is done, may or may not get the job done.

Why?

Because there is always more than one way to describe the HOW of anything.

For example, imagine you are asked to write a technical guide on the HOW of running; a "User's Guide to Running."

If as a technical writer you immediately pull up your sleeves and start writing i, you might be in for a big trouble.

Let's say you devote chapters on strength and speed training, without ever thinking WHAT this guide is supposed to achieve, for WHAT kind of an audience.

What if it turns out that you were actually asked to write this guide for runners over 50 years old, who could care less about "strength" and "speed" but are keen about "losing weight"? That of course would require a totally different sort of technical guide, wouldn't it?

Copy writing excels as long as people buy the product; period.

Technical writing, on the other hand, excels only when the description of HOW matches the PERFORMANCE GOAL of the project's AUDIENCE (or, the project's "WHAT" and "WHY").

Technical Writing - What's the Difference Between Copy Writing and Technical Documentation?

Ugur Akinci, PhD is a Fortune 500 Senior Technical Writer who loves to share his technical writing tips, tutorials and advice with those who subscribe to his FREE Technical Writing Tips email list at http://www.learntechnicalwriting.com

Subscribe and download your FREE Special Report "How Much Do Technical Writers Make?" today!

Dr. Akinci is the author of "101 Ways to Power-Up Your Writing: Tips & Advice from a Fortune 500 Writer" http://www.powerupwriting.com

watch mobile phone Best Offer Jaypro Sports Stg 824 8 Ft