Fear fades with humility

I got my communications training in real time. I didn’t feel the anguish that many people feel in front of a crowd . . .  until that day in Denton, Texas.  I was invited to give a presentation on modifying personal computers for use by persons with disabilities. An easy and familiar subject, because I modified one of the TRS-80 computers to be controlled by an especially designed joystick so that a high school aged gymnast who broke his neck in a training accident could use the computer. 

The auditorium was full, maybe the largest crowd I have ever addressed. Most of the audience was made up of students and faculty in the occupational therapy field.  The first two rows were reserved for their clients, people with a variety of physical disabilities.  Lots of white canes, wheel chairs, and the like.

I was doing a pretty good job of explaining how the system was modified and wanted to drive home the point that these modified home computers were a cost effective solution compared to any other options available in the market.  I exclaim, “The really nice thing about these mass produced computers is that they don’t cost you an arm and a leg.”  As I finished my statement, I realized that many of the folks in the first two rows can’t use their arms or legs.  I stand there in stunned silence, expecting a shouted response or unified gasp from the audience.  Nothing but silence.  It seemed like 5 minutes, but I’m told I resumed my talk after about 15 seconds of regaining my composure.

After that, I knew that there was nothing I could do in front of a crowd that would embarrass me.

Speaking to a Crowd


http://www.usccb.org/bible/readings/043018.cfm
Acts 14:5-18
John 14:21-26


Many people, when asked to rank stressful situations, would often rank getting up to speak in front of a large group of people somewhere between dealing death in their family and a tax audit.  The fear is very real, a combination of not wanting to look foolish, especially while addressing a topic that may not be familiar to the audience and, well, the audience itself – this large group of strangers that may or may not care about the message you are trying to deliver and who have so many ways of showing they don’t care for or don’t like what you have to say.  At least that’s what you have convinced yourself.

While I was going to school, I was blessed with a pretty sharp mind, easily grasping math and science and doing well with spelling and most other tasks.  I was not a fast reader or writer, though. You see, I am dyslexic. The International Dyslexia Association say that “dyslexia refers to a cluster of symptoms, that result in people having difficulties with specific language skills, particularly reading. Students with dyslexia often experience difficulties with both oral and written other language skills, such as writing, and pronouncing words and writing.”

I was able to compensate for my slow reading and writing through hard work and a photographic memory. I managed to do well in grade school, junior high, and high school, and really enjoyed science and math.  As I approached college, I knew that I wanted to go into electrical engineering.  In fact, I knew that I wanted to be a guitar amp designer, perhaps the world’s best.  After all, I had managed to get a job repairing amplifiers and electronic organs in 2 local music stores while I was still in high school.

When I went to Purdue University, the electrical engineering curriculum did not include much in the way of language, English, or communications courses.  I had already “passed out” of those requirements based on subjects I took in high school.  So I had a full dose of electronics courses, some physics, and an introduction into computer languages, which was in the business school.  Almost nothing to prepare me for the communications needs required to state a case for something to be done (or not) in either a written or spoken manner.  I was good with facts, details, and numbers, but really didn’t have any experience in public speaking, writing to inform, or debate.

As my schooling progressed, I found that my guitar amplifier design skills did not match my desire to be the best ever.  I didn’t have the gut feel for what worked and didn’t work as well.  Luckily, I took a beginning course in digital logic design.  My classmates struggled with the concepts involved and perhaps the extra layer of abstraction that in my mind made things really easy.  I advanced to become proficient the art of computer architecture, design, and simulation.  I had picked up programming skills from the business school, and spent most of my time studying in the electrical engineering library.

One thing I used to do between studies was to go through the magazine rack in the library which had all sorts of electrical engineering trade journals.  These monthly publications covered the vast interests and disciplines of the electrical engineering field.  One of the magazines did a particularly good job of following the newest trends in real components, including the digital integrated circuits that I had become so familiar with. I remember seeing the first article that Intel did on their new device, the microprocessor.  It was a single component which had all of the logic for a simple computer inside.  Not the memory or any of the other parts of a complete system, but I knew that was going to be something big.  I wrote a letter to Intel, letting them know that I was an engineering student that was interested in their proprietary product, but, being a student, could not afford the high cost of their microprocessor technical manuals.  A week later, Intel sent me not one but four technical manuals.  I devoured them, using one as the basis for a computer simulation class I was just starting.  

My new direction in life was to be a small computer designer.  Upon graduation, I was offered a job in Silicon Valley with National Semiconductor.  In my spare time, I would attend the monthly Homebrew Computer Club meetings held at the Stanford Linear Accelerator Auditorium.  I was at the Wilbur and Orville Wright moment of the personal computer era.  Steve Jobs and Steve Wozniak from the garage shop Apple, Inc where there, along with other geeks and engineers.  All of us were building computers at home and freely shared what we were working on.

