The system gets adapted, right?
You keep the bits you like, ditch the parts that cause problems, and circumnavigate the inevitable glitches along the way.
Oh, no. Not with our Project Manager. She wants everything up and running 'as it should be', going so far as to bury news of problems so they're never properly dealt with. She has repeatedly tried to force us into using parts of the system that are broken and increase not only our workload, but our turnaround times.
Thank God for a department Manager who (a) gives a damn about staff and their workloads and (b) is enough of a control freak to know what works, what doesn't, and what we do at every stage of our process. Hell, she wrote the process.
But Project Manager kicks up a storm because not using the system 'as it should be' could be considered a failure on her part (and burying the bad news couldn't?). This gets passed on to my MD, who then passes it down to my Manager... Who then kicks up a whole new storm in retaliation... and successfully proves our case, winning a significant victory in the name of sanity. "If it ain't broke, don't fix it."
Because it's not about the system. It's about who thinks what about whom, and other such dreary office politics. The retaliation wasn't about the system, it was about being forced into using something that we have already shown is of no benefit, by someone who has shown not the least bit of concern about the workflow.
Watch for the signs, lest you be caught in a similar crossfire!
Blogged with the Flock Browser
No comments:
Post a Comment