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

"A to Z of C" in the book Cimple (ISBN 0070260982)

I was just searching "A to Z of C" in Google Books and found that the book Cimple written by Sasant K Rout has used our code. The irony is that the book was published by Tata McGraw-Hill , who rejected us in final stage stating that it wants us to get endorsement from any IIT professor, which we couldn't. (For the sake of record... IIT Bangalore was linking & supporting "A to Z of C" for long time once it's published over the net; see old IIT page from web.archives.org ) It's just another incident to prove that success isn't a measurable unit; even failed attempts can be appreciated in any other forms.
5 comments
Read more

BehaviorS.js - An alternative to Behaviour.js, event:Selectors and Low Pro libs for unobtrusive JavaScript programming

BehaviorS.js yet another unobtrusive JavaScript library similar to Behaviour.js and event:Selectors but in implementation uses hash based lookup without extending elements; so presumably it should be faster than the rest. The original script and idea was by JLof ; I extended it for DOMContentLoaded support, optimized a bit to avoid scanning of more depths, and added new rules support. I wanted to document the plug a long time and just got time to do it. For the time being BehaviorS.js is available here Update (2006-09-11) : Coralized the link to BehaviorS.js so as to save the load on free brinkster.com webpage Update (2006-09-27) : If the coralized link to BehaviorS.js doesn't work, use http://www21.brinkster.com/guideme/BehaviorS/ Update (2025-06-07) : Now available in https://github.com/rrjanbiah/behaviorsjs
17 comments
Read more

Solved: "Ports" Tab Not Visible in VS Code (WSL2)

None of the solutions I found on Reddit or GitHub worked, and most of the related GitHub issues were locked. So I'm documenting this here for future reference. Problem When using WSL2 in Visual Studio Code, the Ports tab—needed to access your application in Windows browsers like Chrome or Edge—doesn't appear. Even the Ports-related options are missing from the Command Palette. Solution After a lot of trial and error, here's what worked: Run npx serve in the VS Code terminal. It will output a URL such as http://localhost:3000/ . Click the link (or use the Follow Link option). This will open the app in your default browser. You may notice that it opens on a different port (for example, http://localhost:64198 ). At this point, the Ports tab becomes available in VS Code. After this initial trigger, the Ports tab seems to remain available in future VS Code...
Post a Comment
Read more