On the Safe Side podcast Episode 35: Safety technology and the value of storytelling
EDITOR’S NOTE: Each month, the Safety+Health editorial team discusses important safety topics, and interviews leading voices in the profession.
In Episode 35, the S+H team dives into the January issue’s feature story on adoption and acceptance of safety technology. Additionally, senior safety consultant and keynote speaker Jack Jackson discusses how safety professionals can use storytelling to spread safety messages.
Web links associated with this episode:
- “Safety technology: adoption, acceptance and use”: This feature story by Associate Editor Alan Ferguson appears in the January issue of Safety+Health magazine.
- My Story: Safety pros share their journey into the EHS profession in this monthly feature. Email [email protected] to submit your safety origin story.
- “Tell them a story”
- January is the National Safety Council’s Member Appreciation Month
- “Improving nanomaterial Safety Data Sheets: CPWR launches e-tool”
- “Fungi that can make outdoor workers sick are now nationwide, researchers say”
| Don’t miss the next one: Sign up to be notified in an email about each new “On the Safe Side” podcast episode. |
Subscribe:
- Search your favorite podcast app for “On the Safe Side.” Please let us know if your podcast app doesn’t show a listing.
- Subscribe to the podcast using the RSS feed.
More ways to listen:
- The podcast’s media page on the Safety+Health website
- Apple Podcasts
- Google Podcasts
- Soundcloud
- Stitcher
- Spotify
- YouTube
- Amazon Music (Say "Alexa, play On the Safe Side podcast.")
- Audible
Catch up:
Listen to past episodes.
Post a comment to this article
Safety+Health welcomes comments that promote respectful dialogue. Please stay on topic. Comments that contain personal attacks, profanity or abusive language – or those aggressively promoting products or services – will be removed. We reserve the right to determine which comments violate our comment policy. (Anonymous comments are welcome; merely skip the “name” field in the comment box. An email address is required but will not be included with your comment.)