Login | Register
The Engineer's Place for News and Discussion®


OH CR4P!

"An expert is a man who has made all the mistakes, which can be made, in a very narrow field." -Niels Bohr

These words frame the OH CR4P! blog, a place which encourages engineers to discuss, reminisce, and learn about mistakes, failures and mishaps made by those who have become "experts" the hard way.

Previous in Blog: Oil Spill – Engineering Failure or Necessary Evil?   Next in Blog: Classic Case Study: Hartford Civic Center
Close

Comments Format:






Close

Subscribe to Discussion:

CR4 allows you to "subscribe" to a discussion
so that you can be notified of new comments to
the discussion via email.

Close

Rating Vote:







3 comments

Writing, Documenting, Paperwork, Oh My!

Posted May 23, 2012 11:00 AM by cheme_wordsmithy

If there's one thing I've gathered from being around engineers and engineering students, it's that most don't like to write. Writing is just a difficult and time consuming obstacle. Documenting is that seemingly unnecessary step that slows down the work of brilliant people who can do it all in their heads. Paperwork is the obligatory bore that was instated by the devil himself as some sort of sadistic punishment.

(Image Credit: Engineeringwritingsolutions.com -->)

Who can blame them? When it comes to design documents and paperwork, even I'll admit that writing can be incredibly dull and bland. And it may seem like all it is doing is taking time away from the work we actually want to do.

Ultimately, however, writing and documenting is an essential part of the engineering process. Companies, firms, and individuals who slack off in this area are bound to encounter problems down the road.

DO Show Your Work

It may seem trivial, but writing down what you do is very important. Whether it's for a design or a process, proper internal documentation ensures that somebody else can learn or translate your work, and pick up where you left off if necessary. It also makes referencing past work more convenient and much less painful.

Documenting is by nature a very unselfish task. If you died, became ill, or left your workplace tomorrow in the middle of the project, what kind of hole would you leave? Would the company be able to function without you? The answer is more likely to be yes if you've left behind good documentation. Poor documentation is thus assumed by some to be a method for job security.

In very small companies, there may be some truth to this. But ultimately, engineers who document their work are worth more than those who try to ignore it. Employers risk far more by allowing professionals to keep all the knowledge and know-how in their own heads.

Proper documentation of design specs and parts is also critical for passing the torch to other departments. This type of communication helps reduce mistakes when last minute changes are necessary and allows for parts to move from design to manufacturing & production quickly and affordably.

People Actually Have To Read This…

If you've ever read an instruction manual, then you know how laughably confusing they often are. From a manual for setting up a clock on a desktop penholder:

"The beginning accounts the hour: At position number that show the 'DATA' from 00 change into 59 circulations are gradually decrease, current a minute for setting up the number gradually decrease open to start, the same a number for setting up gradually decrease also start"

Granted, this extreme example is the fault of terrible language translation, but many similarly confusing explanations are due just to bad writing. Engineers are typically good at making sure explanations are technically accurate, but don't bother to consider the human element of style and form that makes it readable. Often this includes a lack of needed pictures and diagrams, undefined or confusing terminology, or a lack of consideration for the technical competency (or lack thereof) of the intended audience.

(Credit: Dilbert by Scott Adams)

Unfortunately, user manuals usually take a back seat to everything else because they aren't directly related to product performance or profit for the company. But proper instructions and directions are directly related to customer satisfaction, and a confused or dissatisfied customer often becomes a lost customer; hence the value of a technical writer or engineer who takes the time to write with accuracy and clarity.

Striving for Excellence

The engineering profession is marked by a characteristic strive for excellence. But this attitude should be reflected in all aspects of the work, including the sometimes dreaded task of writing and documenting. It may seem worthless, but the tedium will pay unseen dividends through the hassles that will be avoided. Those who've experienced the consequences of bad writing and poor document control know this all too well.

References

Arena Solutions - Documenting Designs

Professional Engineering - Poor Document Control

Reply

Interested in this topic? By joining CR4 you can "subscribe" to
this discussion and receive notification when new comments are added.

Comments rated to be Good Answers:

These comments received enough positive ratings to make them "good answers".

Comments rated to be "almost" Good Answers:

Check out these comments that don't yet have enough votes to be "official" good answers and, if you agree with them, rate them!
2
Power-User

Join Date: Jan 2008
Location: Tucson, AZ
Posts: 233
Good Answers: 2
#1

Re: Writing, Documenting, Paperwork, Oh My!

05/23/2012 1:53 PM

...most of the time, you're getting "graded" on getting the 'correct' numerical values on test questions in engineering colleges, not upon 'writing' accompanying / supporting information for "dummys" to read.

...and, isn't that *why* those yellow & black "...for Dummys..." books are around?

__________________
...and the Devil said: "...yes, but it's a DRY heat..!"
Reply Good Answer (Score 2)
Guru
Hobbies - CNC - New Member Hobbies - DIY Welding - New Member Engineering Fields - Electromechanical Engineering - New Member

Join Date: Aug 2007
Posts: 8728
Good Answers: 100
#2

Re: Writing, Documenting, Paperwork, Oh My!

05/23/2012 2:04 PM

I have to admit. as for as a place for everything and everything has a place. was on my desk. the bigger the desk, the more that can be stacked on it.

Odd thing was, even though I was criticized it for have a 'mess', from some of my sterile and at times anal colleagues. I have a tendency to keep my desk fluid, and I the documentations I was well informed and current as well as in tuned with all of my projects. When asked a technical question. I can respond immediately, or if I needed references, I could retrieve it from my desktop, (by the way, what I mean as desktop is from the top of my desk, or somewhere in between the top of the desk and the top of the stack of papers) The information was stratified. Sure it was a mess, but it was an organized mess. very similar to the work I am called into to work upon. Starts out as Chaos, ends up as Organized Chaos.

I do enjoy a neat well organized documentation, but I do not do it on a daily basis. Only when I no longer have a comfort feeling do I 'reboot' and organize. which is approx. once a month.

__________________
phoenix911
Reply
Member

Join Date: Sep 2010
Location: Indianapolis
Posts: 8
#3

Re: Writing, Documenting, Paperwork, Oh My!

05/24/2012 6:41 AM

Kudos! A Maserati with three tires isn't "almost" as good as the whole thing. When we strive for excellence in most of our work, but neglect to do so in all important areas, we are delivering the three-tired product. Communication--of which documentation is a critical subset--is too often relegated to a task of lesser importance, and that might be true if you were designing a system for yourself on a desert island. However, even you, sitting on that sandy beach, contemplating your navel, would be fuzzy six months from now when you ask, "why did I put that widget there?" We become our own customers at some point.

So there's no escaping: we must communicate; we must document. We must do so with excellence. How embarrassing to be rescued from that island and have the deck hand thumb through the scratchings on our coconut shell manual only to say, "this doesn't make any sense!"

__________________
"We have met the enemy, and he is us." -- Walt Kelly
Reply Score 1 for Good Answer
Reply to Blog Entry 3 comments
Interested in this topic? By joining CR4 you can "subscribe" to
this discussion and receive notification when new comments are added.

Comments rated to be Good Answers:

These comments received enough positive ratings to make them "good answers".

Comments rated to be "almost" Good Answers:

Check out these comments that don't yet have enough votes to be "official" good answers and, if you agree with them, rate them!
Copy to Clipboard

Users who posted comments:

70AARCuda (1); Flaxfield (1); phoenix911 (1)

Previous in Blog: Oil Spill – Engineering Failure or Necessary Evil?   Next in Blog: Classic Case Study: Hartford Civic Center