Notes on Conducting the Survey<\/strong><\/h2>\n\n\n\nTo maximize responses and insights, we recommend following a few practices when putting together and conducting your survey:<\/p>\n\n\n\n
\n- Keep it short.<\/strong> Too many questions may drive employees to navigate away prematurely. <\/li>\n\n\n\n
- Leave room for comments.<\/strong> Offer optional text boxes for employees to qualify or expand upon their answers.<\/li>\n\n\n\n
- Clarify that answers won\u2019t result in disciplinary action.<\/strong> Some IT questions may ask about times employees have routed around prescribed processes or tools. While workarounds are not best practices, the goal of the survey is to understand these instances and solve for them rather than reprimand shadow IT culprits. If employees fear reprimand, they might not answer truthfully. Anonymizing the survey can help employees feel freer to answer truthfully as well.<\/li>\n\n\n\n
- Set a deadline.<\/strong> Deadlines add urgency and set a definitive date for you to stop collecting and start compiling and analyzing answers. <\/li>\n<\/ul>\n\n\n\n
Questions Around Solutions and Tools<\/strong><\/h2>\n\n\n\n![\"Woman's](\"https:\/\/jumpcloud.com\/\/wp-content\/uploads\/2021\/12\/pexels-george-milton-7015034-683x1024.jpg\")
<\/figure>\n\n\n\nQuestion 1:<\/strong> Which tools do you use most frequently? <\/h3>\n\n\n\nStart by gauging what is<\/em> working. This question will pinpoint which tools serve a viable need. Even if you end up changing your tech stack this year, make sure you keep the tools frequently mentioned in these responses or replace them with tools that can serve the same needs.<\/p>\n\n\n\nQuestion 2:<\/strong> Do you use non-company tools to accomplish your work? Which tools, and what do you use them for?<\/h3>\n\n\n\nThis question will help you identify gaps in your tools or their functionality. Employees may use non-company tools either because the company hasn\u2019t provided a tool or because the provided tool is insufficient. <\/p>\n\n\n\n
When employees use their own tools, they introduce vulnerabilities into the organization, from putting company information into non-approved software to granting third-party tools direct access to company infrastructure. Understanding why employees deem a tool insufficient can help you assess solutions that prevent employees from needing to source unapproved tools to complete their work. Consider including this follow-up question to determine the gaps in your stack\u2019s functionality:<\/p>\n\n\n\n
Follow-up: Why do you use the tools you listed instead of the company-provided ones? <\/h4>\n\n\n\n
Suggested multiple choice answers:<\/p>\n\n\n\n
\n- We don\u2019t have one for this purpose.<\/li>\n\n\n\n
- It\u2019s frustrating\/hard to use. <\/li>\n\n\n\n
- I don\u2019t know how to use it. <\/li>\n\n\n\n
- It can\u2019t do everything I need it to. <\/li>\n\n\n\n
- It\u2019s not compatible with other tools or devices. <\/li>\n\n\n\n
- I liked the old one better. <\/strong>(Include this option if you recently switched tools).<\/strong> <\/li>\n\n\n\n
- Other. (Give employees the chance to explain their other reasons for using a different tool.) <\/li>\n<\/ul>\n\n\n\n
If responses indicate that your company\u2019s tool suite lacks critical functionality, consider looking for ways to consolidate tools rather than investing in a new one just to fill the identified gap. For example, if your company needs a more user-friendly MFA solution, consider one that can accomplish other things as well \u2014 JumpCloud\u00ae<\/sup><\/a>, for example, offers multi-factor authentication (MFA)<\/a> as part of its entire cloud directory platform, which includes identity and access management (IAM), mobile device management (MDM), and single sign-on (SSO). Combining tools can be an effective cost-savings tactic. <\/p>\n\n\n\nFor responses that indicate a lack of buy-in or understanding of how to use the tool, consider hosting training or making educational resources available. Many vendors provide user-oriented educational resources for their tools \u2014 pulling a few of these and circulating them to coworkers can be a quick and easy first step. <\/p>\n\n\n\n
Question 3:<\/strong> Are there tools we offer that you don\u2019t use? Which ones?<\/h3>\n\n\n\nIdentifying areas where you could reduce licenses or shed tools altogether can generate significant cost-saving wins and offset the costs of new technology you may need to invest in.<\/p>\n\n\n\n
Question 4:<\/strong> Which tools do you dread or avoid using?<\/h3>\n\n\n\nThis question helps identify tools that slow productivity or generate frustration, potentially leading to shadow IT<\/a>. If you notice commonly named tools in responses, try offering more training or educational resources on usage, as a first step. If this doesn\u2019t improve usage or satisfaction, investing in a different tool may cost less than the security vulnerabilities that workarounds create. <\/p>\n\n\n\nQuestions Around Employee Devices<\/strong><\/h2>\n\n\n\n![\"Hands](\"https:\/\/jumpcloud.com\/\/wp-content\/uploads\/2021\/12\/pexels-michael-burrows-7129038-683x1024.jpg\")
<\/figure>\n\n\n\nQuestion 5:<\/strong> Are you comfortable with your operating system?<\/h3>\n\n\n\nIt\u2019s no secret that people have strong feelings about their OS preference, and imposing Windows on a lifelong Mac user (or vice versa) can seriously slow their productivity. Workplaces are becoming more heterogeneous in device types, and newer infrastructure and device management tools are rising to the challenge of supporting them. JumpCloud, for example, is an OS-agnostic<\/a> directory platform; that flexibility extends to its MDM, MFA, and other capabilities.<\/p>\n\n\n\nQuestion 6<\/strong> (for organizations using company-issued devices): Do you use your personal device for any work tasks? For which applications or tasks do you use your personal device? <\/h3>\n\n\n\nIf employees are using their personal devices for a variety of tasks, this could indicate a need for a bring your own device (BYOD) policy or MDM tool. Completing company tasks on a non-compliant personal device places your company data at risk. <\/p>\n\n\n\n
Note that a BYOD policy<\/a> shouldn\u2019t be considered without also addressing employee privacy. If you\u2019re not ready to implement a mandatory, full-fledged, BYOD program, consider using a minimally intrusive MDM tool that allows users to opt in. This way, users can choose to make use of the BYOD program if they like using email, messaging, or other work apps on their phone without fear of endangering company data or the company violating their privacy.<\/p>\n\n\n\nQuestion 7: <\/strong>Are you experiencing problems with any of the following on your device?<\/h3>\n\n\n\nSuggested multiple choice answers:<\/p>\n\n\n\n
\n- Storage space<\/li>\n\n\n\n
- Speed<\/li>\n\n\n\n
- Functionality<\/li>\n\n\n\n
- Hardware problems (e.g., broken keyboard or port)<\/li>\n\n\n\n
- Other<\/li>\n<\/ul>\n\n\n\n
Always ensure devices are functioning optimally to prevent slowdowns or complications from old or faulty machines. If there\u2019s room in the budget, consider following up with a question about additional hardware they might need. Low-cost items like adapters can go a long way toward powering productivity.<\/p>\n\n\n\n
Questions Around Technical Issues <\/strong><\/h2>\n\n\n\n![\"404](\"https:\/\/jumpcloud.com\/\/wp-content\/uploads\/2021\/12\/erik-mclean-sxiSod0tyYQ-unsplash-1024x683.jpg\")
<\/figure>\n\n\n\nQuestion 8: <\/strong>Do you know how and where to report technical issues?<\/h3>\n\n\n\nQuestion 9:<\/strong> Do you know where to go for technical or security questions?<\/h3>\n\n\n\nQuestion 10:<\/strong> Have you noticed any recurring technical issues that affect your ability to complete your work?<\/h3>\n\n\n\nEfficient issue reporting reduces the time needed to rectify problems and prevents shadow IT and security blind spots. Ensure employees understand and follow issue reporting protocols to bolster your organization\u2019s overall productivity, efficiency, and security. <\/p>\n\n\n\n
If responses indicate that technical reporting processes aren\u2019t clear, try starting off 2022 with a quick refresher course on recognizing and addressing IT problems.<\/p>\n\n\n\n
Questions Around Resource Access<\/strong><\/h2>\n\n\n\n![\"Laptop](\"https:\/\/jumpcloud.com\/\/wp-content\/uploads\/2021\/12\/pexels-markus-spiske-8247921-1024x683.jpg\")
<\/figure>\n\n\n\nEven the best tools in the world can\u2019t power productivity if your employees can\u2019t access them. Many organizations have switched to remote or hybrid-remote work, making resource access a challenge. Lack of easy access, or access that is cumbersome or confusing, slows efficiency and negatively impacts the user experience. <\/p>\n\n\n\n
Question 11<\/strong> (for hybrid-remote organizations): Is it easier for you to access the tools you need to get work done when working remotely or in the office?<\/h3>\n\n\n\nSuggested multiple choice answers:<\/p>\n\n\n\n
\n- Remotely<\/li>\n\n\n\n
- In the office<\/li>\n\n\n\n
- They are equally accessible<\/li>\n<\/ul>\n\n\n\n
Ideally, employees should feel that access to resources is equally easy when in the office or working remotely. Employees aren\u2019t generally interested in the back-end processes that power their experience; they simply want to be able to log on and work, regardless of where they are. Consistency and simplicity are key factors in delivering on those expectations.<\/p>\n\n\n\n
Question 12: <\/strong>How easy is it for you to access everything you need to complete your work?<\/h3>\n\n\n\nSuggested multiple choice answers:<\/p>\n\n\n\n
\n- Very easy<\/li>\n\n\n\n
- Somewhat easy<\/li>\n\n\n\n
- Somewhat difficult<\/li>\n\n\n\n
- Very difficult<\/li>\n<\/ul>\n\n\n\n
Follow-up question: Which resources are difficult to access? <\/h4>\n\n\n\nQuestion 13:<\/strong> Do you feel overwhelmed by the number of login credentials or accounts you need to keep track of?<\/h3>\n\n\n\nAs we digitize processes and multiply the number of cloud-based tools in our stack, we ask employees to track more and more credentials. This is a detriment to both the business and the employee: it tends to frustrate employees and create password fatigue<\/a>, which creates security vulnerabilities for the business. <\/p>\n\n\n\nSingle sign-on (SSO)<\/a> prevents this by facilitating secure authorization to all an employee\u2019s apps using just one set of secure credentials. With SSO, employees only have to remember one set of credentials, and businesses actually enjoy a more <\/em>secure login process via secure protocols like SAML instead of just the simple (and vulnerable) username and password. <\/p>\n\n\n\n
Questions Around Solutions and Tools<\/strong><\/h2>\n\n\n\n<\/figure>\n\n\n\nQuestion 1:<\/strong> Which tools do you use most frequently? <\/h3>\n\n\n\nStart by gauging what is<\/em> working. This question will pinpoint which tools serve a viable need. Even if you end up changing your tech stack this year, make sure you keep the tools frequently mentioned in these responses or replace them with tools that can serve the same needs.<\/p>\n\n\n\nQuestion 2:<\/strong> Do you use non-company tools to accomplish your work? Which tools, and what do you use them for?<\/h3>\n\n\n\nThis question will help you identify gaps in your tools or their functionality. Employees may use non-company tools either because the company hasn\u2019t provided a tool or because the provided tool is insufficient. <\/p>\n\n\n\n
When employees use their own tools, they introduce vulnerabilities into the organization, from putting company information into non-approved software to granting third-party tools direct access to company infrastructure. Understanding why employees deem a tool insufficient can help you assess solutions that prevent employees from needing to source unapproved tools to complete their work. Consider including this follow-up question to determine the gaps in your stack\u2019s functionality:<\/p>\n\n\n\n
Follow-up: Why do you use the tools you listed instead of the company-provided ones? <\/h4>\n\n\n\n
Suggested multiple choice answers:<\/p>\n\n\n\n
\n- We don\u2019t have one for this purpose.<\/li>\n\n\n\n
- It\u2019s frustrating\/hard to use. <\/li>\n\n\n\n
- I don\u2019t know how to use it. <\/li>\n\n\n\n
- It can\u2019t do everything I need it to. <\/li>\n\n\n\n
- It\u2019s not compatible with other tools or devices. <\/li>\n\n\n\n
- I liked the old one better. <\/strong>(Include this option if you recently switched tools).<\/strong> <\/li>\n\n\n\n
- Other. (Give employees the chance to explain their other reasons for using a different tool.) <\/li>\n<\/ul>\n\n\n\n
If responses indicate that your company\u2019s tool suite lacks critical functionality, consider looking for ways to consolidate tools rather than investing in a new one just to fill the identified gap. For example, if your company needs a more user-friendly MFA solution, consider one that can accomplish other things as well \u2014 JumpCloud\u00ae<\/sup><\/a>, for example, offers multi-factor authentication (MFA)<\/a> as part of its entire cloud directory platform, which includes identity and access management (IAM), mobile device management (MDM), and single sign-on (SSO). Combining tools can be an effective cost-savings tactic. <\/p>\n\n\n\nFor responses that indicate a lack of buy-in or understanding of how to use the tool, consider hosting training or making educational resources available. Many vendors provide user-oriented educational resources for their tools \u2014 pulling a few of these and circulating them to coworkers can be a quick and easy first step. <\/p>\n\n\n\n
Question 3:<\/strong> Are there tools we offer that you don\u2019t use? Which ones?<\/h3>\n\n\n\nIdentifying areas where you could reduce licenses or shed tools altogether can generate significant cost-saving wins and offset the costs of new technology you may need to invest in.<\/p>\n\n\n\n
Question 4:<\/strong> Which tools do you dread or avoid using?<\/h3>\n\n\n\nThis question helps identify tools that slow productivity or generate frustration, potentially leading to shadow IT<\/a>. If you notice commonly named tools in responses, try offering more training or educational resources on usage, as a first step. If this doesn\u2019t improve usage or satisfaction, investing in a different tool may cost less than the security vulnerabilities that workarounds create. <\/p>\n\n\n\nQuestions Around Employee Devices<\/strong><\/h2>\n\n\n\n<\/figure>\n\n\n\nQuestion 5:<\/strong> Are you comfortable with your operating system?<\/h3>\n\n\n\nIt\u2019s no secret that people have strong feelings about their OS preference, and imposing Windows on a lifelong Mac user (or vice versa) can seriously slow their productivity. Workplaces are becoming more heterogeneous in device types, and newer infrastructure and device management tools are rising to the challenge of supporting them. JumpCloud, for example, is an OS-agnostic<\/a> directory platform; that flexibility extends to its MDM, MFA, and other capabilities.<\/p>\n\n\n\nQuestion 6<\/strong> (for organizations using company-issued devices): Do you use your personal device for any work tasks? For which applications or tasks do you use your personal device? <\/h3>\n\n\n\nIf employees are using their personal devices for a variety of tasks, this could indicate a need for a bring your own device (BYOD) policy or MDM tool. Completing company tasks on a non-compliant personal device places your company data at risk. <\/p>\n\n\n\n
Note that a BYOD policy<\/a> shouldn\u2019t be considered without also addressing employee privacy. If you\u2019re not ready to implement a mandatory, full-fledged, BYOD program, consider using a minimally intrusive MDM tool that allows users to opt in. This way, users can choose to make use of the BYOD program if they like using email, messaging, or other work apps on their phone without fear of endangering company data or the company violating their privacy.<\/p>\n\n\n\nQuestion 7: <\/strong>Are you experiencing problems with any of the following on your device?<\/h3>\n\n\n\nSuggested multiple choice answers:<\/p>\n\n\n\n
\n- Storage space<\/li>\n\n\n\n
- Speed<\/li>\n\n\n\n
- Functionality<\/li>\n\n\n\n
- Hardware problems (e.g., broken keyboard or port)<\/li>\n\n\n\n
- Other<\/li>\n<\/ul>\n\n\n\n
Always ensure devices are functioning optimally to prevent slowdowns or complications from old or faulty machines. If there\u2019s room in the budget, consider following up with a question about additional hardware they might need. Low-cost items like adapters can go a long way toward powering productivity.<\/p>\n\n\n\n
Questions Around Technical Issues <\/strong><\/h2>\n\n\n\n<\/figure>\n\n\n\nQuestion 8: <\/strong>Do you know how and where to report technical issues?<\/h3>\n\n\n\nQuestion 9:<\/strong> Do you know where to go for technical or security questions?<\/h3>\n\n\n\nQuestion 10:<\/strong> Have you noticed any recurring technical issues that affect your ability to complete your work?<\/h3>\n\n\n\nEfficient issue reporting reduces the time needed to rectify problems and prevents shadow IT and security blind spots. Ensure employees understand and follow issue reporting protocols to bolster your organization\u2019s overall productivity, efficiency, and security. <\/p>\n\n\n\n
If responses indicate that technical reporting processes aren\u2019t clear, try starting off 2022 with a quick refresher course on recognizing and addressing IT problems.<\/p>\n\n\n\n
Questions Around Resource Access<\/strong><\/h2>\n\n\n\n<\/figure>\n\n\n\nEven the best tools in the world can\u2019t power productivity if your employees can\u2019t access them. Many organizations have switched to remote or hybrid-remote work, making resource access a challenge. Lack of easy access, or access that is cumbersome or confusing, slows efficiency and negatively impacts the user experience. <\/p>\n\n\n\n
Question 11<\/strong> (for hybrid-remote organizations): Is it easier for you to access the tools you need to get work done when working remotely or in the office?<\/h3>\n\n\n\nSuggested multiple choice answers:<\/p>\n\n\n\n
\n- Remotely<\/li>\n\n\n\n
- In the office<\/li>\n\n\n\n
- They are equally accessible<\/li>\n<\/ul>\n\n\n\n
Ideally, employees should feel that access to resources is equally easy when in the office or working remotely. Employees aren\u2019t generally interested in the back-end processes that power their experience; they simply want to be able to log on and work, regardless of where they are. Consistency and simplicity are key factors in delivering on those expectations.<\/p>\n\n\n\n
Question 12: <\/strong>How easy is it for you to access everything you need to complete your work?<\/h3>\n\n\n\nSuggested multiple choice answers:<\/p>\n\n\n\n
\n- Very easy<\/li>\n\n\n\n
- Somewhat easy<\/li>\n\n\n\n
- Somewhat difficult<\/li>\n\n\n\n
- Very difficult<\/li>\n<\/ul>\n\n\n\n
Follow-up question: Which resources are difficult to access? <\/h4>\n\n\n\nQuestion 13:<\/strong> Do you feel overwhelmed by the number of login credentials or accounts you need to keep track of?<\/h3>\n\n\n\nAs we digitize processes and multiply the number of cloud-based tools in our stack, we ask employees to track more and more credentials. This is a detriment to both the business and the employee: it tends to frustrate employees and create password fatigue<\/a>, which creates security vulnerabilities for the business. <\/p>\n\n\n\nSingle sign-on (SSO)<\/a> prevents this by facilitating secure authorization to all an employee\u2019s apps using just one set of secure credentials. With SSO, employees only have to remember one set of credentials, and businesses actually enjoy a more <\/em>secure login process via secure protocols like SAML instead of just the simple (and vulnerable) username and password. <\/p>\n\n\n\n
<\/figure>\n\n\n\nQuestion 1:<\/strong> Which tools do you use most frequently? <\/h3>\n\n\n\nStart by gauging what is<\/em> working. This question will pinpoint which tools serve a viable need. Even if you end up changing your tech stack this year, make sure you keep the tools frequently mentioned in these responses or replace them with tools that can serve the same needs.<\/p>\n\n\n\nQuestion 2:<\/strong> Do you use non-company tools to accomplish your work? Which tools, and what do you use them for?<\/h3>\n\n\n\nThis question will help you identify gaps in your tools or their functionality. Employees may use non-company tools either because the company hasn\u2019t provided a tool or because the provided tool is insufficient. <\/p>\n\n\n\n
When employees use their own tools, they introduce vulnerabilities into the organization, from putting company information into non-approved software to granting third-party tools direct access to company infrastructure. Understanding why employees deem a tool insufficient can help you assess solutions that prevent employees from needing to source unapproved tools to complete their work. Consider including this follow-up question to determine the gaps in your stack\u2019s functionality:<\/p>\n\n\n\n
Follow-up: Why do you use the tools you listed instead of the company-provided ones? <\/h4>\n\n\n\n
Suggested multiple choice answers:<\/p>\n\n\n\n
\n- We don\u2019t have one for this purpose.<\/li>\n\n\n\n
- It\u2019s frustrating\/hard to use. <\/li>\n\n\n\n
- I don\u2019t know how to use it. <\/li>\n\n\n\n
- It can\u2019t do everything I need it to. <\/li>\n\n\n\n
- It\u2019s not compatible with other tools or devices. <\/li>\n\n\n\n
- I liked the old one better. <\/strong>(Include this option if you recently switched tools).<\/strong> <\/li>\n\n\n\n
- Other. (Give employees the chance to explain their other reasons for using a different tool.) <\/li>\n<\/ul>\n\n\n\n
If responses indicate that your company\u2019s tool suite lacks critical functionality, consider looking for ways to consolidate tools rather than investing in a new one just to fill the identified gap. For example, if your company needs a more user-friendly MFA solution, consider one that can accomplish other things as well \u2014 JumpCloud\u00ae<\/sup><\/a>, for example, offers multi-factor authentication (MFA)<\/a> as part of its entire cloud directory platform, which includes identity and access management (IAM), mobile device management (MDM), and single sign-on (SSO). Combining tools can be an effective cost-savings tactic. <\/p>\n\n\n\nFor responses that indicate a lack of buy-in or understanding of how to use the tool, consider hosting training or making educational resources available. Many vendors provide user-oriented educational resources for their tools \u2014 pulling a few of these and circulating them to coworkers can be a quick and easy first step. <\/p>\n\n\n\n
Question 3:<\/strong> Are there tools we offer that you don\u2019t use? Which ones?<\/h3>\n\n\n\nIdentifying areas where you could reduce licenses or shed tools altogether can generate significant cost-saving wins and offset the costs of new technology you may need to invest in.<\/p>\n\n\n\n
Question 4:<\/strong> Which tools do you dread or avoid using?<\/h3>\n\n\n\nThis question helps identify tools that slow productivity or generate frustration, potentially leading to shadow IT<\/a>. If you notice commonly named tools in responses, try offering more training or educational resources on usage, as a first step. If this doesn\u2019t improve usage or satisfaction, investing in a different tool may cost less than the security vulnerabilities that workarounds create. <\/p>\n\n\n\nQuestions Around Employee Devices<\/strong><\/h2>\n\n\n\n<\/figure>\n\n\n\nQuestion 5:<\/strong> Are you comfortable with your operating system?<\/h3>\n\n\n\nIt\u2019s no secret that people have strong feelings about their OS preference, and imposing Windows on a lifelong Mac user (or vice versa) can seriously slow their productivity. Workplaces are becoming more heterogeneous in device types, and newer infrastructure and device management tools are rising to the challenge of supporting them. JumpCloud, for example, is an OS-agnostic<\/a> directory platform; that flexibility extends to its MDM, MFA, and other capabilities.<\/p>\n\n\n\nQuestion 6<\/strong> (for organizations using company-issued devices): Do you use your personal device for any work tasks? For which applications or tasks do you use your personal device? <\/h3>\n\n\n\nIf employees are using their personal devices for a variety of tasks, this could indicate a need for a bring your own device (BYOD) policy or MDM tool. Completing company tasks on a non-compliant personal device places your company data at risk. <\/p>\n\n\n\n
Note that a BYOD policy<\/a> shouldn\u2019t be considered without also addressing employee privacy. If you\u2019re not ready to implement a mandatory, full-fledged, BYOD program, consider using a minimally intrusive MDM tool that allows users to opt in. This way, users can choose to make use of the BYOD program if they like using email, messaging, or other work apps on their phone without fear of endangering company data or the company violating their privacy.<\/p>\n\n\n\nQuestion 7: <\/strong>Are you experiencing problems with any of the following on your device?<\/h3>\n\n\n\nSuggested multiple choice answers:<\/p>\n\n\n\n
\n- Storage space<\/li>\n\n\n\n
- Speed<\/li>\n\n\n\n
- Functionality<\/li>\n\n\n\n
- Hardware problems (e.g., broken keyboard or port)<\/li>\n\n\n\n
- Other<\/li>\n<\/ul>\n\n\n\n
Always ensure devices are functioning optimally to prevent slowdowns or complications from old or faulty machines. If there\u2019s room in the budget, consider following up with a question about additional hardware they might need. Low-cost items like adapters can go a long way toward powering productivity.<\/p>\n\n\n\n
Questions Around Technical Issues <\/strong><\/h2>\n\n\n\n<\/figure>\n\n\n\nQuestion 8: <\/strong>Do you know how and where to report technical issues?<\/h3>\n\n\n\nQuestion 9:<\/strong> Do you know where to go for technical or security questions?<\/h3>\n\n\n\nQuestion 10:<\/strong> Have you noticed any recurring technical issues that affect your ability to complete your work?<\/h3>\n\n\n\nEfficient issue reporting reduces the time needed to rectify problems and prevents shadow IT and security blind spots. Ensure employees understand and follow issue reporting protocols to bolster your organization\u2019s overall productivity, efficiency, and security. <\/p>\n\n\n\n
If responses indicate that technical reporting processes aren\u2019t clear, try starting off 2022 with a quick refresher course on recognizing and addressing IT problems.<\/p>\n\n\n\n
Questions Around Resource Access<\/strong><\/h2>\n\n\n\n<\/figure>\n\n\n\nEven the best tools in the world can\u2019t power productivity if your employees can\u2019t access them. Many organizations have switched to remote or hybrid-remote work, making resource access a challenge. Lack of easy access, or access that is cumbersome or confusing, slows efficiency and negatively impacts the user experience. <\/p>\n\n\n\n
Question 11<\/strong> (for hybrid-remote organizations): Is it easier for you to access the tools you need to get work done when working remotely or in the office?<\/h3>\n\n\n\nSuggested multiple choice answers:<\/p>\n\n\n\n
\n- Remotely<\/li>\n\n\n\n
- In the office<\/li>\n\n\n\n
- They are equally accessible<\/li>\n<\/ul>\n\n\n\n
Ideally, employees should feel that access to resources is equally easy when in the office or working remotely. Employees aren\u2019t generally interested in the back-end processes that power their experience; they simply want to be able to log on and work, regardless of where they are. Consistency and simplicity are key factors in delivering on those expectations.<\/p>\n\n\n\n
Question 12: <\/strong>How easy is it for you to access everything you need to complete your work?<\/h3>\n\n\n\nSuggested multiple choice answers:<\/p>\n\n\n\n
\n- Very easy<\/li>\n\n\n\n
- Somewhat easy<\/li>\n\n\n\n
- Somewhat difficult<\/li>\n\n\n\n
- Very difficult<\/li>\n<\/ul>\n\n\n\n
Follow-up question: Which resources are difficult to access? <\/h4>\n\n\n\nQuestion 13:<\/strong> Do you feel overwhelmed by the number of login credentials or accounts you need to keep track of?<\/h3>\n\n\n\nAs we digitize processes and multiply the number of cloud-based tools in our stack, we ask employees to track more and more credentials. This is a detriment to both the business and the employee: it tends to frustrate employees and create password fatigue<\/a>, which creates security vulnerabilities for the business. <\/p>\n\n\n\nSingle sign-on (SSO)<\/a> prevents this by facilitating secure authorization to all an employee\u2019s apps using just one set of secure credentials. With SSO, employees only have to remember one set of credentials, and businesses actually enjoy a more <\/em>secure login process via secure protocols like SAML instead of just the simple (and vulnerable) username and password. <\/p>\n\n\n\n
Question 2:<\/strong> Do you use non-company tools to accomplish your work? Which tools, and what do you use them for?<\/h3>\n\n\n\nThis question will help you identify gaps in your tools or their functionality. Employees may use non-company tools either because the company hasn\u2019t provided a tool or because the provided tool is insufficient. <\/p>\n\n\n\n
When employees use their own tools, they introduce vulnerabilities into the organization, from putting company information into non-approved software to granting third-party tools direct access to company infrastructure. Understanding why employees deem a tool insufficient can help you assess solutions that prevent employees from needing to source unapproved tools to complete their work. Consider including this follow-up question to determine the gaps in your stack\u2019s functionality:<\/p>\n\n\n\n
Follow-up: Why do you use the tools you listed instead of the company-provided ones? <\/h4>\n\n\n\n
Suggested multiple choice answers:<\/p>\n\n\n\n
\n- We don\u2019t have one for this purpose.<\/li>\n\n\n\n
- It\u2019s frustrating\/hard to use. <\/li>\n\n\n\n
- I don\u2019t know how to use it. <\/li>\n\n\n\n
- It can\u2019t do everything I need it to. <\/li>\n\n\n\n
- It\u2019s not compatible with other tools or devices. <\/li>\n\n\n\n
- I liked the old one better. <\/strong>(Include this option if you recently switched tools).<\/strong> <\/li>\n\n\n\n
- Other. (Give employees the chance to explain their other reasons for using a different tool.) <\/li>\n<\/ul>\n\n\n\n
If responses indicate that your company\u2019s tool suite lacks critical functionality, consider looking for ways to consolidate tools rather than investing in a new one just to fill the identified gap. For example, if your company needs a more user-friendly MFA solution, consider one that can accomplish other things as well \u2014 JumpCloud\u00ae<\/sup><\/a>, for example, offers multi-factor authentication (MFA)<\/a> as part of its entire cloud directory platform, which includes identity and access management (IAM), mobile device management (MDM), and single sign-on (SSO). Combining tools can be an effective cost-savings tactic. <\/p>\n\n\n\nFor responses that indicate a lack of buy-in or understanding of how to use the tool, consider hosting training or making educational resources available. Many vendors provide user-oriented educational resources for their tools \u2014 pulling a few of these and circulating them to coworkers can be a quick and easy first step. <\/p>\n\n\n\n
Question 3:<\/strong> Are there tools we offer that you don\u2019t use? Which ones?<\/h3>\n\n\n\nIdentifying areas where you could reduce licenses or shed tools altogether can generate significant cost-saving wins and offset the costs of new technology you may need to invest in.<\/p>\n\n\n\n
Question 4:<\/strong> Which tools do you dread or avoid using?<\/h3>\n\n\n\nThis question helps identify tools that slow productivity or generate frustration, potentially leading to shadow IT<\/a>. If you notice commonly named tools in responses, try offering more training or educational resources on usage, as a first step. If this doesn\u2019t improve usage or satisfaction, investing in a different tool may cost less than the security vulnerabilities that workarounds create. <\/p>\n\n\n\nQuestions Around Employee Devices<\/strong><\/h2>\n\n\n\n<\/figure>\n\n\n\nQuestion 5:<\/strong> Are you comfortable with your operating system?<\/h3>\n\n\n\nIt\u2019s no secret that people have strong feelings about their OS preference, and imposing Windows on a lifelong Mac user (or vice versa) can seriously slow their productivity. Workplaces are becoming more heterogeneous in device types, and newer infrastructure and device management tools are rising to the challenge of supporting them. JumpCloud, for example, is an OS-agnostic<\/a> directory platform; that flexibility extends to its MDM, MFA, and other capabilities.<\/p>\n\n\n\nQuestion 6<\/strong> (for organizations using company-issued devices): Do you use your personal device for any work tasks? For which applications or tasks do you use your personal device? <\/h3>\n\n\n\nIf employees are using their personal devices for a variety of tasks, this could indicate a need for a bring your own device (BYOD) policy or MDM tool. Completing company tasks on a non-compliant personal device places your company data at risk. <\/p>\n\n\n\n
Note that a BYOD policy<\/a> shouldn\u2019t be considered without also addressing employee privacy. If you\u2019re not ready to implement a mandatory, full-fledged, BYOD program, consider using a minimally intrusive MDM tool that allows users to opt in. This way, users can choose to make use of the BYOD program if they like using email, messaging, or other work apps on their phone without fear of endangering company data or the company violating their privacy.<\/p>\n\n\n\nQuestion 7: <\/strong>Are you experiencing problems with any of the following on your device?<\/h3>\n\n\n\nSuggested multiple choice answers:<\/p>\n\n\n\n
\n- Storage space<\/li>\n\n\n\n
- Speed<\/li>\n\n\n\n
- Functionality<\/li>\n\n\n\n
- Hardware problems (e.g., broken keyboard or port)<\/li>\n\n\n\n
- Other<\/li>\n<\/ul>\n\n\n\n
Always ensure devices are functioning optimally to prevent slowdowns or complications from old or faulty machines. If there\u2019s room in the budget, consider following up with a question about additional hardware they might need. Low-cost items like adapters can go a long way toward powering productivity.<\/p>\n\n\n\n
Questions Around Technical Issues <\/strong><\/h2>\n\n\n\n<\/figure>\n\n\n\nQuestion 8: <\/strong>Do you know how and where to report technical issues?<\/h3>\n\n\n\nQuestion 9:<\/strong> Do you know where to go for technical or security questions?<\/h3>\n\n\n\nQuestion 10:<\/strong> Have you noticed any recurring technical issues that affect your ability to complete your work?<\/h3>\n\n\n\nEfficient issue reporting reduces the time needed to rectify problems and prevents shadow IT and security blind spots. Ensure employees understand and follow issue reporting protocols to bolster your organization\u2019s overall productivity, efficiency, and security. <\/p>\n\n\n\n
If responses indicate that technical reporting processes aren\u2019t clear, try starting off 2022 with a quick refresher course on recognizing and addressing IT problems.<\/p>\n\n\n\n
Questions Around Resource Access<\/strong><\/h2>\n\n\n\n<\/figure>\n\n\n\nEven the best tools in the world can\u2019t power productivity if your employees can\u2019t access them. Many organizations have switched to remote or hybrid-remote work, making resource access a challenge. Lack of easy access, or access that is cumbersome or confusing, slows efficiency and negatively impacts the user experience. <\/p>\n\n\n\n
Question 11<\/strong> (for hybrid-remote organizations): Is it easier for you to access the tools you need to get work done when working remotely or in the office?<\/h3>\n\n\n\nSuggested multiple choice answers:<\/p>\n\n\n\n
\n- Remotely<\/li>\n\n\n\n
- In the office<\/li>\n\n\n\n
- They are equally accessible<\/li>\n<\/ul>\n\n\n\n
Ideally, employees should feel that access to resources is equally easy when in the office or working remotely. Employees aren\u2019t generally interested in the back-end processes that power their experience; they simply want to be able to log on and work, regardless of where they are. Consistency and simplicity are key factors in delivering on those expectations.<\/p>\n\n\n\n
Question 12: <\/strong>How easy is it for you to access everything you need to complete your work?<\/h3>\n\n\n\nSuggested multiple choice answers:<\/p>\n\n\n\n
\n- Very easy<\/li>\n\n\n\n
- Somewhat easy<\/li>\n\n\n\n
- Somewhat difficult<\/li>\n\n\n\n
- Very difficult<\/li>\n<\/ul>\n\n\n\n
Follow-up question: Which resources are difficult to access? <\/h4>\n\n\n\nQuestion 13:<\/strong> Do you feel overwhelmed by the number of login credentials or accounts you need to keep track of?<\/h3>\n\n\n\nAs we digitize processes and multiply the number of cloud-based tools in our stack, we ask employees to track more and more credentials. This is a detriment to both the business and the employee: it tends to frustrate employees and create password fatigue<\/a>, which creates security vulnerabilities for the business. <\/p>\n\n\n\nSingle sign-on (SSO)<\/a> prevents this by facilitating secure authorization to all an employee\u2019s apps using just one set of secure credentials. With SSO, employees only have to remember one set of credentials, and businesses actually enjoy a more <\/em>secure login process via secure protocols like SAML instead of just the simple (and vulnerable) username and password. <\/p>\n\n\n\n
If responses indicate that your company\u2019s tool suite lacks critical functionality, consider looking for ways to consolidate tools rather than investing in a new one just to fill the identified gap. For example, if your company needs a more user-friendly MFA solution, consider one that can accomplish other things as well \u2014 JumpCloud\u00ae<\/sup><\/a>, for example, offers multi-factor authentication (MFA)<\/a> as part of its entire cloud directory platform, which includes identity and access management (IAM), mobile device management (MDM), and single sign-on (SSO). Combining tools can be an effective cost-savings tactic. <\/p>\n\n\n\n For responses that indicate a lack of buy-in or understanding of how to use the tool, consider hosting training or making educational resources available. Many vendors provide user-oriented educational resources for their tools \u2014 pulling a few of these and circulating them to coworkers can be a quick and easy first step. <\/p>\n\n\n\n Identifying areas where you could reduce licenses or shed tools altogether can generate significant cost-saving wins and offset the costs of new technology you may need to invest in.<\/p>\n\n\n\n This question helps identify tools that slow productivity or generate frustration, potentially leading to shadow IT<\/a>. If you notice commonly named tools in responses, try offering more training or educational resources on usage, as a first step. If this doesn\u2019t improve usage or satisfaction, investing in a different tool may cost less than the security vulnerabilities that workarounds create. <\/p>\n\n\n\n It\u2019s no secret that people have strong feelings about their OS preference, and imposing Windows on a lifelong Mac user (or vice versa) can seriously slow their productivity. Workplaces are becoming more heterogeneous in device types, and newer infrastructure and device management tools are rising to the challenge of supporting them. JumpCloud, for example, is an OS-agnostic<\/a> directory platform; that flexibility extends to its MDM, MFA, and other capabilities.<\/p>\n\n\n\n If employees are using their personal devices for a variety of tasks, this could indicate a need for a bring your own device (BYOD) policy or MDM tool. Completing company tasks on a non-compliant personal device places your company data at risk. <\/p>\n\n\n\n Note that a BYOD policy<\/a> shouldn\u2019t be considered without also addressing employee privacy. If you\u2019re not ready to implement a mandatory, full-fledged, BYOD program, consider using a minimally intrusive MDM tool that allows users to opt in. This way, users can choose to make use of the BYOD program if they like using email, messaging, or other work apps on their phone without fear of endangering company data or the company violating their privacy.<\/p>\n\n\n\n Suggested multiple choice answers:<\/p>\n\n\n\n Always ensure devices are functioning optimally to prevent slowdowns or complications from old or faulty machines. If there\u2019s room in the budget, consider following up with a question about additional hardware they might need. Low-cost items like adapters can go a long way toward powering productivity.<\/p>\n\n\n\n Efficient issue reporting reduces the time needed to rectify problems and prevents shadow IT and security blind spots. Ensure employees understand and follow issue reporting protocols to bolster your organization\u2019s overall productivity, efficiency, and security. <\/p>\n\n\n\n If responses indicate that technical reporting processes aren\u2019t clear, try starting off 2022 with a quick refresher course on recognizing and addressing IT problems.<\/p>\n\n\n\n Even the best tools in the world can\u2019t power productivity if your employees can\u2019t access them. Many organizations have switched to remote or hybrid-remote work, making resource access a challenge. Lack of easy access, or access that is cumbersome or confusing, slows efficiency and negatively impacts the user experience. <\/p>\n\n\n\n Suggested multiple choice answers:<\/p>\n\n\n\n Ideally, employees should feel that access to resources is equally easy when in the office or working remotely. Employees aren\u2019t generally interested in the back-end processes that power their experience; they simply want to be able to log on and work, regardless of where they are. Consistency and simplicity are key factors in delivering on those expectations.<\/p>\n\n\n\n Suggested multiple choice answers:<\/p>\n\n\n\n As we digitize processes and multiply the number of cloud-based tools in our stack, we ask employees to track more and more credentials. This is a detriment to both the business and the employee: it tends to frustrate employees and create password fatigue<\/a>, which creates security vulnerabilities for the business. <\/p>\n\n\n\n Single sign-on (SSO)<\/a> prevents this by facilitating secure authorization to all an employee\u2019s apps using just one set of secure credentials. With SSO, employees only have to remember one set of credentials, and businesses actually enjoy a more <\/em>secure login process via secure protocols like SAML instead of just the simple (and vulnerable) username and password. <\/p>\n\n\n\nQuestion 3:<\/strong> Are there tools we offer that you don\u2019t use? Which ones?<\/h3>\n\n\n\n
Question 4:<\/strong> Which tools do you dread or avoid using?<\/h3>\n\n\n\n
Questions Around Employee Devices<\/strong><\/h2>\n\n\n\n
<\/figure>\n\n\n\nQuestion 5:<\/strong> Are you comfortable with your operating system?<\/h3>\n\n\n\n
Question 6<\/strong> (for organizations using company-issued devices): Do you use your personal device for any work tasks? For which applications or tasks do you use your personal device? <\/h3>\n\n\n\n
Question 7: <\/strong>Are you experiencing problems with any of the following on your device?<\/h3>\n\n\n\n
\n
Questions Around Technical Issues <\/strong><\/h2>\n\n\n\n
<\/figure>\n\n\n\nQuestion 8: <\/strong>Do you know how and where to report technical issues?<\/h3>\n\n\n\n
Question 9:<\/strong> Do you know where to go for technical or security questions?<\/h3>\n\n\n\n
Question 10:<\/strong> Have you noticed any recurring technical issues that affect your ability to complete your work?<\/h3>\n\n\n\n
Questions Around Resource Access<\/strong><\/h2>\n\n\n\n
<\/figure>\n\n\n\nQuestion 11<\/strong> (for hybrid-remote organizations): Is it easier for you to access the tools you need to get work done when working remotely or in the office?<\/h3>\n\n\n\n
\n
Question 12: <\/strong>How easy is it for you to access everything you need to complete your work?<\/h3>\n\n\n\n
\n
Follow-up question: Which resources are difficult to access? <\/h4>\n\n\n\n
Question 13:<\/strong> Do you feel overwhelmed by the number of login credentials or accounts you need to keep track of?<\/h3>\n\n\n\n
![\"Laptop](\"https:\/\/jumpcloud.com\/\/wp-content\/uploads\/2021\/12\/chris-montgomery-smgTvepind4-unsplash-1024x768.jpg\")
<\/figure>\n\n\n\n