How hard can it be to put in a meaningful, productive movement policy?
All that's needed is a couple of geeks to design a 'swap/transfer' program, a handful of GS-05's who can type, and an open period every so often in which people who are looking to move elsewhere can apply with their current port and a list of the port(s) they wish to move to.
Input it all into the system and have the computer spit out every 37-way swap needed in order to get it all done.
I don't really buy into the 'good worker out/slug in' line of reasoning myself. I find it hard to believe that a 'good worker, just denied a swap/transfer, and who's left to deal with the issues that caused him to ask for the swap in the first place, is somehow going to remain 10-8. More than likely, imo, that 'good worker' finds himself down, out-of-it, and mailing in his performance at some point soon thereafter.
Or...in other words...reduced to a slug himself.
All that's needed is a couple of geeks to design a 'swap/transfer' program, a handful of GS-05's who can type, and an open period every so often in which people who are looking to move elsewhere can apply with their current port and a list of the port(s) they wish to move to.
Input it all into the system and have the computer spit out every 37-way swap needed in order to get it all done.
I don't really buy into the 'good worker out/slug in' line of reasoning myself. I find it hard to believe that a 'good worker, just denied a swap/transfer, and who's left to deal with the issues that caused him to ask for the swap in the first place, is somehow going to remain 10-8. More than likely, imo, that 'good worker' finds himself down, out-of-it, and mailing in his performance at some point soon thereafter.
Or...in other words...reduced to a slug himself.
Comment