There is this process that a leaving coworker wrote using (I feel) outdated software. The issue is anytime there is an error I have to consult with said coworker to get it fixed because no one else in my department knows work this software either. So I want to replace his process before he leaves. Should I let him know that I will replace his process and possibly offending him? or just replace it without telling him since he is leaving anyways.

  • 4
    That decision (of telling him) is yours. What do you want to achieve here? What's your goal beside asking for opinions (which would make all answers equal)?
    – OldPadawan
    Apr 14, 2023 at 5:05
  • Why the downvotes?
    – morsor
    Apr 14, 2023 at 6:38
  • 2
    @morsor : from the tour = don't ask questions that ask for "personal advice on what to do". Seems pretty clear to me (shrug)
    – OldPadawan
    Apr 14, 2023 at 8:04
  • @OldPadawan: The situation is quite general, though. Would editing the question in a more general direction make it acceptable?
    – morsor
    Apr 14, 2023 at 8:11
  • 1
    maybe asking about a good way to switch persons/replace process in a professional way and without bruising egos? Something around this idea would seem much better to me.
    – OldPadawan
    Apr 14, 2023 at 9:01

2 Answers 2


There is nothing kind in telling that the first thing you'll do when he leaves, is throwing his work in the trash. Unless you have a personal need to make a point or be unkind, I would suggest you don't do it like that.

I would use the situation to get every piece of information out of this persons head and into the specification for the replacement system. "Outdated, I feel" is very vague - there is a vast difference between "This MS-DOS based software only runs on 32-bit Windows 10 machines, so updating now is due dilligence" and "I don't like this software because Outlook365 has something much nicer". It might turn out that the price for updating instead of just learning the existing software is much higher than you expect.

If you sell this right, this can be highly beneficial for both the employee, the company and yourself.


If you change the wording to 'updating' rather than 'replacing', you signal the process is necessary - and might have an easier time extracting valuable information from the soon-to-depart colleague. He probably knows that the process is very much tied to him so he will probably expect some hand-over at the very least.

A more constructive move could be involving him in creating 'Process v 2.0' with requirements like:

  • Process must be performed by multiple people
  • Update technological stack (if necessary)
  • New business enhancements

If he had to create the process from scratch today, it's quite likely that he would make different choices. Find out what they are.

The most important point is to avoid stepping on his ego - and that can probably be accomplished by demonstrating that his process and opinions are valued.

  • Regardless you should plan to learn the current process so you can write a new process if you will not be responsible for the result of the current process (or new process) before the indivdual leaves.
    – Donald
    Apr 14, 2023 at 15:24

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .