If you are seeing this message, you may be experiencing temporary network problems. Please wait a few minutes and refresh the page. If the problem persists, you may wish to report it to your local Network Manager.
It is also possible that your web browser is not configured or not able to display style sheets. In this case, although the visual presentation will be degraded, the site should continue to be functional. We recommend using the latest version of Microsoft or Mozilla web browser to help minimise these problems.
Wiley InterScience | |||||||||
![]() Risk AnalysisVolume 17 Issue 4, Pages 489 - 498 Published Online: 29 May 2006 © 2010 Society for Risk Analysis Published on behalf of the Society for Risk Analysis
Abstract | References | Full Text: PDF (Size: 1007K) | Related Articles | Citation Tracking Mixed Messages in Risk Communication Copyright 1997 Society for Risk Analysis KEYWORDS Concepts • technical • colloquial • meaning • confusion ABSTRACTThe exchange of risk information between risk managers and affected parties is frequently hampered by differences in the understanding or interpretation of many words and phrases. Much of the terminology used by risk practitioners may have different "technical" and "colloquial" meanings, resulting in "mixed messages" in risk communication. Several words and concepts commonly used in risk management that may be resulting in these "mixed messages" are discussed. These include primary underlying concepts, such as the various meanings of the word "risk" itself, as well as the perplexity of the notions of "safety vs. zero risk" and "probability". The potential "mixed messages" of the derived concepts of "significant vs. nonsignificant", "negative vs. positive results", "conservative assumptions", "population vs. individual risk", "relative vs. absolute risk", and "association vs. causation" are shown to range from mild confusion to the completely opposite interpretation of these words and expressions. Suggested strategies for recognizing and mitigating the use of words and phrases which may create unnecessary confusion are presented. Received June 19, 1996; revised April 29, 1997 |
|
![]() | |||||||