Is it fear of upsetting the status quo or “rocking the boat”? Too often, I see critical issues being overlooked during client onboarding, such as:
โข ๐ข๐น๐ฑ ๐๐๐ฒ๐ฟ๐ lingering in M365, left active long after they’ve left the companyโsometimes account which existed well before the IT firm took over.
โข ๐ข๐๐๐ฑ๐ฎ๐๐ฒ๐ฑ ๐ฐ๐ผ๐บ๐ฝ๐๐๐ฒ๐ฟ๐ remaining in use, posing security risks and inefficiencies.
โข ๐จ๐ป๐๐ฟ๐ฎ๐ฐ๐ธ๐ฒ๐ฑ ๐ฑ๐ฒ๐๐ถ๐ฐ๐ฒ๐ purchased without IT’s knowledge, never making it into the Mobile Device Management (MDM) system.
โข ๐๐ป๐ฐ๐ผ๐ป๐๐ถ๐๐๐ฒ๐ป๐ ๐๐ฒ๐ฐ๐๐ฟ๐ถ๐๐ ๐ฝ๐ผ๐น๐ถ๐ฐ๐ถ๐ฒ๐, where some users have MFA enforced while others do not, leaving gaps in protection.
โข ๐๐ผ๐บ๐ฝ๐น๐ถ๐ฎ๐ป๐ฐ๐ฒ ๐ผ๐ฟ ๐ฐ๐ผ๐ป๐ณ๐ถ๐ด๐๐ฟ๐ฎ๐๐ถ๐ผ๐ป ๐ฝ๐ฟ๐ผ๐ณ๐ถ๐น๐ฒ๐ from the previous IT firm not reviewed, potentially leaving outdated or insecure settings in place.
โข ๐ฃ๐ฟ๐ฒ๐๐ถ๐ผ๐๐ ๐๐ง ๐ฎ๐ฝ๐ฝ๐น๐ถ๐ฐ๐ฎ๐๐ถ๐ผ๐ป๐ not removed from the environment, creating unnecessary vulnerabilities and clutter.
These scenarios are disheartening, and these only scratch the surface. ๐
๐๐ฑ๐๐ถ๐ฐ๐ฒ ๐ณ๐ผ๐ฟ ๐๐ง ๐๐ถ๐ฟ๐บ๐:
Your clients have chosen you for your expertiseโnow’s the time to show it. Step up, communicate clearly, and implement a structured plan to align the clientโs environment with your standard processes.
Remember:
โข Your client won’t leave you for taking charge and improving their infrastructure.
โข If they do, they likely weren’t the right fit and could have led to bigger challenges down the road.
Stand firm in your role as experts and make the tough calls when needed. Your proactive approach will pay off in the long run.
๐ช๐ต๐ฎ๐ ๐ฑ๐ผ ๐๐ผ๐ ๐๐ต๐ถ๐ป๐ธ?
Why do you believe IT teams sometimes hesitate to step up during client onboarding? What are some of the other critical areas that IT might overlook in these transitions? What conversations around roles and responsibilities should be happening during this process? Iโd love to hear your thoughts and experiences!