Humor as a communication technique

Subject: Humor as a communication technique
From: Andrew Plato <aplato -at- EASYSTREET -dot- COM>
Date: Mon, 15 Jun 1998 20:42:05 -0700

I have a thought for the list to ponder. This came about based on my last post.
I posted a rather satirical message about the "blueprint for a tech pubs group".
Some people got seriously offended by it. Which made me realize something I
pretty much already knew -- humor is a powerful persuasive device.

Thus the point to ponder: What is more persuasive - humor or details?

I have a theory here and I am curious to see what people say. I think that a
well written, humorous and slightly irreverent document is more persuasive and
can communicate more ideas then something that is written seriously. However,
it can also divide people quickly since it is open to greater interpretation and
conjecture. Nevertheless, I think that can be a benefit, not a hindrance.

Case in point. What moves you and makes you think more: A movie like Contact or
the Truman Show? Or a documentary on the sociological ramifications of alien
contact or loss of personal identity? Let's face it, documentaries can be
interesting, but they rarely move you or make you really think about things.

Now, let's extrapolate that idea to tech writing. Do we want readers to read
our material like robots? Or do we want them to think and ponder our ideas and
concepts. What is more useful and productive? A user armed with a good
background both conceptually and contextually or a user who can follow
directions?

I think that the more dramatic and humorous works can communicate more because
they break down the notions that communication of complex ideas and details is a
purely logical, methodical, and empirical activity. I'm not suggesting that we
all give up writing about packet filtering, mixed signal analysis, and Windows
NT services. However, in support of these dry and, let's face it, completely
boring topics couldn't we throw in a funny analogy or a funny satire?

I think readers want something more than directions. They want to feel
connected to the ideas that are being rammed down their throat. Humor and drama
are much more human elements of life than which NT service to start or the
arguments passed to the GrpRndFudPack function. I am not suggesting that we
should throw away all the technical details and write technical manuals about
funny sex noises or something. However, wouldn't it be fun to pick up a user
manual that actually made you giggle once or twice.

Ducks are funny, right. I don't know about you but I can't look at a duck and
not want to giggle. How about a manual with some ducks doing funny things.

At the risk of offending a few, is it worth it to make the majority laugh? A
good laugh -- not a "oh my God these people are morons" kind of laugh.

I'm curious to hear your ideas and thoughts. Send them along to me and I'll
post a summary in a week or so.

Quack...
.......................................................
Andrew Plato
Owner/Principal Consultant
Anitian Technology Services
www.anitian.com




Previous by Author: Re: Doc Department Blueprint
Next by Author: Re: FW: Humor vs. Tech Pubs
Previous by Thread: Re: Tools query
Next by Thread: Re: Humor as a communication technique


What this post helpful? Share it with friends and colleagues:


Sponsored Ads