Generic enough may be the answer, but many jobs require very specific skills. I don’t think you can build a database of skill sets of current employees b ecause those would most likely contain only those jobs the person used to create their current resume.
Right now, I work as a budget analyst, but I have many past lives in other positions that I would only use if I were applying for a specific job. As companies close, merge, are taken over, people move, etc., they may change career paths completely. The current trends in technology are changing skills requirements way faster than government classification could ever keep up with.
Example: Secretaries/Administrative Assistants used to not be paid much. They answered phones, typed and filed. They still aren’t paid much in comparison to the skills they have to have. They have to learn many systems to do their various work. They do budget, payroll, HR actions, procurement, and deal with a wide range of staff, but their PDs still have minimal skill requirements and pay. Those PDs and pay have not kept up with the technology they use and what they do.
Field staff used to just go out and take notes, stake out some quads for study. Now they have to be able to handle lots of test equipment, GPS, radios, emergency training.
When you have to have so many people involved in the development process, it is obsolete by the time it is written and then they want to adhere to it and use it for the next 20 years.
The process has to be more dynamic and responsive.
Poll of the Week
Could your inbox use a little more awesome?
Sign up to get a daily dose of awesome gov-focused resources, trainings, blogs and articles to help you do you job better.