What should I consider when someone leaves the team?

0
4
Asked By TechWiz101 On

Hi everyone! I'm looking to create a comprehensive offboarding checklist for when team members leave the company. Sure, I've got the basics down like revoking access and onboarding a replacement. But I'm curious about the less obvious aspects, particularly around tacit knowledge—like understanding if an alert means something or if it's just background noise. What else should I keep in mind to ensure a smooth transition?

4 Answers

Answered By CloudQueen88 On

Also, in a Microsoft environment, be prepared for issues surrounding Power Automate. Any dependencies on that can lead to problems after someone departs. Just a heads-up!

Answered By OffboardingHero On

Just a side note—stuff that was purchased using a personal card can cause chaos. If someone had their credit card tied to services like AWS or Google, you might be in for a surprise when payments are due after their departure!

Answered By DevGuy42 On

Don't forget to check on any API keys. Often, people set up integrations without making it clear that they're tied to their own accounts. When they leave, those integrations can break unexpectedly, even with decent documentation.

Answered By DataDude_89 On

If a key business process relies on a user's domain account instead of a service account, it can lead to major hiccups. Trust me, I've seen this go wrong before and it causes a lot of headaches as people scramble to figure out what happened.

SystemsGal -

Yeah, you’d be surprised how many teams have accidentally trapped themselves in that situation. It's a real mess when the wrong account is tied to something crucial!

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.