What to Have in Place Before a Team Member Leaves

Posted by Bill Onion

May 8, 2017 | 10:30 AM

Share this blog on:     

team member leaving.pngIt can be a challenging time when a key team member leaves. Whether it’s an IBM i lead or IT Director, many organizations are left scrambling at an unexpected departure. While we’ve discussed what can be done in the aftermath in order to keep things moving, there are a few things you should have prepared at all times that could make a future transition easier.

Create a Succession Plan

One thing we encourage all of our customers to have in place at all times is an updated Succession Plan. If your IT Director put in their two weeks’ notice tomorrow, do you know who would fill that role? Having a documented plan for who moves to what position in the event of someone leaving will remove a lot of the initial panic when the time comes.

Have an Established Ticketing System

Not only will this help in the event that a staff member leaves, but it will make every day processes easier. Establishing a ticketing system to use for all projects will keep everyone in tune with the overall progress of a project, whether they are directly involved or not. If a key team member leaves, the rest of the team will be able to reference the project tickets to keep things on track.

Encourage Cross Training

We get it; everyone is busy and they don’t have time to take on additional tasks that don’t even directly affect their responsibilities. But cross-training in different departments of your organization, or even just on other processes within the same department, can be a huge help when someone leaves. You’ll have a bigger pool of resources to pull from to pick up the slack until a full-time replacement is found.

Additionally, this helps team members get a better idea of how other aspects of the organization work, potentially leading to more understanding and tolerance for business processes from start to finish.

Credentials Process

One of the tricky things that we’ve seen happen when someone leaves is the discovery that the person who left was the only admin of a program, or they were the only ones with the appropriate credentials. Trying to get that information after someone has left can be time consuming, not to mention awkward. If your organization has a credential documentation process, that information is available to those who need it.

A team member’s sudden departure doesn’t have to be a crisis. It’s unfortunate, to be sure, but it doesn’t have to be the end of the world. Having these processes in place before someone leaves will make their exit much easier on the rest of the team.

Is your team in panic mode because someone left and you weren't prepared? Contact our team to pick up the slack. 

Need More Information? Contact Us.

Topics: Technology

About Bill Onion

Bill Onion is Managing Director of Briteskies, where he has a distinguished track record helping B2B and B2C companies integrate e-commerce solutions. His expertise in the eCommerce world includes Magento and WebSphere Commerce software systems and his enterprise software experience is focused on the Oracle/JD Edwards platform. Bill has many years of consulting experience in various industries, including distribution, warehousing, retail and manufacturing. Bill is an avid runner, is very involved with Scouts, and cannot help but to root for the Browns every fall.

Find me on:

Search

Subscribe to Email Updates

magento-platform-checklist
New Call-to-Action

Contact Us

B2B-2.0

Recent Posts