“Beyond the Technical: Teaching Professionalism…”

Technical Communication

Paul Herrick University of Alaska Anchorage

Along with poor appearance, demeanor & work habits, poor communication

ability presents a negative impression of

professionalism.

What is the goal of Technical Communications?

Technical writing/graphics/discussion is the process of communicating complex ideas in logical, concise and

unambiguous terms.

“Precision communication”.

Consider what the audience needs, not yourself.

The Metric:

In such detail that the recipient can duplicate what you have done.

One “conversant in the art”.

Consider what the audience needs, not yourself.

Additionally, a good technical communicator can

present material that does not “talk down to” a less

knowledgeable recipient while at the same time

brings the recipient up to a level of understanding

which allows them to act upon or accept what is

presented with confidence and comfort.

Paul’s Pearl of Wisdom

“If you want something from someone, make it easy for them

to give it to you.”

The technical communicator must always strive to;

MAKE IT EASY FOR THE RECIPIENT TO UNDERSTAND THE MATERIAL!

If the communication is intended to persuade the recipient (management, the Federal

Aviation Administration, etc.) to implement a recommendation;

MAKE IT EASY FOR THE RECIPIENT TO AGREE WITH THE RECOMMENDATION!

Additionally, if the communication is part of a required record (maintenance record entry,

other legally binding document) it should describe exactly what was done, no more, no

less, therefore;

MAKE IT EASY FOR THE RECIPIENT TO UNDERSTAND WHAT WAS DONE!

“Complete & Concise”

These concepts apply to all forms of technical communication.

Written

Verbal

Including computations! (math tells a “story”!)

Graphics“a picture generates a thousand words…”

WrittenGeneral Items

•All that can be typed, will be typed.•All work clean & neat (typed or not).•Third person form.

Learning to Reference Sources

In all classes which use manufacturers data or regulations, and in ALL maintenance record entries, students must specifically reference their source.

Learning to Reference Sources

According to FAR 43.9:(a) Maintenance record entries… (1) A description (or reference to data acceptable to the Administrator) of work performed.

Example 1:

Learning to Reference Sources

According to Superior Airparts Inc., O-360 & IO-360 Maintenance Manual, P/N SVMM01, Rev. B, Feb. 2007, Chap. 73 00 00, Pg. 3, “Fuel Pump Replacement”…

Example 2:

Creating Forms

•Create forms for maintenance records and recording work.•Forces them to think about what the recipient needs.•Using their own forms shows deficiencies in that process.•Organizes their efforts (planning).

Creating Forms

•Part name/description.•Part number.•Quantity.•Pricing.•Supplier info.•Etc.

Example: Parts Order Form

Learning to Use Graphics

Example“Movie Technique”

Learning to Speak

•Use correct nomenclature.•Use same “precision” as other methods.•Formal settings, plan your thoughts.•Minimize profanity.

Is it work?Absolutely!

But, someone will spend time on your work.

If it is you, you reap the reward.

If it is someone else (teacher, boss, FAA…) you will reap the penalty.

A technical writing tutorial titled :

“Technical WritingFor Aviation Maintenance”

Prepared by Paul Herrickwill be included in the conference proceedings.