I'm all for a good process, I love ticking things off a list, and knowing what the next step will be. It kills me when I don't know or understand what's involved in a process. I absolutely hate it when consultants tell me "not to worry about the detail" when they're doing things for me. I'll admit that for some people this would be seen as needing to be in control (maybe I am a control freak!) and for others it might be seen as just good practice. Whatever, I have a process for pretty much everything my business does. I've even got the processes written down in many cases. There's still a few things that would benefit from being tried and tested, but we're getting there.
Here are the headlines of my pay review process:
That's the nutshell version, the major process document runs to 2 pages. Why? Because someone somewhere needs to know what the history is, or have checked past reviews for anomalies and know what policy decisions were made, or what went wrong, so that these can be take into account for the future. This will probably be the person everyone goes to with the "can you remember why......" queries and issues.
Of course I know that not all of these steps apply in every organisation, and some will not be applied even if they should, but that's just reality in practice.
Hopefully I've helped someone with these thoughts. My next blog will be on the decisions you really should document, and the one after that will be about supporting managers with the process.
If there was one piece of advice you could give someone undertaking a pay review for the first time, what would it be?
Reward Risk Management Ltd.