Posts

Showing posts with the label Competencies

"First Who Then What" - Getting 'right people' in 'right seat'

Image
In the above video Mr. Jim Collins (Author - Good to Great 2001) highlights the importance of "who" before "what". If we think about this in line with strategic management perspective, we may have to amend the typical strategy development process. It usually begins with defining or re-defining Vision & Mission statement of an organization - precisely 'where to go' - the "what". Now, in case we have to begin with "who", an organization may have to opt for Resource Based View (RBV) of available human capital for 'Internal Analysis'. And make sure that we have right people on the bus. Normally this process (RBV) involves defining various resources the organization possesses and examine them to gauge which resources truly have strategic value. It is important for two reasons, 1) to know whether we have right people on the bus & 2) to remove wrong people from the bus. However, make sure not to throw out th

IBM Leadership Competencies

Image
I had referred to 11 IBM Leadership Competencies in my previous posts. Fortunately I had managed to get more details (below) of these competencies in Management and Organisational  Behaviour by Laurie J. Mullins – (2005)(Page 319-320). Hope this would give us additional insights to understand efforts taken by Mr. Louis Gerstner for the transformation of IBM during his tenure. [ IBM - List of Competencies page 210, Who Says Elephants Can't Dance? (2002) ]. This post will give us a complete picture of the significant role of competencies in organizational transformation.  Focus to Win Customer Insight Outstanding IBM managers and senior professionals put themselves in the minds of the customer, and see customers’ needs and businesses, from the customers’ point of view. They focus on the unexpressed or future needs of the customer. Managers and senior professionals having Customers’ Insight go beyond IBM’s exemplary responsiveness to customer complaints or prob

Competency-based Job Description

Image
Once, I heard someone say, what is so important about the Job Description? After all, it's just a piece of paper & what difference does that make? The Job Description can best be compared to a  'User Manual'  which tells us  'how to'  operate particular device or machine. It gives precise details about components, requirements, directions for effective and efficient use. As they say 'When all else fails, read the instructions', and, 'When all else fails, and the instructions are missing - kick it'. In our case we can't kick it; hence a wise option is to 'read the instructions'. Let us see why a Job Description is so important. As we all know the process involved for this is called 'Job Analysis' and theoretically the output is 'Job Description' and 'Job Specification'. [While the Job Description describes tasks to be accomplished, the Job Specifications lists the Knowledge, Skills, and