{"id":3072,"date":"2017-11-29T11:43:56","date_gmt":"2017-11-29T11:43:56","guid":{"rendered":"https:\/\/www.culturesummit.co\/?p=3072"},"modified":"2022-04-20T09:46:41","modified_gmt":"2022-04-20T13:46:41","slug":"communicating-change-across-distributed-teams","status":"publish","type":"post","link":"https:\/\/www.culturesummit.co\/communicating-change-across-distributed-teams\/","title":{"rendered":"A Step-by-Step Strategy for Communicating Change Across Distributed Teams"},"content":{"rendered":"
There is just one thing you can be sure about in your business – and that is the fact that it\u2019s going to change. Whether you\u2019re someone that drives change for the sake of progress or someone who tries to resist change, it\u2019s inevitable – and there\u2019s nothing you can do to stop it.<\/span><\/p>\n What you can<\/i> do is control how you handle change, including the way you communicate it to your team. This is even more important if you\u2019re part of a company with distributed teams.<\/span><\/p>\n Delivering the right message to the right people in the right way is key to ensuring your team understands:<\/span><\/p>\n Get this wrong, and you risk alienating employees and hindering how effectively change is implemented.<\/span><\/p>\n Managing this is a challenge in businesses with just one facility. When teams are distributed over multiple facilities and locations, the risks increase substantially, which is why it\u2019s all the more important to implement and follow a strategy when communicating change.<\/span><\/p>\n We\u2019ll run through a step-by-step strategy for communicating change across distributed teams in just a moment, but before that, let\u2019s go over a few things you can do (and probably should do) to prepare to communicate more effectively, in general.<\/span><\/p>\n It\u2019s vital that to communicate change – and to communicate, period – distributed teams all use the same web-based communication platform (and use it in the same way).<\/span><\/p>\n I use Slack<\/a>, but there are countless other options if that doesn\u2019t fit your needs or budget. Here are just a few:<\/span><\/p>\n Once you\u2019ve picked a platform, you need to lay out the foundations of how you\u2019re going to use it. This will, to an extent, evolve over time. However, it\u2019s important that you\u2019re all on the same page from day one.<\/span><\/p>\n The majority of these platforms revolve around two key features:<\/span><\/p>\n Private messaging is just that – a private, instant messaging service between two or more users.<\/span><\/p>\n \u201cBoards, groups or channels\u201d (which are essentially<\/span> all the same thing, just with different titles) are where messages you want to distribute to specific departments, teams, or the company as a whole, are shared.<\/span><\/p>\n This is where ensuring all users are on the same page – and by that<\/span> I mean that they\u2019re all using the tool in the same way – is so important.<\/span><\/p>\n Not all members of staff are going to have access to every \u201cboard,\u201d so it\u2019s critical you ensure the right team members have access to the right information.<\/span><\/p>\n For instance, you might have a board for \u201ccustomer service,\u201d another for \u201csales,\u201d and another for \u201cHR.\u201d Chances are your sales team isn\u2019t going to need to view the same messages as your customer service team, and vice versa. They only need access to boards that concern them and their work.<\/span><\/p>\n Time zones commonly cause problems for distributed teams. If you have teams operating in wildly different time zones, there\u2019s a high chance there will be minimal, if any crossover, between working hours.<\/span><\/p>\n To counteract this, you can establish \u201cgolden hours\u201d – a time period in which the maximim number of staff <\/span>(ideally all staff, although that\u2019s not always possible) will be at work.<\/span><\/p>\n Figure out when this crossover is, and ensure all key communications are made during this time.<\/span><\/p>\n While some announcements need to made<\/span> using a specific process (like the one we\u2019re going to go through in just a moment), there are going to be many more snippets of information that are worth sharing<\/span>, but don\u2019t call for a formal announcement.<\/span><\/p>\n Unfortunately, it\u2019s easy for these sorts of things to fly under the radar and not be announced – at all.<\/span><\/p>\n Fostering a culture in which sharing information becomes second nature to your team is key.<\/span><\/p>\n For this to happen, when a staff member hears or receives new information, they should:<\/span><\/p>\n Some information can be shared informally. I\u2019m referring to things a team member or members need to know, but that <\/span>do not have a substantial direct impact on them – either positive or negative.<\/span><\/p>\n Other information, such as significant internal changes that will impact employees\u2019 day-to-day lives, calls for a more formal approach – like the following strategy, which is what I use to communicate change<\/span> to distributed teams.<\/span><\/p>\n Before you can broadcast your message, you need to define exactly what your message will be. This might sound<\/i> straightforward – you just say what needs to be said, right?<\/span><\/p>\n Unfortunately, the effectiveness of your attempt to communicate change, especially across distributed teams, begins with what you say and how you say it. For that reason, defining exactly<\/b> what you\u2019ll say ahead of time is essential.<\/span><\/p>\n To do this, you need to establish:<\/span><\/p>\n Use this information to craft a statement that divulges your message clearly and concisely. Before signing off on the message, ensure it only contains essential<\/b> information, and that nothing within it is liable to be misunderstood. Consider the connotations of the words you use, too. \u201cX is leaving the company\u201d has very a different connotation than \u201cX is pursuing a new opportunity\u201d – the first one can potentially be construed in a negative light.<\/span><\/p>\n This step ensures that multiple people don\u2019t attempt to deliver the message – all potentially in slightly different ways.<\/span><\/p>\n One<\/b> person at each of your premises should be assigned the task of delivering the message, or, if it\u2019s to be delivered via your communication platform (more on this in step 3), handling questions and follow-ups.<\/span><\/p>\n There is no one \u201cbest\u201d way to deliver your message – it all depends on your company culture, and the nature of the message itself.<\/span><\/p>\n Townhall announcements<\/b><\/span><\/p>\n A \u201ctown hall\u201d announcement (i.e. a public announcement made in an open domain to as many members of staff as possible) ensures everyone hears the same message, at the same time. This greatly limits the odds of the message being misheard or wires getting crossed.<\/span><\/p>\n Townhall announcements are best suited to positive messages that help bring the company together. Do not use this method for delivering potentially<\/span> bad news (unless you want to instantly shroud your offices in negativity<\/span>).<\/p>\n Line managers to teams<\/b><\/span><\/p>\n This might also be referred to as \u201cthe cascade.\u201d It involves messages being passed \u201cdown the ladder\u201d from management to the level below them, and then again to the level below that.<\/span><\/p>\n It\u2019s well-suited to the delivery of \u201cbad news,\u201d since it limits how many people will hear the message at once, and allows for (if needed) the message to be delivered in different ways, to different people. It also means concerns can be raised and addressed immediately.<\/span><\/p>\n Be aware, however, that this method is vulnerable to the \u201cChinese whisper effect.\u201d However well you plan your message, each additional person involved in delivering it increases the odds it will be changed or diluted.<\/span><\/p>\n Internal communications platform<\/b><\/span><\/p>\n Messages delivered this way are usually presented in a written format, which eliminates any margin for error: you have total control over the wording used and you will know, without doubt, what\u2019s been conveyed to each employee. It also makes it really easy for employees to follow up with questions, and in turn, for you to answer them.<\/span><\/p>\n On the downside, this method can be seen as impersonal or even cowardly – like you\u2019re intentionally hiding behind a screen (which, perhaps, you are).<\/span><\/p>\n It\u2019s almost inevitable that when you announce change<\/span>, employees are going to have questions. As part of your strategy for communicating change, you need to be prepared to answer them. Specifically, you need to formulate a process for employees who want to ask questions, raise concerns, and provide feedback.<\/span><\/p>\n Your internal communications platform is ideal for this.<\/span><\/p>\n If you used it to deliver the initial message, just let employees know that any questions or comments should be posted there. You may even want to create a specific \u201cgroup\u201d just for delivering the message and addressing follow ups. This ensures all information pertaining to the change is stored in one location.<\/span><\/p>\n Even if you\u2019re delivering your message by another means, you might still want to consider using your internal communications platform for handling follow-ups.<\/span><\/p>\n In all cases, you need to:<\/span><\/p>\n You might also want to consider setting up follow-up meetings, or at the very least, repeating the message and encouraging staff to speak up if there\u2019s anything<\/i> they\u2019re unsure of.<\/span><\/p>\n If you aren\u2019t prepared to deal with the aftermath of your message, and you don\u2019t provide a clear route for asking and answering questions, you risk staff trying to decipher what\u2019s happening between themselves (or in other words, gossiping). Employees will raise and ponder questions with each other, which will inevitably lead to incorrect conclusions and more often than not, a worried and unhappy workforce.<\/span><\/p>\n Of course, there is no foolproof approach to communicating change – especially when it\u2019s bad news. You can, however, control the impact of the change on staff morale by taking the time to plan how to communicate it and preparing to deal with what happens after.<\/b><\/span><\/p>\n Have you ever been responsible for communicating change – either to distributed teams or a single team? How did you do it and what, if anything, would you do differently next time? It\u2019d be great to hear your thoughts if you have the time to leave a comment below.<\/i><\/b><\/span><\/p>\n","protected":false},"excerpt":{"rendered":" There is just one thing you can be sure about in your business – and that is the fact that it\u2019s going to change. Whether you\u2019re someone that drives change for the sake of progress or someone who tries to resist change, it\u2019s inevitable – and there\u2019s nothing you can do to stop it. What […]<\/p>\n","protected":false},"author":6,"featured_media":1678,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[52,53,42,43],"yoast_head":"\n\n
Preparing to Communicate More Effectively for Distributed Teams<\/h2>\n
Implement a company-wide communications platform<\/h3>\n
\n
\n
Establish \u201cgolden hours\u201d<\/h3>\n
Foster a transparent culture of continuous communication<\/h3>\n
\n
A Step-By-Step Strategy for Communicating Change<\/h2>\n
Step 1: define your message<\/h3>\n
\n
Step 2: decide who\u2019s best-placed to deliver the message<\/h3>\n
Step 3: decide the best channel for delivering the message<\/h3>\n
Step 4: prepare to handle follow-ups<\/h3>\n
\n