Your company's app has been down for most of the morning, and people are complaining about it online. At lunchtime a message arrives on LinkedIn from someone who writes for a technology news site. They have seen that you work on the platform team. Could you tell them what went wrong? They promise to keep your name out of it.
It is flattering to be asked, and you may even feel the public deserves a straight answer. Do not give one. Not because you have anything to hide, but because this is not your conversation to have.
Most companies have a small team, or at least one named person, who speaks to the press. They know what has been confirmed, what is still being investigated, and what the company has legal or contractual reasons not to say yet. During an incident, the facts are often still changing. A guess you share at lunchtime may be wrong by the evening, and once it is in an article, it is very hard to take back. Many employment contracts and social media policies also say clearly that only authorised people may comment.
So reply briefly and politely. Something like thank you for getting in touch, I am not able to comment, but our press team can help, followed by their contact details if you know them. That is all. Do not confirm anything, even casually. Saying I cannot talk about the database is still telling them something about the database.
Then tell someone. Forward the message to your manager or the communications team straight away, so they know a journalist is asking questions and which angle they are taking. That information is genuinely useful to them.
Be careful with the conversations around you, too. A frustrated post in a public channel or a comment on a forum can be quoted just as easily as a direct reply. Keep your frustration for your team, in private.
And if you think the company should say more about what happened, that is a fair view. Raise it inside, with the people writing the public update. A clear, honest explanation from the company will do far more good than an anonymous source in someone else's story.
– Asael Shinder
Top comments (0)