Having set up a database to record Workforce Planning data we now need some advice as to how to get the best from it.
Who is responsible for the inputting of information?
Who takes the responsibility that this information is up to date?
Is it best to make a decision to have a "start date for the information, or try to get all historical information on to the database as well?
How do you "sell" the idea of a WP database to the organisation?
Andrew Crawford
One Response
Who is it for?
All the questions you raise apply to any system, but are none the less valid for that. What worries me is that they are being asked AFTER you have ‘set up a database’.
Leaving aside what you mean by a ‘Workforce Planning’ database – general administration?, rota/shift scheduling?, succession planning? – it is a little late to be deciding how to ‘sell’ it.
Without I hope being patronising, there is no point in introducing ANY new system unless you have already identified:
the business objectives to be met, what has to be delivered and to whom, why the objectives are not being met currently and the cost of this failure.
The answers to these points should then lead naturally to what kind of system (if any) is required and what resources will be needed to implement and maintain it.
At this stage you are ready to ‘sell’ the idea and, as part of this process, gain commitment to budget, resources and responsibilities. (Of course you may not gain these commitments, but in that case the organisation doesn’t recognise the need for a new system).
It sounds as if, at the moment, you have a solution looking for a problem – which is the wrong way round. On the other hand, if you do know what the problem is, then (keeping quiet about having a system) I would go through the stages set out above and try to convince people that they have a need for which, it so happens, you have a solution up your sleeve!