{"id":34674,"date":"2022-04-06T07:13:02","date_gmt":"2022-04-06T11:13:02","guid":{"rendered":"https:\/\/centricconsulting.com\/?p=34674"},"modified":"2023-11-14T12:48:00","modified_gmt":"2023-11-14T17:48:00","slug":"do-you-still-use-email-to-collaborate-with-other-companies-heres-why-thats-a-mistake","status":"publish","type":"post","link":"https:\/\/centricconsulting.com\/blog\/do-you-still-use-email-to-collaborate-with-other-companies-heres-why-thats-a-mistake\/","title":{"rendered":"Do You Still Use Email to Collaborate With Other Companies? Here\u2019s Why That\u2019s a Mistake"},"content":{"rendered":"
When collaborating with other companies on a project, too many businesses rely on email and other outdated practices. Complications, headaches and frustrations ensue. Roadblocks can stem from anything from a lack of trust between organizations, a lack of clarity on tools and processes to key differences in culture.<\/p>\n
But it doesn\u2019t have to be this way. Over the past several years, businesses have learned a great deal about asynchronous work and the tools that make it possible. Okta\u2019s 2022 Businesses At Work Report<\/a> found that, for the first time, five collaboration tools topped the list of fastest-growing apps.<\/strong><\/p>\n It\u2019s time to take the lessons learned about remote work<\/a>, and the tools that make remote work seamless,<\/p>\n Phil Simon, workplace technology expert and author of “Reimagining Collaboration: Slack, Microsoft Teams, Zoom and the Post-Covid World of Work,” recently wrote a blog post<\/a> describing the common roadblocks of inter-organizational projects: \u201cSadly and despite my best efforts, the short project had quickly devolved into a morass of misunderstandings, scheduling snafus and duplicate work.\u201d<\/p>\n In other words, a lack of clarity on the way to accomplish work and by whom led to major issues.<\/p>\n The solution: Begin every inter-organizational endeavor with a project charter designed to smooth the way for efficient, effective collaboration.<\/strong> The charter should address:<\/p>\n By creating a project charter, you\u2019ll cut down on inefficiency, leaving team members to focus on important work (instead of wasting time coordinating tasks, searching for documents, requesting status updates and the like).<\/p>\n Choosing a collaboration tool isn\u2019t as simple as saying \u201cWe\u2019ll use our Microsoft Teams<\/a> channel, here\u2019s a login and password.\u201d You must consider a number of important details.<\/p>\n Modern collaboration tools allow for tight control of what guests can and can\u2019t see and do. First, you\u2019ll need to decide what exactly you\u2019ll be sharing and what you\u2019ll allow access to within the tool. A non-disclosure agreement may be necessary.<\/strong><\/p>\n It\u2019s also prudent to establish processes to ensure you\u2019re not granting a guest access and then never turning that access off. Once a project wraps up, it\u2019s easy to lose sight of those external relationships. For instance, Slack allows users to create guest accounts with ticking clocks. Their access automatically lapses on a certain date. Many tools allow you to set up notifications to check if you\u2019re still using a specific channel.<\/p>\n Finally, you\u2019ll need to decide what is considered appropriate use within the tool. Does your external partner need to sign the same kind of HR agreement you require of employees? How tightly does this need to be controlled? Are there any applicable regulatory or corporate compliance requirements?<\/p>\n Whenever two organizations collaborate for the first time, there\u2019s going to be a learning curve. Identify any gaps up front, then take the time to educate one another where needed.<\/p>\n One team may need to learn a new collaboration tool. Formal training is invaluable. Simon points out that many organizations mistakenly assume people will \u201cjust pick it up.\u201d And while they may be able to independently figure out how to navigate the tool\u2019s basic functions, they\u2019ll end up missing out on a ton of useful capabilities to make collaboration more seamless.<\/strong><\/p>\n Another area of potential learning involves remote work. If one team is more adept at working remotely<\/a> and asynchronously, it may be a worthwhile investment to communicate some basic norms.<\/p>\n Although training may feel like it slows a project down, the efficiency gains down the road more than make up for it. Especially training around a collaboration tool. \u201cIf you don\u2019t figure this stuff out, at some point people say \u2018Screw it, I\u2019m going to give up and use email,\u2019\u201d Simon says. Reverting to e-mail, by the way, is the last thing you want to do. Studies have shown that nearly two-thirds of employees<\/a> ignore their inboxes.<\/p>\n Of course, not every inter-organizational project will call for a charter or an investment in learning a new collaboration platform. Email is perfectly sufficient for simple tasks that people can accomplish with a few exchanges over a short period of time.<\/strong><\/p>\n That rule doesn\u2019t apply to longer-term, more complex endeavors or relationships involving two or more organizations. In these cases, it\u2019s worth the initial investment in agreeing to how you\u2019re going to work together and completing any necessary training on the selected collaboration tool and work norms.<\/p>\nStep 1: Agree to The Rules of Engagement<\/h2>\n
\n
Step 2: Put Appropriate Controls in Place<\/h2>\n
Step 3: Invest in Time for Learning<\/h2>\n
\n
No One Size Fits All<\/h2>\n