OK, time to jump ahead in this story.  I get hired by Radio Shack to design their first personal computer.  Just over a year from the date I was hired, we are in production of the TRS-80 Microcomputer System, with a retail price of $599 complete with monitor and cassette recorder for data and program storage.  I was the designer and programmer for the whole system.  I was soon asked to give speeches on the making of the computer, which was pretty easy, because I understood the subject so well.

I was finally getting my communications training in real time. To be honest, I didn’t feel the anguish that many people feel in front of a crowd . . .  until that day in Denton, Texas.   I was invited to give a presentation on modifying personal computers for use by persons with disabilities.  Again, an easy and familiar subject, because I modified one of the TRS-80 computers to be controlled by an especially designed joystick so that a high school aged gymnast who broke his neck in a training accident could use the computer. 

The auditorium was full, maybe the largest crowd I have ever addressed.  Most of the audience was made up of students and faculty in the occupational therapy field.  The first two rows were reserved for their clients, people with a variety of physical disabilities.  Lots of white canes, wheel chairs, and the like.

I was doing a pretty good job of explaining how the system was modified and wanted to drive home the point that these modified home computers were a VERY cost effective solution compared to any other options available in the market.  I exclaim “The really nice thing about these mass produced computers is that they don’t cost you an arm and a leg.”  As I finish my statement, I realize that many of the folks in the first two rows can’t use their arms or legs.  I stand there in stunned silence, expecting a shouted response or unified gasp from the audience.  Nothing but silence.  It seemed like 5 minutes, but I’m told I resumed my talk after about 15 seconds of regaining my composure.

After that, I knew that there was nothing I could do in front of a crowd that would embarrass me.  But I decided to learn more about the art of public speaking.

That brings us to today’s readings.

Many of the public speaking and presentation skills I found described in textbooks could be identified in the verses from Acts 14.

Know when to quit

This technique generally refers to finishing a presentation when you have given all of the relevant information, and continuing would be non-productive.  In the first reading, Paul and Barnabas were fleeing to the Lycaonian cities of Lystra and Derbe because part of their audience, the Gentiles, Jews, and their leaders where planning to attack and stone them.

Make eye contact and be aware of body language

At Lystra, Paul was doing a good job checking out the audience, in particular focusing on the crippled man in the crowd.  The crippled man’s attention demeanor was such that Paul “saw that he had the faith to be healed”. 

Make it memorable

Often a speaker will do something so unexpected that that point becomes the “take-home memory” of the whole event. When Paul called out in a loud voice “Stand up straight on your feet” and the crippled man “jumped up and walked about”, the crowd went nuts!

Identify and correct misunderstandings

The crowd immediately decided that Paul and Barnabas were the Greek gods Hermes and Zeus respectively.  Time for a celebration, our gods have arrived!  This is about as far from the Good News that was the underlying message of the tour.  The crowd responded in a manner consistent with their pagan beliefs.  Rather than accept their new found fame and glory, the Apostles Barnabas and Paul “tore their garments”, and act of showing their displeasure with the crowd.

Know the context of the audience

Oh yeah, this crowd is mostly made up of Gentiles, a friendly term for those lacking Jewish ancestry.  They were not well prepared to receive the Good News, because they didn’t understand the concept of the living God “who made heaven and earth and sea and all that is in them”.  Paul continued to try to make the point that they were merely the messengers, and that the faith in god was the power and force behind the cure of the crippled man.  That’s a lot of information to explain, and, well, he only got part of the message across.

Know when to quit

Didn’t we do this one before?  If you read into the next few verses, you will find that some of the folks that were plotting to stone Paul in Iconium have traveled to Lystra and put their original plan into action, stoning Paul, dragging him out of town, and leaving him for dead.  The Lord has other plans for Paul, and he gets up and heads on to the next town.

Give follow up information and references

When a person gives a wide ranging and complex presentation, it is often very useful to give the listeners some guidance on where to find additional clarifying information and more in-depth details.

The Gospel reading is an example of this.  The event is the Last Supper, and Jesus has been giving quite a load of information about everything that has happened is about to happen.  Jesus sums up his talk with “Whoever loves me will keep my word, and my Father will love him, and we will come to him and make our dwelling with him.”

The source of follow up information will be the Holy Spirit, for as Jesus concludes: “I have told you this while I am with you.  The Advocate, the Holy Spirit whom the Father will send in my name – he will teach you everything and remind you of all that I told you.”

Using Format