Spent time on an Engineering Unit and I loved the QA side of things.
Each Task/job/process was broken down to almost MacJob level and amended to cope with rule and other changes (by the incumbent). This not only listed the admin actions but also the applicant/customer actions.
By having a standard to follow, anybody could come along and do the job just as long as the 'manual' was comprehensive and complete. This would make moving people around a lot easier and would help to ensure that there is a best practice out there.
There is a need to have a latent general trade knowledge, the wider view about how things work, sitting in your grey matter but being an expert in only one area and only knowing that area is not the best, get us all moving around and we will all understand the pressures, pains and joys of each others jobs.
But there should be a plan for each individual, they should have a rough idea of when they are going to be moved (subject to the usual caveats) and where to. Individual goals should be put in place to ensure and individual does not treat each post as a quick stepping stone but a job that requires their best efforts. If it results in the best gyrating towards PSF (or what ever you want to call it) then they should have had a chance to work around the station first.
One of the better aspects of the QA manual was the onus on the customer to follow the process as well, great for chasing up 6000s, and highlighting where the real admin problems lay.