Now that you\u2019ve learned about all remote work software<\/a> and you\u2019ve bought a lot of new subscriptions, it\u2019s time to actually utilize these new tools. How can you onboard your team? How can you get the most out of your new tech? How can you track that each tool is really being used?<\/strong><\/p>\n\n\n\n That\u2019s exactly what we\u2019re exploring today, because we all want to get the most out of what we\u2019re paying for.<\/p>\n\n\n\n Before the coronavirus, 44% of US companies<\/a> didn\u2019t allow remote work at all. The current work-from-home orders have placed information workers into two categories:<\/p>\n\n\n\n What camp does your team fall in? Whether or not your team already has a remote-work-enabling tech stack in place will likely affect how swiftly you can roll out additional tools. That\u2019s a fact.<\/p>\n\n\n\n What doesn\u2019t change is that every company can speed up the rollout process by more easily providing access to new tools. GoLinks<\/a> can help you create super short internal links for sharing new tools across even large organizations.<\/p>\n\n\n\n For example, let\u2019s say that you partner up with a remote mental health provider like Lyra<\/a>. The GoLink for information on how to download the app and receive mental health coaching could be go\/mental-health<\/a> or go\/cope<\/a>. Managers and colleagues can easily share this link amongst each other to make sure everyone knows about this brand new resource.<\/p>\n\n\n\n One of the most confusing things about adding new remote work tools is simply letting people know what they should be using and when they should start using it.<\/p>\n\n\n\n Even with all of the communication channels available to us (Slack, email, intranet announcements, etc.), things get lost or go unseen.<\/p>\n\n\n\n To make sure employees are using the updated tools, use GoLinks<\/a> to set up short internal links that redirect to whatever the admin dictates.<\/p>\n\n\n\n Here are some example go links:<\/p>\n\n\n\n When you switch from one tool to another, you can change what the go link redirects to. For example, go\/hr<\/a> could stop redirecting to Zenefits<\/a> and start redirecting to Gusto<\/a>. This way, employees automatically get taken to the right tool without having to remember to make the switch.<\/p>\n\n\n\n Very early on in the rollout process (before team members are touching the new tool), you need to set up rules and expectations.<\/p>\n\n\n\n Here are some examples of what this looks like:<\/p>\n\n\n\n For every tool you need to rollout, take time to ask yourself some important questions. How do I expect different groups or teams to use this tool? What user settings and access levels do I need to set up? How can I preset other settings or dummy content to put the desired organization in place?<\/p>\n\n\n\n Turn the answers to these questions into your pre-rollout checklist, and during and after rollout schedule time to review the effectiveness of the settings you chose.<\/p>\n\n\n\n People on your team will have very different levels of comfort with the new tool. That\u2019s why it\u2019s important to provide a variety of optional resources for getting started (in addition to a mandatory meeting or video you might have).<\/p>\n\n\n\n Make it easy for people who need extra help to drop in and get that support.<\/p>\n\n\n\n Here are some ways you can help out your team:<\/p>\n\n\n\n Essentially, you need to get creative. You can\u2019t all gather around one person\u2019s computer at the office. You can\u2019t walk over to each other\u2019s desks. You need to drum up ways for people to ask questions and get support during the rollout process, so they don\u2019t procrastinate getting their questions answered.<\/p>\n\n\n\n In today\u2019s SaaS world, there\u2019s a whole lot of overlap between various tools. Some vendors take the approach of being an \u201call in one\u201d solution and add in lots of features so their users don\u2019t have to integrate a bunch of different tools. Other vendors like to focus on just the main function or feature.<\/p>\n\n\n\n Review what you\u2019ve bought recently with what you already have. A new tool you just subscribed to might be able to satisfy the reason you bought it while also eliminating the need for other products in your tech stack. For example, if an e-commerce company purchases Privy<\/a> for analytics-powered pop-ups to save carts before abandonment, then that company might be able to do away with Active Campaign<\/a> and start using Privy not only for pop-ups but all emails too.<\/p>\n\n\n\n For any new tool you use (whether it can replace multiple subscriptions or not) you want to get the most of it. Let\u2019s say you purchased Zendesk Support Suite. You\u2019ll want to make sure your customer success team is getting the most out of that purchase by surfacing all features. A great way to do this is to create go links for different feature areas like go\/support<\/a>, go\/selfservice<\/a>, go\/analytics<\/a>, and go\/knowledge<\/a>. This allows quick access to all of the parts of that platform.<\/p>\n\n\n\n You\u2019ve paid for new subscriptions to remote work tools that will help your company succeed, but do you know if they\u2019re getting used?<\/p>\n\n\n\n Some tools are easier to track than others. For example, a project manager will know who doesn\u2019t update Jira cards and who does.<\/p>\n\n\n\n But reviewing the utilization of other tools can be more challenging. If you have a page where you post announcements, company news, or stand up summaries, you can\u2019t immediately know the percentage of adoption.<\/p>\n\n\n\n This is another place where using\u00a0GoLinks<\/a>\u00a0can provide a ton of value. The platform lets administrators track the usage of the internal short links. You can see how many times a particular go link is used in any time period. If you find issues, you can remind your team or reconsider the necessity of that tool.<\/p>\n\n\n\n <\/p>\n\n\n\nSpeed up the rollout process<\/h2>\n\n\n\n
\n
![\"Work](\"https:\/\/media3.giphy.com\/media\/XymXANrzgI4k6FL6zr\/giphy.gif\")
<\/a>\n<\/div><\/figure>\n\n\n\nInstantly share tool replacements<\/h2>\n\n\n\n
![\"GoLinks](\"https:\/\/images.golinks.io\/blog\/wp-content\/uploads\/2021\/02\/18195551\/image-48-1024x744.png\")
<\/figure>\n\n\n\n\n
![\"Changing](\"https:\/\/images.golinks.io\/blog\/wp-content\/uploads\/2021\/02\/18195548\/image-47-1024x384.png\")
<\/figure>\n\n\n\nPreset rules, tool organization, and expectations around use<\/h2>\n\n\n\n
\n
![\"Remote](\"https:\/\/images.golinks.io\/blog\/wp-content\/uploads\/2021\/02\/18195546\/image-46-1024x394.png\")
<\/figure>\n\n\n\nHost virtual onboarding workshops and coworking sessions<\/h2>\n\n\n\n
\n
![\"Remote](\"https:\/\/images.golinks.io\/blog\/wp-content\/uploads\/2021\/02\/18195544\/image-45-1024x542.png\")
<\/figure>\n\n\n\nUse every feature you\u2019re paying for<\/h2>\n\n\n\n
![\"Go](\"https:\/\/images.golinks.io\/blog\/wp-content\/uploads\/2021\/02\/18195604\/image-49-1024x449.png\")
<\/figure>\n\n\n\nReview which tools are getting used and which aren\u2019t<\/h2>\n\n\n\n
![\"\"](\"https:\/\/images.golinks.io\/blog\/wp-content\/uploads\/2024\/09\/25102826\/golinks_blog_footer_cta_2x_2x-1.webp\")
<\/figure>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"