Resume Bombs
Here's the problem. You can't build a resume with the following:
I took over a program that was doing pretty well, so I just kept things humming along in the same general direction. I may have tweaked a few things here and there, but basically I just left well enough alone.
No, to really put some beef on the old resume, you need a sentence that starts with "Implemented..."
And so, the resume bomb.
Someone moves into a new administrative position and starts looking for a way to Make a Splash, Leave Their Mark, or Show They Are a Dynamic Change Agent.
They may consolidate power by taking over functions previously performed by staff or other offices. They will certainly create a new program. And they will develop and start the implementation of the policies and procedures needed to support the new program. Congratulations. You have your brand new resume bomb, and your new administrator will grab his brightly polished resume and get out the door to his next job before the bomb ever goes off.
Some bombs have a long fuse. The program gets up and running without too much incident, and it is only once you get further down the road that serious problems begin to emerge, that the new program begins to create some real problems for the district. But by then, the one person who knows exactly how it's supposed to work and how to keep it functioning and can answer questions about it-- that person is at his next job.
Some bombs have a short fuse, or are set off by the administrative departure itself. "We just need to rip up this system here, and I'm going to create a new policy with software support over here, and CURMUDGUCATION: Resume Bombs: