Lists Home |
Date Index |
Come to think of it a process would not help either in the example you mention - would it? For example if the ultimate authority for hiring in Egypt is the MD and the MD hires a person who is 14 yrs - thus totally circumventing the process what do you do?
Do you reject the hire because the process does not allow it?
processes, constraints, etc, do not reflect reality - they never were intended for that purpose.
So yes - perhaps a process is more amenable to the constraint expressed here - but ultimately all of them are trying to achieve the same end goal - prevent organizational policies from being broken; as I mentioned in my earlier post - how you enforce them is a question of tradeoffs.
Michael Kay <firstname.lastname@example.org> wrote:
> The constraints are driven by the organizational policies. If the organizational policies require that employees must be over 16, then they need to be enforced.
That's precisely the assumption I was complaining about. If the MD of your subsidiary in Egypt tells you that he has just hired a 14-year-old tea-boy, then in most organizations that I know of it's not the job of the IT department to tell him he shouldn't have done that: IT is the servant, not the master. When the crunch comes, the tea-boy won't be fired (and even if he is, the IT system will have to record the fact).
The way to enforce an organizational policy on recruitment is by having a process for approving all hiring of employees, not by restricting the capabilities of the employee database.
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!