Skip to main content

HRM systems diagnostic checklists

For last couple of days, I have tried to get overall idea about appraisal system in other companies and materials about appraisals. While checking, I came across an interesting checklist and warning indicators:

Your organization is more than likely in trouble if any of the following holds true:
  • chronic industrial relations problems
  • no means of resolving employee grievances
  • increasing / erratic employee turnover
  • increasing number of customer complaints
  • no pride in the organization
  • inter-group conflicts
  • no career paths for ambitious talented employees
  • dissatisfaction with pay and conditions
  • unclear job roles
  • no clear performance measures
  • quality is unimportant
  • bad product service / delivery records
  • poor recruitment standards / practices
  • no management development programs
  • no induction training for new employees
  • critical skill shortages
  • inter-departmental conflict
  • you do not know if any of the above are applicable
  • you ignore any of the above
Labels:

Comments

Post a Comment

Popular posts from this blog

Open source PHP frameworks and problems

I was using CakePHP for sometime and proposed CakePlus , another UIMS toolkit on the top of CakePHP but also altering some problematic core of it. The thread should explain the outcome of the post. And, then I noted Akelos framework has most of the things built in. Issues with frameworks esp. CakePHP Scalability not a priority - Developers aren't aware that we can't throw more and more hardware Excessive use of regular expressions Evangelist isn't aware that the framework throws many queries unnecessarily More memory consumption - 100M would never be enough for a simple project Poor coding standards and practices - Prolong use of extract() often leads to more memory consumption Can't use the native approaches or baked codes. The override approach always lead to hard to debug codes Poor architected codes and no clear defined approaches. People belong to the cult drives the direction and often throws unprofiled codes. No native provision to share codes between M-V-C and...
6 comments
Read more

Interview question #2

This is related to PHP's array . An array has number of elements. All elements are integers and unique, which means there is no repetitive integers. (e.g.) $foo = array(7, 5, 9, 13, 2, 8); You have to sort the array, provided: You should scan the elements only once. You're not allowed to compare the elements when sorting. (i.e., you're not supposed to use any comparison operators) Sorted resultant array may not be the source array. How will you do that?
6 comments
Read more

What's wrong with delicious.com?

The recent UI changes of delicious.com is quite confusing and smells suicidal phase. I have noted that, after Joshua Schachter sold it to Yahoo!, it's going crazy changes. Probably, it's because a Yahoo! company now or Engineers don't get the real idea? Some crazy moves: del.icio.us to delicious.com change; probably to reach countries that censor .us TLD? delicious.com to www.delicious.com; unjustified Perl to PHP switch; why? for:handle geekish way to share to separate box; crazy but ok. Looks like, the new Yahoo! guys don't know how to make it a cult following like how twitter popularized @handle Recent broken UI
Post a Comment
Read more