Mary:
First of all, if they’re replacing you with some consultant, they’re
idiots.
My inclination would be to approach it from the top down. So,
- A list of all of the types of hardware to be supported.
- A list of all of the types and versions of software to be
supported.
- A list of any programming languages that need to be known and to
what extent - beginner, intermediate, advanced, expert.
- A list of known upgrades, migrations, etc. that have already been
approved and are in the planning stages.
- The experience level required to support each of the above.
- A weighting for each of the above showing it’s importance for
performance of the work involved. Things that absolutely need to be
known on day one, down to things that can be picked up along the way.
So, pretty much what you’d list if you were going to be hiring
someone for the position. Whether it’s a hire position or an
outsourcing, it makes no difference. The work is the same.
From this you can make a checklist for vendors to fill out, so they
can tick off what they know how to do, and give a rating of 1-10 of
their skill level at it.
The vetting process itself should be not much more than checking the
list of skills of vendor applicants to see how well their experience
fits in with all of the above, the interviews of qualified vendors,
and then the checking of the information on their checklist with
their previous employers and/or customers.
No matter how good a job you do on this, it won’t matter. Your
company will hire who they want to hire, so I wouldn’t put too much
time and effort into it.
I find it in appallingly BAD taste when a company decides to replace
someone, probably thinking they’ll save money somehow, pretty much
kicking out a valued employee, and expects that employee to happily
find their replacement and train them. It’s reasonable if the
employee is the one initiating the departure. It’s unreasonable if
the employer is, and it’s actually a pretty dangerous thing for an
employer to do, because the employee will often (you would never do
this, I know, but some people would) sabotage something.
If they can’t figure out who the right vendor is based on the types
of hardware and software and systems the company has, and the proven
experience of a given vendor, then there’s no hope for your current
employer, anyway.
If this all happens, and they come back to you at some point with hat
in hand asking you to come back, you should double your salary
requirements, and make sure you get all of the best benefits the
company has to offer, including an extra week or so of vacation,
before accepting your old position back. Make sure it’s put in
writing.
I’m so sorry to hear this happened to you. They may never admit it,
but there will be a day when they’ll regret this move. And you will
come out ahead. You’ve been overworked and underpaid by them all
along. It may take awhile, but there’s something better for you
ahead. Be patient, and don’t settle for less than you deserve.
–
Susan
Novell Community Chat Moderator
http://forums.novell.com/faq.php?faq=novfor#faq_rules
http://www.ncci.org NCCIrregulars Web Site
https://www.facebook.com/groups/NCCIrregulars
Please read the following before posting in here:
http://preview.tinyurl.com/27zopdy