There’s a new paper about how scientists should communicate with the public about climate change. It’s rather good, as is the summary that Anna Fahey at the Sightline Institute wrote of it. She draws out four key lessons, which I think are relevant for science communication in general:
- Emphasize what is known (a.k.a. Stop leading with unknowns, caveats, and disclaimers)
- Invert the standard order for reporting. (a.k.a. Start with the main point, then give the background)
- Less is more (“They recommend scientists craft simple, clear messages about what’s important and repeat them often.”)
- Stop speaking in code (a.k.a. Choose plain language over technical terms, insider jargon, and acronyms)
I’m trying to take this to heart with my own writing, and if you ever find yourself trying to explain controversial science topics to a non-expert audience it’s worth reading at least Fahey’s summary, or the original article.
I think those four key lessons are relevant for communication in general, especially communication with non-experts in a field.
‘Stop speaking in Code’ can be a helpful suggestion even when speaking with those that understand the intended meaning of particular words and acronyms, but don’t use them everyday. For example, I attended a talk the other day about Design for Reliability & Manufacturability and every time that I saw the acronym DRM placed on the board in phrases like “DRM helps improve . . .” I had to remind myself that it didn’t mean Digital Rights Management.
Yeah, that’s a good point. Even within the rather small staff of the Happiness Initiative we occasionally get tripped up by acronyms that have prior meanings to some but not all of us.