Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-plugin-hostgator domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home4/ubica/public_html/wp-includes/functions.php on line 6114

Warning: Cannot modify header information - headers already sent by (output started at /home4/ubica/public_html/wp-includes/functions.php:6114) in /home4/ubica/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home4/ubica/public_html/wp-includes/functions.php:6114) in /home4/ubica/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home4/ubica/public_html/wp-includes/functions.php:6114) in /home4/ubica/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home4/ubica/public_html/wp-includes/functions.php:6114) in /home4/ubica/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home4/ubica/public_html/wp-includes/functions.php:6114) in /home4/ubica/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home4/ubica/public_html/wp-includes/functions.php:6114) in /home4/ubica/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home4/ubica/public_html/wp-includes/functions.php:6114) in /home4/ubica/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home4/ubica/public_html/wp-includes/functions.php:6114) in /home4/ubica/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
{"id":12098,"date":"2016-11-11T15:34:10","date_gmt":"2016-11-11T20:34:10","guid":{"rendered":"https:\/\/www.ubicastrategy.com\/?p=12098"},"modified":"2024-07-23T15:38:58","modified_gmt":"2024-07-23T20:38:58","slug":"the-antidote-to-office-gossip","status":"publish","type":"post","link":"https:\/\/www.ubicastrategy.com\/the-antidote-to-office-gossip\/","title":{"rendered":"The Antidote to Office Gossip"},"content":{"rendered":"

Sara*, the CEO of a software company, had recently fired an employee. In a heartbeat, gossip about the who, how and why of the termination began spreading through the office grapevine like chicken pox in a kindergarten classroom.<\/p>\n

The copy-room commentary was flat-out false. But the buzz quickly infected her team with a\u00a0rumor that more people were on the chopping block, even though this was far from the truth.<\/p>\n

How did the gossip get to that\u00a0point? Why do workplace rumors happen in the first place? And what can be done to prevent them?<\/p>\n

Up to\u00a090% of conversations qualify as gossip<\/a>. That means it is almost certain that you are pretty regularly a rumor initiator or enabler, listening without deterrence. And it\u2019s not just cafeteria and hallway whispers that contribute to the problem:\u00a0Nearly\u00a015% of all work email<\/a>\u00a0can be categorized as gossip.<\/p>\n

To be sure,\u00a0not all gossip is bad<\/a>\u00a0for an organization. But the kind that poisons rapport, maligns reputations, and contaminates cooperation is what you need to take action\u00a0against. To do this, it\u2019s important to go back to the basics and understand\u00a0what gossip really is<\/a>: casual and unconstrained conversation, about absent third parties, regarding information or events that cannot be confirmed as being true.<\/p>\n

Gossip is born out of uncertainty. When we are uncertain, we are inclined to make assumptions. Why? Uncertainty creates a knowledge void that must be filled with actual, or in many cases artificial, information. The antidote, of course, is open and honest communication with your employees. Here are a few strategies to try.<\/p>\n

Give Them the Low-Down<\/strong><\/h3>\n

A big change in a company \u2014 firing a top executive, shutting down an office \u2014\u00a0can be a tripwire for explosive speculations if the\u00a0change isn\u2019t communicated clearly to employees. Because uncertainty creates a knowledge void, be sure to quickly fill the void with facts before suspicion becomes \u201cfact.\u201d The more quickly you spill the beans, no matter how painful doing so might be, the less likely people are to start panicking.<\/p>\n

For example, before seeking to acquire another firm, Joe, the CEO of a midsize consumer packaged goods company, gathered his\u00a0team and revealed the\u00a0company\u2019s financials in great detail. Next, he outlined the process for acquisition with a well-defined timeline. In the following weeks, rather than counterproductive chatter clamoring through the ranks, Joe\u00a0saw her team become more cohesive, rallying together to pull the company through a challenging and transformative time.<\/p>\n

Get the Scoop from Employees<\/strong><\/h3>\n

Katrina, the COO of an international software company, made a decision to terminate her entire sales team over the course of a year. It was a move she knew would send the company into a frenzy. To mitigate this, she regularly asked questions\u00a0before<\/em>,\u00a0during<\/em>, and\u00a0after<\/em>\u00a0the process. She wanted to know:<\/p>\n