Technical Writing

48
About Technical Writing Writing Just Enough

description

A short presentation - used in a company training program - purposed to describe the 5 W's of technical writing.

Transcript of Technical Writing

Page 1: Technical Writing

AboutTechnical Writing

Writing Just Enough

Page 2: Technical Writing

Recipe

What is “technical” writing?

What is it’s purpose?

How is technical writing done?

When should it be done?

Who does technical writing?

How can you know when technical writing is done well?

Page 3: Technical Writing

What is “technical writing”?

(and where do you find “technical writers?”)

Page 4: Technical Writing

Technical writing is…

© 2008 Joe Gollner

Page 5: Technical Writing

Technical writing is not…

Page 6: Technical Writing

Technical writing is done to…Purpose

Page 7: Technical Writing

Define and order standard processes…

Page 8: Technical Writing

Ensure critical processes are standardized…

Page 9: Technical Writing

Present accepted norms for understanding &  recognizing quality…

Page 10: Technical Writing

Qualify acceptance& rejection metrics…

Page 11: Technical Writing

Simplify complexity…

Page 12: Technical Writing

Codify allowable error and excess in specific environments…

Page 13: Technical Writing

Detail operational necessities…

Page 14: Technical Writing

Reference systems demands and tolerances…

Page 15: Technical Writing

Highlight & describe risk…

Page 16: Technical Writing

Structure available knowledge in support of research…

Page 17: Technical Writing

Identify useful content…

Page 18: Technical Writing

Assemble parts into a whole…

Page 19: Technical Writing

Show the way…

Page 20: Technical Writing

Coordinate functionalities…

Page 21: Technical Writing

Facilitate requirements …

Page 22: Technical Writing

Achieve success

Page 23: Technical Writing

Write 12 volume boEdit

Distribute

How is technical writing done?

Page 24: Technical Writing

Determine purpose of communication

Page 25: Technical Writing

Analyze the audience2

Page 26: Technical Writing

Choose most effective format, organization, and style

3

Page 27: Technical Writing

Collect information4

Page 28: Technical Writing

5. Organize and outline information

Page 29: Technical Writing

Write first draft; then revise and edit

Page 30: Technical Writing

When  should technical      writing be done?

Page 31: Technical Writing

Officially…

Page 32: Technical Writing

During initial requirements gathering phase of any project

As project          requirements are modified

Whenever new versions of existing “deliverables”are contemplated

Page 33: Technical Writing

Normally…

Page 34: Technical Writing

If you want your customers to walk away from product failures….

Page 35: Technical Writing

If you want to reduce customer calls to your technical support team….

Page 36: Technical Writing

If you want customers to “get” your product and become “affiliate” marketing push….

Page 37: Technical Writing

If you want each version of your product to flow smoothly into an established market….

Page 38: Technical Writing

If you want customers who really like your company and your product…….

Page 39: Technical Writing

then technical writing ought to be included in every step of your business plan.

Page 40: Technical Writing

Who does technical writing?

Page 41: Technical Writing

An experienced, professional technical writer

OR

Page 42: Technical Writing

An experienced writerOR

Page 43: Technical Writing

An experienced professional with access to a 

professional content editor

Page 44: Technical Writing

How can you know when technical writing is done well?

Page 45: Technical Writing

The intended audience will “tell” you.

> Market share

Vocal brandloyalists

Fewer customer complaints

Fewer product returns

Fewer calls to tech support

Product that works

Positive spin

Page 46: Technical Writing

RecapUse professional technical writers.

Start the writing aspects of project when you’re conducting initial requirements collection.

Be ready to provide useful, current information.

Follow the “recipe” – K.I.S.S. principle DOES work!

Quality of final product is directly related to level of technical writer involvement in project development.

Page 47: Technical Writing

Millman, Barry, How to Create Great User Documentation: A Hands‐On Course; IgetItNow Training (Internet Training Program), 2008

Reep, Diane C., Technical Writing: Principles, Strategies, and Readings; 3rd ed., Allyn and Bacon, Boston, 1997

Jones, Dan, Technical Writing Style; Allyn and Bacon, Boston, 1998

Gretchen Hargis, Michelle Carey, AnnKilty Hernandez, Polly Hughes, Deirdre Longo, Shannon Rouiller, Elizabeth Wilde, Developinf Quality Technical Information: A handbook for Writers and Editors; 2nd ed., IBM Press, Prentice Hall, New Jersey, 2004

Page 48: Technical Writing

Please feel freeto let me know what you think

about this presentation.

PowerPoint BureauAt: [email protected]

orplace your comments on Slideshare.

Thanks!