Final Analysis and Interpretation (Chapter 13 Adrian and Downs)

Surprise surprise, the first thing we learn in this chapter is that the analysis is subject to interpretation. “No one has been able to delineate completely and specifically how interpretation ought to be performed.” (Location 5000). I guess this means this chapter is a really good teaching point — on how to learn when something isn’t cut and dried.

It has a lot of summary list.

Dewey’s legendary reflective thinking pattern:

  1. Define the problem
  2. analyze the problem
  3. Set up criteria for a solution
  4. List alternative solutions
  5. Choose a solution

DeWine steps for communication audits:

  1. Problem Identification
  2. Set an objective
  3. Proposed method or solution
  4. Reality
  5. Implementation
  6. Evaluation

Adrian and Downs method (the one we follow):

  1. Synthesize data
  2. develop focal area
  3. Identify and define problems
  4. Identify organizational criteria for success
  5. Consider the organization’s stages of development
  6. Form tentative conclusions
  7. Finalize conclusions
  8. Make client-centered recommendations

Brainstorming is the process of constructing a case, not discovering a case. It requires time and should not be rushed.

Not all problems are communication problems.  Sometimes it is communication that needs to be resolved, sometimes it is other issue that need to be resolved but communication can help in resolving it.

Problem definition is tricky. Auditors sense problems, and then try to use their creativity to define and express the problems. Errors that can occur in the process include:

  1. Not discovering a problem that exists
  2. Identifying a problem that does not exist
  3. Trying to solve the wrong problems
  4. Failing to probe deeply enough to understand the problem.

To avoid this the auditor should do as comprehensive search as possible. Then make sure whether an observation is a problem or not. Test different ways of characterizing the problem. Probe the nature of problems fully.

We need benchmarks for comparison. We need to tailor ideas to the organization. It isn’t a one size fits all.  Various national cultures may suggest different needs and options.

From all this we form tentative conclusions, and then test them, check assumptions, use intuitive powers, while being wary of false cause-effect traps.  It is too easy to see causation in correlation. For that matter, looking for causes in systems, where an event can be both cause and effect, is a dangerous thing to do.

Once you go through all that, finalize conclusions, and make client-centered recommendations.

 

Reference

Cook, D., Patterson, J., Downs, C. (2004). Final Analysis and Interpretation.In Downs, C., Adrian, A. (Eds), Assessing Organizational Communication: Strategic Communication Audits(Location 990-1281), New York, NY: The Guildford Press.

 

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.