How to Deal with Tragedy on Social Media

Share this post

I don’t have to tell you that we are living in the age of social media. It is now the norm to see news of momentous events coming to us on Twitter before CNN or any other network can report it. Pictures and video, sometimes ugly and chilling, are sent from phones before reporters or even first responders can arrive. It all goes viral in a matter of minutes. Families and friends of victims learn that their loved ones may be involved in some horrific event before they can be contacted by authorities. Sometimes, it is all too much to take in.social media in times of tragedy

Tragedies take many forms. There can be national events which touch us as a country, or local catastrophes which are felt within the community. Sometimes, as stories unfold through social media, there is an impulse to comment and share. When your business takes a step into the world of news events, however, caution should be observed. It’s all a matter of protecting your brand.

In the aftermath of the Boston Marathon bombings of 2013 we posted a blog which we hoped everyone would understand came from the heart, but there were still some who accused us of being self-serving. Even with the best of intentions, and tiptoeing gently, we couldn’t remain above criticism. It served to remind us, however, that our reputation is our most precious commodity.

Because of the volatile nature of social media, and the hair-trigger reality of everyday events, I established an editorial policy regarding major news events which probably merits sharing. This reflects an approach based on our commitment to sharing useful, informative content, combined with a civic-minded need to contribute to our community, and a commonsense respect for the CommonPlaces brand and image.

A Practical Social Media Response Plan

Freeze all planned content posts

Most of us schedule social media updates through services like HootSuite or TweetDeck. At the risk of something embarrassing slipping out, the prudent thing to do is to put everything on hold. Never assume that that infographic on Pinterest, or that meme intended for Facebook is benign.

Assume editorial command for any branded social media

Make sure that your staff posts comments solely on their own social media accounts. I’m not advocating censorship, here, just assurance that opinions or statements aren’t coming from a branded site.

Stop ‘- Observe ‘- Listen

Initially, make absolutely no statement of any kind. None. Follow every development closely, but don’t believe everything that comes across your various sized screens. Listen to your co-workers and management to assess general impressions and feelings.

First statement must be brief, sincere, factual

Put raw emotions aside. When the time is appropriate, you should confront the situation, but not dwell on it. Don’t allow any brand messaging to creep in. Keep it short.

Remember that a time of crisis affects everybody. Be smart, and realize that it could be a crisis for your brand, as well.

Insights

600+ articles to give you key insights for your projects

8 Simple Ways to Improve Your Website Security

8 Simple Ways to Improve Your Website Security

With cyber threats becoming increasingly sophisticated, it’s essential to implement robust security measures to safeguard your website and the sensitive information it holds.  You know that you need to keep your website safe from the bad guys, but once you venture...

The Dilemma of Estimates

The Dilemma of Estimates

Estimates serve as the cornerstone of any website project, providing clients with a roadmap for budgeting, planning, and expectation management. They offer a glimpse into the intricate tapestry of tasks, timelines, and resources needed to bring a website to life....

Config Sync Overview

Config Sync Overview

When Drupal 8 was released, it came with Configuration Syncing functionality. This has been a staple ever since for Drupal 9, Drupal 10, and beyond. Configuration Syncing was a game changer and one of my favorite features in Drupal Core. The days before config sync...