We’re in the process of training for a new system. Learning a new system is good. Change is good. I accept there are going to be glitches and I accept that it’s going to take a while to wrap my head around the new system.
What I don’t accept is that at the (first and only) training session, we - the lowly minions – were informed that we’re to go live with this new system tomorrow. If not today.
This is the first time most of us have even clapped eyes on the software. Never mind used it. And now we must master it by when?
Generally, a new launch or upgrade is phased in. A few hours of training, a few days if not weeks of testing, then a few more tests before going live.
What’s the rush in this case…? Our managers have just realised that the launch party is tomorrow. Crap. Well we better have something to show at the launch, hey?
So now our managers, who have only recently discovered their belly buttons, are scurrying around like ants under a microscope because – surprise! – time carries on in spite of their best attempts to ignore it.
My list of priorities when introducing a new system:
- Contemplate feasibility and logistics of new system
- Design new system
- Train employees
- Test new system
- Organise launch party
- Go live
Their list of priorities, as far as I can tell:
- Organise a launch party
- Design the new system
- Fret about unseen incompatibilities
- Go live anyway
- Oh ja... train employees
Oh, and by the way, the lowly minions are not invited to the launch party proper. We get pizza in our office – possibly placed just out of reach from our ankle shackles. They all need a lesson in efficiency from Randburg bloody Home Affairs. I am not paid enough for this shit.
Then I went off in a blind rage and played a hockey match. That we lost. I also managed to break a team mate’s finger – not directly, but she was kinda in the way of a ball that I cleared… at hip height. Lose cannon. Not sure if the finger’s broken, but her three middle fingers sure were a pretty shade of blue.
I’m going to hell.