Monday, August 17, 2009

The power of ‘carrot and stick’

It seems rather ‘regressive’ for someone who calls himself an ‘Organization Development Professional’ to write a post on ‘the power of carrot and stick’. Haven’t we transcended the ‘carrot and stick’ method of motivating employees a long time ago (at least after Frederick Herzberg came up with the ‘two-factor'/'motivation - hygiene’ theory almost 50 years ago)?

The objective of this post is not to recommend or to praise the ‘carrot and stick method’. It is just to examine the actual situation in this domain (in terms of both theory and practice) and to explore the possible reasons for the 'power of carrot and stick'. We will also look at possible responses to this situation - from both the employee's and the employer's points of view.

While today's organizations are unlikely to talk about the 'carrot and stick method', if we analyze the methods that are actually being used by organizations to 'motivate' their employees, we are likely to find a high amount of ‘carrot and stick’ element in them. Of course, the ‘carrots’ and ‘sticks’ have become more sophisticated. But, in time of ‘organization stress’ (e.g. the recent economic downturn) some of this sophistication often disappears and more crude forms of ‘carrot and stick’ (that were thought to have become extinct) reappear!

Let us come back to Herzberg. Technically speaking, the ‘two factor’ theory of Herzberg is primarily about ‘satisfaction and dissatisfaction’ – and not exactly about motivation (as job satisfaction might not necessarily lead to motivation or productivity). So it seems possible that the ‘carrot and stick’ method of 'motivation' might be very much alive – both ‘in theory' (more about this later in this post) and ‘in practice'.

Now, let us examine why the 'carrot and stick method' works so well. I think that the power of ‘carrot and stick’ emanates mainly from the fact that it takes advantage of two of the most basic human emotions -‘desire’ and ‘fear’. To be more explicit, ‘carrot’ scores a direct hit on ‘desire’ and ‘stick’ does the same on ‘fear’. It can be argued that if we use the terms ‘desire’ and ‘fear’ in a broad sense, most of the human emotions (and hence most of the human behavior and motivation!) can be ‘modeled’ in terms of these two (and the human responses to them).

If we push the above argument a little further, it can be deduced that the so called ‘content theories’ of motivation (especially those that talk about fulfillment of ‘needs’ – e.g. Maslow’s hierarchy of needs, ERG theory, McClelland’s theory of needs etc.) can’t distance themselves too much from ‘desire’ element (and hence from ‘carrot and stick’). Similarly, if we take a close look at some of the ‘process theories’ of motivation (e.g. Expectancy theory) we might be able to detect elements of ‘carrot and stick' in them also (e.g. especially in the 'valance' part of the 'expectancy - instrumentality - valance' chain/of the cognitive process that leads to motivation, as per the Expectancy theory).

If we consider motivation as a 'state of mind' (i.e. something that happens in the mind of a person), 'carrot and stick' (or anything external to that person, like what the manager/ employer does) can't directly cause motivation to occur - it can only create a situation where motivation is likely to be 'triggered'. Again, the method for applying carrots and/or sticks for maximum effectiveness (especially if we take the sustainability of the effectiveness account), can become quite complex. There have been quite a few studies on the effectiveness of various types of positive and/or negative reinforcement strategies to elicit desired responses. So the 'power' of 'carrot and stick' does not imply that the application (of 'carrot and stick') is always easy!

Now, let us look at this situation from the other side – from the point of view of the employee who is at the ‘receiving end’ of these motivation strategies. From the above discussion, it can be seen that if an employee wants to be immune from the power of ‘carrot and stick’, he/she should develop immunity from ‘desire and fear’ – at least those types of desires and fears that can be leveraged/manipulated by the employer. Easier said than done – I must admit - for most of the 'real' people in 'real' organizations! By the way, in the novel 'Siddartha' by Hermann Hesse, there is a beautiful description of how this method of motivation (implemented through an incentive scheme - with a significant upside and downside for the employee) attempted by an employer (Kamaswami, the rich merchant) fails to have any impact on an employee (Siddartha) who had transcended 'desire and fear' ("Siddartha can think, Siddartha can wait, Siddartha can fast"). It is also interesting to note that this novel was first published in 1922 - much before 'HRD' (in the current sense of the term) came into existence.

My point is not that most of the human beings are nothing more than bundles of ‘desires and fears’. We are capable of other emotions (like love, sense of pride, sense of duty, quest for purpose/meaning etc.) that might go beyond ‘fear and desire’. So it should be possible to find ways of motivation based on these 'higher' emotions. However, these higher emotions might not be very easy to ‘manipulate’ in an organization setting. Please see 'Passion for work and anasakti' for a more detailed discussion on this.

Now, let me tell you a little bit about incident that triggered the thought process that resulted in this post. One of my friends asked me to comment on an article which argued that ‘Leaders should inspire people as opposed to motivating them’. When I thought about this, I felt that the situation was a bit more complex than what it appeared to be – when we look at what really happens in many organizations. Most of the organizations have an essentially top-down goal setting/goal cascade process. While individuals might have some degree of freedom to shape their roles/deliverables, individual goals must add up to the corporate goals. Also, organizations usually hire people to do a particular job (which might even have a formal job description that details the job responsibilities). These factors can lead to a situation where a large part of what needs to be done by a particular employee has been 'fixed'/‘mandated’ or even 'imposed'. If what you need to do is fixed, then whether the leader ‘inspires you’ or ‘motivates you’ to get the same thing done can become essentially a matter of semantics!

I also feel that ‘inspiring someone’ (creating a situation where someone might become inspired- to be precise) is a more unpredictable process (in terms of outcomes) as compared to 'motivating someone' (to do a particular task – say through carefully applied positive and/or negative reinforcement - including the promise/threat of applying/withdrawing positive and negative reinforcement or ‘carrots and sticks’ !). No, I am not endorsing the 'morality' of these 'motivation' techniques. I am just saying that they are possible. I must also mention that there could be situations where these techniques might fail. For example, it is easy to create 'incentives' (financial and non financial) for someone to write a book. But, whether this can result in a 'great book' (if the author is not really inspired to write the book) is debatable. However, the fact still remains that 'inspiration' is often a complex (and elusive!) phenomenon.

While, your manager can 'inspire' you, what you will end up doing based on (triggered by) that inspiration can’t always be predicted accurately. So, if the objective is to get you to do a particular task, I am not sure if the pure inspiration route will always work. Any attempt to make the inspiration more controlled, will bring in the element of manipulation that this inspiration approach is trying to avoid. Of course, if we are talking about a community with no predefined goals (as opposed to organizations that usually have predefined/ mandated goals) then this inspiration approach might work – though no one can predict what will exactly will the outcome be (at the individual and at the community level – considering ‘interaction effects’ and ‘emergence’)!!

Well, it can be seen that the post that I ended up writing (based on the above trigger) went much beyond a response to the immediate ‘provocation’. May be I was inspired (as opposed to just being motivated)!!!

Now, over to you for your comments!

Note 1: It might be possible to make a distinction between actions that we take because of some sort of compulsion and those we take because we really want to do so (e.g. between compliance and commitment). The problem here is that compulsion does not necessarily mean coercion (at least not in the usual meaning of the term 'coercion') - any sort of 'inducement' can also imply compulsion. In a way, all we can observe is the action and the reason behind the action is some thing that we infer - especially in the case of other people. Even if we are talking about our own actions and the reasons for those actions there is the problem of rationalization (e.g. we can attribute the 'good' actions to intrinsic motivation and the 'not so good' actions to external compulsions). Hence the distinction between the two types of actions can get blurred.

Note 2: In this post, the term 'desire' has been used in a broad sense. This makes it easy to link 'needs' and 'carrots' to this term. But it can also be argued that if we use broad definitions for fear and desire, even the 'higher order' emotions mentioned above (like love, sense of pride/ duty/ purpose/ meaning etc.) can be mapped to/'reduced to' (at least, in the 'factor analysis' sense) the core emotions of fear and desire. To deal with this, we need to define these terms (terms like desire, fear, love, sense of purpose and of course the terms action/ motion/ movement, motivation, and inspiration) more precisely and in a manner that has internally consistency/ coherence (at least 'arbitrary coherence' -as Dan Ariely says in his book 'Predictably Irrational') . But that involves too much work (may be even a lifetime of work!) which is beyond the scope of this post.

Note 3: Now, that I have mentioned the name of Dan Ariely, I must also say that I am fascinated by the work that behavioral economists (like Daniel Kahneman, Richard Thaler & Dan Ariely) have done in exploring the domain of human motivation and decision-making - and the predictable irrationalities in the same. Their studies have also shown that 'relational rewards' work better than 'monetary rewards' in many circumstances, though relational rewards have the disadvantage of raising relational expectations. Please note that this does not negate the 'power of carrot and stick' . We can always say that while relational rewards ('relational carrots') and different from 'monetary/transactional rewards' ('transactional carrots') - they are still 'carrots' - carrots that appeal to higher order needs (say in Maslow's hierarchy of needs). Again, it has been suggested that monetary incentives work best in the case of simple tasks (tasks involving straight forward physical or mental activity; i.e. tasks that don't require creativity) where higher performance is just a matter of trying harder and where the performance can be measured accurately. This also need not necessarily create problems for the 'power of carrot and stick theory' as this is more about the relative effectiveness of carrots. We must also note that there is an intense debate going in between 'rational choice economists' and 'behavioral economists' - regarding the applicability of the findings from behavioral economics experiments. It has been argued that we are quite rational in most circumstances (i.e. in our natural habitat/ in familiar situations) and these predictable irrationalities surface mainly in in unfamiliar circumstances and that the conditions created in some of the behavioral economics experiments are quite unnatural (i.e. not representative of the conditions faced by most people most of time in the real world). Even the very definition of rationality is open to debate (e.g. rationality can be defined narrowly - just as a consistent system of preferences/consistent response to incentives - even if these preferences might not be 'good' for the decision maker - as judged by the society)!

Note 4: It can be argued that all the leadership/management actions involve influencing and hence some element of manipulation (as it involves getting a person to do something that he/she would not have done otherwise). Now, whether this manipulation is for a ‘good’ cause (and for whose ‘good’) will bring us close to the domain of ethics (and the tricky terrains of situational ethics vs. code ethics, individual good vs. collective good, good of one collective vs. good of another collective etc.). For example, if my manager gives me some information that opens my mind (e.g. by enabling me to see some possibilities that I was not able to see before), I might get inspired (and do something that I might not have done otherwise). But if my manger gives me the additional information selectively, so that I will see only those new possibilities that he/she wants me to see (e.g. so that I will take some particular action) then the element of manipulation creeps in. Yes, the line between 'management and manipulation' or that between 'influencing and manipulation' can be a very fuzzy one!

Sunday, April 19, 2009

The leadership sandwich

This is a 'thinking aloud' kind of post. Usually, I find it difficult to do 'thinking aloud' kind of activities. My reasons (rationalizations!) for this revolve around my personality type (INTJ or 'Dominant Introverted Intuition' - in MBTI/'type dynamics' terms). Of late, I have been reading some books written by Alan Watts and I came across the the following "It is surely a kind of spiritual pride to refrain from 'thinking out loud', and to be unwilling to let a thesis appear in print until you are prepared to champion it to the death. Philosophy, like science, is a social function, for a man cannot think rightly alone, and a philosopher must publish his thought as much to learn from criticism as to contribute to the sum of wisdom." Inspired by this, I have decided to write this post.

The trigger for this post came from some of the conversations that I have been having with my son (the same guy who was the main character in my earlier post called 'Research and a three-year-old' - though he is now seven years old!). During the last academic year, he got his first taste of 'being a leader' - when he was made the 'leader' of his group/class on certain occasions/ for certain events and he has been sharing his experiences as a 'leader' - both good and bad -with me. These discussions about the 'leadership experiences' of a seven-year-old, made me remember a curious thing that I had noticed about the roles and designations - especially in IT/ITES organizations.

In these organizations, often there is a level called 'Team Leader' that appears - just above that of a Team Member - but below that of a 'Team Manager' or 'Project Manager'. Beginning with the Team Manager/Project Manager level, there are multiple levels of 'Managers'. But after these 'managerial levels', 'Leaders' (e.g. Business Leaders) again make an appearance. So we have a curious situation - we have managers 'sandwiched' by leaders. Hence the 'leadership sandwich' which forms the title of this post.

Now let me come back to the 'thinking aloud' part. I was wondering why this 'leadership sandwich' occurs. Why do we have levels/roles with the term 'Leader' in the title on both the sides of the levels/roles with the term 'Manager' in the title? Since too much have already been written about the 'Leaders Vs. Managers debate', I have no intention to get too deep into that tricky territory. But these kind of 'sandwich' situations interest me immensely - because I feel that some phenomenon similar to that of the 'U-curve' (which I have often written about and which is very close to the basic theme of this blog) might be operating here. In such cases something starts in one state - moves to the opposite state - and then comes back to the original state at a higher plane (creating a 'U' - shaped pattern). So I was wondering if 'Leadership' also follows such a 'U' - shaped pattern!

May be we can get a clue to the (leadership sandwich) puzzle if we compare the role of a Team Leader with that of a Team Manager. Typically, a Team Leader does not have formal authority (e.g. to hire, fire, evaluate and reward staff). So a Team Leader is forced to influence (get the work done) without formal authority. Team Managers (and the multiple levels of Managers above them) do have formal authority. Of course, the 'Leaders' who are at higher levels as compared to these 'Managers' also have formal authority - much more than what these 'Managers' have. But may be these senior 'Leaders' are supposed to influence (get the work done) without exercising their formal authority, though they do have a lot of formal authority. May be they are supposed to do the influencing in 'better/higher ways' (e.g. by creating an inspiring vision, by building a high performance culture etc.). So if we can say that "Team Leaders influence without formal authority because they don't have any formal authority and Business Leaders influence without formal authority because they choose not to exercise their formal authority" - then we have the description of a phenomenon that follows the U-curve - that too perfectly!

Now, let us come back to the second part of what Alan Watts said - the part which says that 'a man cannot think rightly alone and that he should publish his thought to to learn from criticism'. I have done the publishing! Over to you for your criticism!!

Sunday, March 29, 2009

Career development and 'sublimation'

Since the words ‘career’ and ‘sublimation’ have many meanings/interpretations, let us begin by defining these terms - for the (limited) purpose of our discussion.

Career – pursuit of consecutive progressive achievement where one takes up positions of increasing responsibility, complexity & contribution

Sublimation - change directly from the solid to the gaseous state without becoming liquid (so we are using the 'Chemistry' meaning of 'sublimation' - as opposed that in 'Psychology')

Now that we have got the definitions out of the way, let us come back to the issue at hand. These days, it is quite common for people to skip some of the steps in (what used to be) the 'typical career path'. That is, they jump from a particular position to another position that is more than one step away/higher. So they transition directly ('sublimate') to a significantly 'higher' position without going through (what were considered to be necessary) intermediate positions.

These kind of career moves make a lot of sense in today's scenario - where many organizations are in state of flux - making traditional 'career paths' and 'career ladders' less relevant. Again, organizations are more open to this kind of career moves these days, especially where this results in cost saving and lower time to fill a vacancy. Of course, it makes eminent sense also from the individual's point of view - in terms of faster career growth.

So, if this 'sublimation' seem to make sense - from the points of view of both the individual and the organization - what is the issue? I think that this 'sublimation' can create problems - for the individual and for the organization.

For the individual, skipping intermediate positions in the career path can result in loss of learning opportunities - and some of these 'missed learnings' can prove costly - in terms of the adverse impact on long term career success and on personal effectiveness at work. Some of the intermediate positions might be key from a 'career & professional maturity' and perspective building (and wisdom development!) points of view. While the 'higher' positions will also provide valuable learning opportunities (may be even learning opportunities at a broader/'higher' level), they can't always substitute for the learnings provided by the intermediate positions. I would even speculate that time spent in the intermediate roles might have a positive impact on the 'ability to learn' - including the ability to learn from opportunities at a broader/'higher' level. The situation is not dissimilar to that of children who are 'forced' (e.g. by life situations) to grow up too fast. They manage to act like grownups - but often they have hidden flaws in their (psychological) development.

Often, after one has taken up a 'higher role' (in terms of organization hierarchy) it becomes difficult* (see the note below) to take up these intermediate roles - unless one moves to another ('bigger'/'more reputed') organization. So it is possible that these necessary learning opportunities are lost forever for the particular individual. Let me give a personal example. I moved to a global/corporate role in the Learning and Organization Effectiveness (L&OE) domain without spending time in a role that involves handling complete operational responsibility for the L&OE function/team at the business unit/country level. At this point, I don't really know what exactly have I missed because of this 'sublimation'. While I have tried to find this out by speaking to people who have handled such jobs (some sort of 'knowledge engineering'), I do feel that there could be significant gaps in my understanding! After all, there is a difference between understanding/wisdom (that is developed from actual experience) and knowledge.

This brings us to the problem of 'unknown unknowns' -a key side effect of 'sublimation' - which can create problems for both the individual and for the organization. Usually, 'unknown unknowns' are more dangerous than 'known unknowns'. Based on our discussion above, it can be seen that the 'sublimated individuals' can create serious risks for the organization. While the 'sublimated individuals' are usually very confident, their confidence often stem from 'simplicity on this side of complexity' as opposed to 'simplicity on the other side of complexity'. These 'unknown unknowns' can seriously undermine the quality of decision making. This becomes a major cause for concern when these individuals are in positions where their decisions can have high organizational impact. From the individual's point of view, a key risk is that of self-destructing their fast track careers! Other risks for the individuals include becoming too big for most of the roles available in their domain too early in their careers (limiting their options for changing jobs - see here for a related HR specific discussion) and of course that of 'reaching their level of incompetence' too fast/too early in their careers!!

So there can be problems/costs involved with 'sublimation'. But there are also potential benefits (as we have seen earlier). In addition to this, we should keep in mind that there are approaches like job rotations, stretch assignments and action learning projects that can provide accelerated career development while avoiding some of the problems associated with 'sublimation' - at least to a large extent. Hence it comes down to a cost benefit analysis - which can be highly context specific - both for the particular individual and for the particular organization - making a standard solution/recommendation difficult. But the awareness of the options and the possible problems/benefits can facilitate better cost benefit analysis and more informed decision making.

*Note: The difficulty in moving into a role that is 'lower' in the organizational hierarchy could be in terms of the possible adverse impact on salary, organization level etc. I do feel that the degree to which the difficulty is felt by an individual also depends on his/her outlook towards salary and career growth. The two extremes here are 'shape approach' and 'area under the curve approach'. It is essentially a matter of what one is trying to optimise - 'shape of the graph' or 'area under the graph'. Let me explain using salary progression as an example. Let us visualize a diagram ('salary graph') with salary on the y-axis and time on the x- axis.

Those who take a 'shape of the graph' approach/philosophy want to ensure that their salary goes up each time they make a job change (either within an organization or across organizations). So they want the salary graph to have a nice shape - with a positive 'slope' at all times. These kind of people will not want to take up a very high paying job if they feel that the salary growth is not sustainable and that they might have to take a pay cut later when they move from the very high paying job.

If we go back to our salary diagram (with salary on the y-axis and time on the x- axis), the area under the graph signifies the total earnings over a period of time/over the span of the career. It is apparent that what the people who take a 'area under the graph' approach/philosophy are trying to maximise is their total earnings/salary. These kind of people will take up a very high paying job even if they feel that the salary growth is not sustainable - so long as their total earnings (over the span of their career) are likely to be higher.

Of course, the above approaches ('shape of the graph' and 'area under the graph') apply not only in the case of salary but also in the case of other dimensions of career growth like 'size of the role' , 'position of the role in the organization hierarchy' and 'learning experiences provided by the role'. It is interesting to note that 'shape of the graph' approach/philosophy is reflected in many of the typical definitions of the term 'career' (even in the one that is given at the beginning of this post - as it talks about ' pursuit of consecutive progressive achievement' and about 'taking up positions of increasing responsibility'). But we have seen that this not the only approach possible or even the most effective one in today's environment. So if one takes the 'area under the graph' approach(which is more attuned to today's scenario), the 'difficulty' mentioned above can become much less significant.

Now over to you for your comments and suggestions!

Friday, November 14, 2008

In the wonderland of HR Business Partners – Part 1

The posts in this series constitute some sort of 'random' walks in the wonderland of HR Business Partners (HRBPs). Since our objective here is to explore the terrain (and not to reach anywhere in particular), we have the liberty of adopting the amazingly liberating philosophy of "if we take any path and walk long enough on it we are bound to get somewhere".

There are a wide range of HR roles that go by the HR Business Partner (HRBP) title. For the purpose of our discussion, let us focus on ‘pure’ HRBPsHRBPs whose role is that of being a strategic business partner - to the business they are supporting. This would mean that they are supposed to have very little or no transactional/operational HR responsibilities. So these roles (HR roles that don't do usual HR work) are some sort of freaks of evolution- in the evolution of the HR function. Freaks occur in the course of biological evolution also. But they are unlikely to create much of a problem as they usually don't live long enough to reproduce. However since HRBPs can (and do) survive long enough in organizations to create (hire/develop) more HRBPs, it is worthwhile to take a closer look at them and their world.

I must say that I have handled HR Business Partner (HRBP) roles – in the not too distant past. Most of what I say in this series of posts are based on ‘hard experiences’ – mine and those of my fellow HR Business Partners – across organizations. While some of the observations in this post might seem funny, I have absolutely no intention to make fun of HRBPs. I know the challenges and complexities faced by HRBPs a bit too well to attempt something like that. Again, though I am in a specialist role now, I have a great amount of respect for HR generalists (see ‘In praise of HR generalists’), – including HRBPs.

In the wonderland of HR Business Partners – Part 1 : Seven guaranteed ways to make an HR Business Partner fail

A story...

Once upon a time, there was an HR Operations leader who was doing very well in his job - happily implementing HR processes & policies. Then the corporate HR leadership in his company came under the spell of Dave Ulrich’s ideas - or what they thought be Dave Ulrich’s ideas. They also saw other firms in their industry adopting such ideas. They did not want to be left behind. After all what is the fun of being in corporate HR - if you are not considered to be 'progressive' and 'state of the art'. So the inevitable happened - the company changed its HR operating model - worldwide.

Being ‘top talent’, our HR Ops leader was chosen to move into one of the newly created HR Business Partner roles - the roles that were supposed to take the HR function in the company to the next level of excellence and to add immense value to the business.

He understood that he should play a strategic HR role. He knew that he should partner with the business leadership. He knew that he was a high cost resource and hence he should produce good results-that too quickly. He wanted to do a good job – he was a top performer throughout his career.

So he worked very hard. In the spirit of collaboration and to ensure seamless service to the business, he did his best to proactively cooperate with other parts of HR and even with the finance & communications teams of the business he was supporting.

Many months passed. Our HR leader was feeling strangely uneasy. Initially, he could not figure out what was wrong. He was doing a lot of things - including participating in all the Leadership Team meetings of the business. He was in a role that was supposed to be the 'highest form of evolution' among HR roles. But he was not feeling happy. Sometimes he felt that he was like a 'mouse in a maze' - running here and there, feeling extremely busy, but getting nowhere. So he took a week's leave - to think things over. After he was away from the pressures of work for a few days, things started becoming clear in his mind.

He realized
…that playing a strategic role required skills he did not have & that these skills are not easy to develop - especially in a short period of time
…that what the business leaders expected from him was not really strategic
…that they wanted him to ‘manage the HR system’ – to ensure that what they want gets done
…that he was getting involved in issues that he was not supposed to – as per his role
…that he was fighting too much with other parts of HR - leading to too many escalations and that the global HR function was looking less like a 'team' and more like a 'house divided against itself'
…that Finance team was not taking him or his role seriously
…that he couldn't get reliable data to analyze business level patterns & trends on people issues
…that he wouldn't have enough results to show at the end of the year to justify his salary &
…that no one really understood what exactly his role was supposed to deliver

Being an intellectually honest person, he could not help wondering if he himself understood his role correctly & if his role really existed.

7 guaranteed ways to make an HRBP fail

1. Don’t define the scope and responsibilities of the HRBP role clearly

2. Don’t establish the performance measures for the HRBP role

3. Don’t secure the buy-in/agreement from the business leaders for the HR operating model, HRBP role, its deliverables and the choice of the role holder

4. Don’t make the other parts of HR (HR operations, specialist functions etc.) accountable to the HRBPs

5. Ensure that the HRBP does not have the data and analytical/reporting tools to derive the business-level patterns/trends on key people and business related parameters. This will create a situation where the HRBP can't work at the patterns/trends level (as they are supposed to do), prompting them to get involved in 'individual employee- level' issues (after all they have to something) - a great recipe for ensuring 'territory battles' with HR operations.

6. Move HR staff from other parts of HR into HRBP roles without verifying if they have the requisite competencies to be effective in the HRBP role. If you can't find any other role for a senior HR leader, move him/her into an HRBP role. Assume that the vacuum created by the removal of transactional/operational HR responsibilities will get automatically filled up by strategic activities (see 'Nature abhors vacuum' for more details)

7. Change the HRBPs frequently - before they have had the opportunity/time to understand the business or to build relationships and credibility with the business leaders

Now that we have heard the story of an HRBP and also derived some lessons from the story, let us explore what can be done to maximize the chances success in HRBP roles. Some of this can be derived from this post itself – by logical deduction. But some other aspects are not so obvious or easy. Anyway, we will look at some of them in the subsequent posts in this series.

Over to you for your comments/suggestions and experiences!

Saturday, November 1, 2008

Crazy HR for crazy times!

It has been argued that insanity is a perfectly sane response to an insane environment. This also implies that ‘abnormal’ situations require ‘abnormal’ responses. While I have often talked about the connection between HR and madness (see ‘HR professionals and Multiple Personality Disorder' and ‘Career Planning and the Myth of Sisyphus’), here I am using the term ‘abnormal’ in the statistical sense of the term (i.e. not fitting into the normal distribution). So in this context, 'abnormal' just means ‘different from normal’.

The basic point in this post is that normal/usual HR responses (HR strategies/practices) are based on certain assumptions about the situation (context/environment) in which the organization (and hence HR) is operating in and when we are faced with situations where those assumptions are not valid, normal/traditional HR responses will not be effective. It also follows that when situations are radically different from usual/normal, we might need HR responses/practices that look very different from the normal/usual HR responses (i.e. responses that are ‘abnormal’) – and that is where we come to ‘crazy’ HR. Again, with the ‘abnormal’ situations becoming increasing common, effective HR responses/practices might also become increasingly ‘crazy’ – till we redefine (or even reverse the definition of!) what is ‘normal’ and what is ‘abnormal.

Now, let us look at a few typical practices/principles/assumptions in HR and explore the implications for the HR response when we are in contexts where those assumptions are not valid. Please note that these situations (and responses!) are not independent - there are common themes - and even contradictions - among them!

1. From long-term employment relationship to short-term employment relationship

This is a big one. Actually, 'continuity of employment relationship' can be treated as the basic assumption that underlies many of the assumptions in HR. If we look at many of the HR systems (like career planning, training and development, staffing etc.) there is often an assumption that the employees/prospective employees will stay with the organization for a long period of time. Now, if one is in a context (organization/industry) where the most of the employees spend much less than 2 years in a particular organization, these assumptions and hence HR strategies/ practices/ systems based on these assumptions, are obviously not valid/effective. So what makes more sense is to assume that the organization would be involved in 'managing' (planning/ developing) only a limited (often very limited) part of the career in the case of most of the employees and to design HR strategies/systems/processes accordingly.

Now, the idea here is not that the systems/processes should be designed to push most of the employees out in two years or less! The idea is just that the HR strategies/systems/processes should not ignore the ground reality - even if it is unpleasant.

In many contexts the reality is that most of the employees are likely to spend only a very limited time in the organization and that HR strategies/systems/ processes should deliver value to the employees (and enable the employees to create value for the organization) within that time while maximising the return on HR investment for the organization. Of course, if one has a reasonable chance to shape the situation (or to create a new reality that is more favorable), it makes sense to make an earnest attempt. May be the attempts to shape the reality (i.e. increasing the time that the employees spend in the organization) will be more successful-if they are focused mainly on some segments of the employees (we will discuss this further later in this post). But 'deluding oneself' or 'wishing away the reality' don't really help - and this brings us to our next point.

2. From trying to reducing attrition to redesigning HR systems to work well in a high attrition environment

The typical HR response in a high attrition situation is to try to reduce attrition. But after one has repeatedly tried this and has failed consistently, this response no longer makes much sense. A better option may be to re-design the HR policies/processes/systems so that they can work effectively in a high attrition environment.

As an example of re-designing an HR system/policy to suit a high attrition environment, let us look at the Training and Development system. In a high attrition environment, there is a high possibility that employees who have been trained (at a significant cost to the company) may leave the company to join a competitor. Now, there are multiple ways of responding to this. One option is to focus most of the training investment on top talent and on employees in critical roles (i.e. don’t try to follow the approach of providing training to everyone). Since they form only a small percentage of the total employee population, the organization (with even limited resources) will be in a better position to create a compelling value proposition for them. So the organization will have a much higher chance of ensuring good return on training investment. The training needs for the rest of the employee population should be met mainly through a shared training infrastructure that provides e-learning solutions for common learning needs. Of course, there are other approaches like skill-based pay, training bonds etc. that tries to ‘lock in’ the employee. But my preference is for the approach focusing on top talent and on critical roles.

3. From Job enrichment to Job deskilling

Designing/redesigning jobs to increase their motivational potential has been a key principle in HR. This is typically done by improving various dimensions of work like skill variety (the variety of activities required), task identity (the completion of a “whole” and identifiable piece of work), task significance (how substantial an impact the job has) and autonomy (the freedom, independence, and discretion that one has to do the job).

Now there can be situations where the opposite of this response (i.e. job deskilling) might be called for. Examples of this can be found in situations where is a critical need to

(a) Manage process risk - Creating detailed process maps that specify each step in micro-detail (e.g. level 5 or level 6 process maps) and insisting that the employees carry out each step as it is described can be good way to manage process risk/reducing chances of error (though it adversely impacts 'autonomy' and hence job enrichment mentioned above).

(b) Reduce cost - The same approach (detailed procedures - strictly enforced) can also reduce the skill-level required to do the job. This can obviously provide opportunity to reduce salary cost (as employees with lower skill profiles can be hired for the job) and training cost (as not much training is required).

(c) Operate in high attrition environment - Again the same approach (detailed procedures and lower skill profile) can make it easier to find and replace employees (as there is not much need to hunt for specialized skill profiles that can be difficult, time consuming and costly to find) and to minimize the adverse impact of employee turnover on work/deliverables (as the 'learning curve' of new employees can be very short because of the low skill requirement of the job).

But there can be many complications when we try to implement the above (job deskilling) idea. Let us look at a couple of the major ones.

The first one is that in some contexts the nature of the work makes the 'formulating detailed procedures and enforcing them strictly' approach difficult to implement - because there are certain parts of the job that require a high degree of skill/judgment/discretion. Here one can try to re-design the jobs so that the activities that require a high level of skill are grouped into a few jobs and most of the other jobs consist of activities that don’t require high degree of skill (where the above approach will work). Of course, this will work best if there is an opportunity to reengineer some of the processes so that there will be greater opportunities for re-designing jobs/grouping activities into jobs differently. Now, this has other advantages like further saving on salary cost (as we need fewer number of high cost specialist positions) and reducing attrition among the highly skilled jobs (as the specialist jobs get enriched in the process because the lower-skill parts of the job are taken away and as the organization can provide these specialists much better value proposition because they are small in number - making the additional investment required much smaller and manageable).

The second problem arises from the very nature of the job-deskilling approach - lower skill requirement for the job is likely to result in lower 'motivation potential' for those jobs (because of its adverse impact on the factors that drive job enrichment that we had discussed earlier). But this can also be avoided to a large extent. Here the trick is to change the profile of the candidates/jobholders. So if the job was being done (before the job re-design exercise) by a graduate engineer, the candidate for the deskilled job should not be a graduate engineer (who will find the job de-motivating) – it should be someone with only an engineering diploma/certificate. Now, what seems routine for a graduate engineer can still be quite challenging and motivating for a certificate holder. Of course, this approach also has cost advantages (as a certificate/diploma holder in engineering costs less as compared to a graduate engineer).

I am not saying that these are the only HR responses possible (or even the best responses) in the situations described above. My point is that certain situations require radically different HR responses – responses that seem so different from the usual/traditional HR responses that they appear to be crazy. But they are actually much more sane - as compared to the alternative of 'continuing to persist with the same (failed) normal/traditional HR response and expecting different results' - which incidentally was the way Einstein defined madness.

What do you think?

Monday, October 27, 2008

A decade of 'active experimentation' in HR

Of all the models/concepts that I encountered during my MBA studies in HR, one of the few that I haven't managed to forget (even after 10 years) is the 'Kolb's learning cycle' - according to which 'experiential learning' takes place through cycles of 'Active Experimentation, Concrete Experience, Reflective Observation & Abstract Conceptualization'. Now, what triggered the memories of this 'old friend' was the new novel written by Abhijit Bhaduri. This book(Married But Available), deals with the first ten years of working life of a young HR professional (Abbey) after he completed his MBA in HR from MIJ(Management Institute of Jamshedpur).

Since I am completely 'innocent' of any deep understanding of fiction (or of reviewing books for that matter), I will confine my self to commenting on (what I think are) a few themes in the book that relates to HR and to the career of an HR professional. While I have also just completed the first decade of my career in HR, I am not sure if that places me in a better position to comment on the book. You see, my data set (primary and secondary points I have on the matter) is limited and it does not come any way close to being a 'representative sample'. So this might make me more prone to the risk of generalising based on limited data. Hence these comments may be based on assumptions/inferences that are closer to fiction than the story that Abhijit tells.

The first one is the tendency of MBAs to compare (or 'benchmark') their achievements against that of their batch mates. Now, this tendency is likely to exist, to some extent, in any group. But the 'pressure cooker' nature of many MBA programs coupled with the high degree of 'results orientation' in many MBA students can make this 'tendency to compare' more pronounced among a batch of MBAs. The situation becomes more interesting in the case of HR MBAs, as 'position and salary benchmarking' is part of the job responsibilities of many HR professionals. Yes, this tendency can lead to lot of unnecessary suffering, especially in those situations where a person's identity (and self worth) is defined mostly in terms of his/her job (see Job and Identity) - because in those situations, the comparisons go beyond 'comparison of achievements' (and get into the territory of comparison of 'worth of individuals'). One good thing is that after a few years out of the B-school, it becomes very difficult to make exact comparisons - as people would have taken different career paths - and as there are often significant differences across organizations in terms of roles, levels and designations. Also, over a period of time 'internal benchmarking' (comparing oneself with people within the organization that one is working) becomes increasingly more important (as compared to comparing oneself with batch mates in other organizations). Again, people might have/use different definitions of success (different parameters to measure success or at least attach different relative weights to the parameters) - making the comparisons even more difficult. So even in those cases where one is not able to avoid comparing oneself with one's batch mates, by being 'creative' with the definition/parameters of success, one can achieve a favorable result for oneself - in the comparison game. Unfortunately, the opposite is also true. One can also find ways to conclude that everyone else in the batch is more successful than himself/herself!

I also liked the mention in the book about being at the receiving end of an HR process (recruitment -in this case). I have found that 'being at the receiving end of HR' (experiencing an HR process as an employee, especially if it is a 'not so pleasant' experience) can be a great eye-opener for an HR professional. This helps one to be more sensitive to the 'human' in 'Human Resources'. While most of us have been employees also (in addition to having been HR professionals) for most part of our careers, we often have this strange tendency to discount our experiences as employees (as internal customers of HR strategies/ processes/ policies) as compared to our experiences as HR professionals (who design/run HR strategies/ processes/ policies).

The last point I want to talk about here is insight that the book provides about the 'increased cost' (human and social cost) of retrenchment in the Indian context. Since there is little or no social security provided by the state, the role of the employer/expectations from the employer in this domain get heightened. I would even say that since the joint family system (that used to provide some sort of insurance/social security) is breaking down, this aspect can become even more significant. Then there is this issue of 'family involvement'. Since many of us still have the tendency to 'get our families involved' in most of the important decisions that we take (like marriage and job!), separation from the job has an impact on the family that goes beyond the economic impact (as it can have impact on dimensions like family pride and even identity!). This also has implications for the 'innovative' employee engagement & employee retention strategies/ initiatives that many organizations are trying out these days - initiatives/strategies that try to 'lock in' the employees by actively involving their families (like parents day, get the families to the office etc.). Yes, these can help in reducing employee attrition/voluntary turnover. However, this would also make retrenchment/involuntary separation more difficult for the organization and more painful for employees (and their families).

Friday, October 24, 2008

In search of a 'sharp' employee value proposition

These days, many companies are quite vocal about their 'employee value proposition' - the 'total employee deal' that they offer. Some of them even have formal employee value proposition statements. Yes, this is a positive development. If organizations are serious about treating their employees as anything more than 'mindless resources' and if they acknowledge that the employees exercise at least some amount of choice (in matters like joining the company, staying on, putting in discretionary effort at work etc.) it make sense to think about (and more importantly, to do something about!) creating a value proposition (or a 'total employee deal') that appeals to the the current and prospective employees.

However, we often come across two types of problems with 'creating a compelling employee value proposition' efforts. The first is that the value proposition exists mainly in word and not in deed. Hence this becomes more of a communication (or 'public relations') exercise. Now this might work for sometime (in terms of increasing employee morale and in terms of attracting new hires) - as employees often believe the employers (or at least give them 'benefit of doubt'). But after some time, when the employees don't see much action (or the alleged 'employee value' in the employee value proposition) it leads to more frustration/ disillusionment/ mistrust. Thus the employees might develop some sort of aversion (or at least reduced sensitivity) to employee value proposition statements/initiatives.

The second problem is that the 'employee value proposition' statements of many of the organizations look very similar. Now if many organizations start speaking about very similar 'employee value propositions' it leads to a lot of clutter and hence the the employees, especially the prospective employees, find it difficult to judge the relative merits/demerits of the employee value propositions offered by various organizations. This can also add to the 'reduced sensitivity' to employee value proposition statements that we were discussing earlier.

In many cases, one of the key reasons for the above two problems is the attempt on part of the organization to do too many things - trying to improve all aspects/dimensions of the employee deal - that too for all the employees. While this ('trying to be everything to everybody' kind of approach) leads to 'well-rounded employee value proposition statements' the implementation/delivery of the employee value proposition becomes too difficult/impossible. When many organizations follow this approach this also results in employee value proposition statements that look very similar (and too good to be true!).

The above discussion implies that, to be effective, organizations need to find a way to cut through this clutter and reduced employee sensitivity - while ensuring that the employee value propositions are implementable. This where 'sharp' employee value propositions come in.

The basic requirement here is to create a very clear employee value proposition that is different from (and perceived to be different from) what other companies are offering. Usually this implies focusing narrowly – concentrating only on one or two levers/dimensions of the ‘total employee deal’. So the idea is to choose one (or two) aspects of the employee value proposition (based on the business and HR context/strategy/plan) and to channelize most of the resources to enhance ‘employee deal’ in those dimensions. For example, the value proposition can be that
  • ‘we are the best paymasters in the industry’ or
  • ‘we provide the fastest career growth in the industry/we offer positions at a higher responsibility level as compared to what the other companies offer for a given employee profile’ or
  • ‘we provide better/more stable long-term career and greater work-life balance’ or
  • ‘we provide greater opportunities for job rotation and the opportunities to work in multiple geographies’ or
  • ‘we provide the opportunity to work with the most advanced technology/tools and the chance to work with people who are considered to be the thought leaders in the field’ or
  • ‘we provide mass-career customization/greater flexibility in designing your own career’ etc.

Now, all of the above options listed above might not be feasible in the context of a particular company. However, some of the options might be very much feasible. Of course, having/developing competent managers and building a good work culture are very important – especially from a retention point of view. But since every company talks about these it becomes difficult to make these differentiating factors – when we are talking about attracting a new candidate/when a candidate has limited primary data points regarding what particular companies are really offering.

Once the organization has chosen the lever(s) to press and has enhanced the employee value proposition on that dimension (by modifying the policies/processes/management style etc.), the next step is to publicize it – both internally and externally. This will also ensure that the organization attracts the 'correct' profile of candidates (as the ‘focused’ employee value proposition will appeal to only a particular set of candidates – candidates who have a set of workplace preferences that is similar to what the organization is highlighting). While this might reduce the size of the ‘candidate pool’, it will help the organization greatly in reducing attrition – as the organization is attracting only those people who are motivated by those aspects of employee value proposition that the organization is providing better than what the other companies are doing.

It is also possible to further customize ('sharpen'!!!) the employee value proposition to make it more attractive to particular employee segments (e.g. high performance – high potential employees, employees in certain jobs, employees with certain skills etc). This makes a lot of sense if the organization has very limited resources and if it doesn't have equal need to retain all segments of the employees.

Any comments/observations/suggestions?

Sunday, July 13, 2008

Influence of 'early career experiences'

What has been the impact of your 'early-career experiences' on you? For the purpose of this discussion, let us define 'early-career experiences' as 'experiences during the 'most impressionable part' of one's career and this would imply (for many people) experiences during the first few years of one's career/the experiences during one's first job. So please take a couple of minutes to think about your 'early-career experiences'. What do you remember about them? Do you think that they have impacted you in any significant manner? If yes, what has been the nature of the impact?

The importance of early life experiences on the psychological/behavioral development of a person is well known. But considering that one is usually much older when one starts working, can a similar phenomena occur - in the domain of one's basic assumptions about organizational life/work/career? In an earlier post (see HR professionals and Multiple Personality Disorder), I had speculated that 'traumatic' early career experiences might contribute to the development of some sort of a 'Multiple Personality Disorder' among HR professionals - especially among young MBAs in HR.

While I have been thinking about this issue for quite some time, the 'trigger' for this post came recently in the form of a discussion in an e-group that I am part of. This e-group consists mainly of my ex-colleagues from an organization in which I had worked a long time ago. We were discussing issues like"the reasons for the existence of strong bonds among us even though most of us had left the organization a long time ago"; "why do we often talk about the 'great experience' that we have had in that organization" etc. Now, there were multiple factors (at multiple) levels involved in the situation. I felt that one of the key factors involved (apart from the factors related to the organization context, nature of work, nature of inter-dependencies in the group etc.) was the profile of the members of the group/organization at that stage - most of us were at an 'impressionable stage' in our careers!.

It was the first job for many of us and I felt that it 'shaped' our definitions of 'what is good' in an organization/workplace context (i.e. the tacit/subconscious definitions of 'good' boss, 'good' team member, 'good' team, 'good' employer, 'good' learning opportunities and even that of 'good' work). Since other organizations (that we joined later in our career) are unlikely to provide environments that exactly match these definitions, the work experiences in them are likely to be perceived as falling short of 'the good old days'. I think that this is similar to the phenomena in which the traditional way of cooking in India (cooking with fire/heating food from the outside) influenced our definition of 'good taste'. This in turn made it difficult for a product like the microwave oven (that heat up food uniformly) to become popular in India* (other than for reheating the food) - till a new generation brought up on a more 'microwave-friendly' definition of 'good taste' became consumers.

So my hypothesis is that early career experiences can have a significant impact on our careers by influencing our basic workplace preferences and attitudes. Of course, there are other factors (like personality related factors) that can also influence our workplace preferences and attitudes. It would also be interesting to examine if the impact/influence of early career experiences reduces as one progresses in one's career (and gains more experiences/data points).

Any observations/comments?

*Note: I am not saying that this is the only factor that possibly worked against the popularity of microwave ovens. There could be many other contributing factors. For example, from a psychological point of view - fire has many important associations (i.e. fire symbolizes a number of things). It is a symbol of purity - for fire is considered to purify everything. Hence cooking food in fire can symbolize purification of food. Fire is also supposed to symbolize 'illumination', 'inner light' , 'holiness' etc.. It is interesting to note that in many of the cultures across the world there are myths related to 'theft of fire' (e.g. according to Greek mythology, Prometheus [whose name means 'foresight'] stole fire [which was available only to the gods at that time] from Zeus and gave it to the mankind). As I have said earlier (please see Myth and truth : 'So true that it can't be real'), myths often embody great truths.

Now let us come back to microwave ovens. From the above discussion, it can be seen that 'microwave-cooking' might have been at a disadvantage as compared to 'fire-cooking' because of the symbolic significance of fire. This argument becomes stronger if we compare microwave ovens to washing machines. As compared to microwave ovens, washing machines became popular in India much faster. One of the reasons for this could be that a washing machine is a more or less 'straight forward automation of an essentially mechanical process' (i.e. washing). So washing machines did not have to fight some of the above 'psychological battles' that microwave ovens had to fight! Anyway, since I am not an expert in marketing (or in microwave ovens/washing machines for that matter) let me not push this point any further !

Sunday, June 29, 2008

In praise of HR generalists

Let me begin by saying that I am a specialist - I am in a specialist role now (in Learning and OD) and I have spent most of my career so far in specialist roles in HR. But I have also handled HR generalist/HR business partner roles where I was the 'internal customer' for specialists roles in HR. Again, I have been fortunate to get opportunities to work in the HR domain in multiple contexts - HR consulting, Internal HR and HR Shared Services Centre. At this point, I am very happy to be back in a specialist role. But I have much higher appreciation/ respect for HR generalists now - as compared to what I used to have during the early years of my career.

Earlier (when I was looking at HR generalist roles as an outsider), I used to consider most of the HR generalist roles to be rather 'shallow' - in the sense that most of those roles (when it comes to the way they are actually executed) don't require any significant application of HR/behavioral science knowledge (please see HR Professionals and Multiple Personality Disorder). The main requirement for those roles seemed to be 'a bit of common sense coupled with knowledge of procedures/policies'.

Now that I have closely worked with some very effective HR generalists (and also seen generalist roles from an 'insider perspective'), I am convinced that what appears to be straight forward common sense decision making often involves fine judgement - the kind of judgement that requires knowledge and much more than knowledge - often requiring the kind of 'wisdom' that I spoke about in 'Wisdom-level consulting'. Since HR generalists need to interface with employees & managers, they need to ensure that what they do/the decisions they are communicating appear simple, clear and consistent. But these simple 'front-end/user interface' is often achieved by absorbing a lot of complexity at the 'back-end' of decision making - and you have to be an insider to see/appreciate this 'back-end' of decision making!

I have seen many senior HR generalists do the kind of great process facilitation/ process consulting work with business leadership teams that would make an Organization Development (OD) specialist proud. But usually these HR leaders don't call it OD and they don't talk too much about it - may be because they see it as a very natural part of their job and may be because they don't want to annoy the 'designated OD specialists' in the organization! I have also seen these leaders being able to synthesize the inputs from multiple specialists (staffing, compensation, resource management, workforce planning, employee relations, capability development etc.) and provide the the business leaders with an integrated HR response (diagnosis and solutions) to business challenges.

This ismuch more useful for the business leaders than receiving separate recommendations from various specialists. I feel that integrating multiple perspectives and answering the 'so what' question for the business is a much higher craft than coming up with isolated findings. Again, some of these HR leaders have a much higher understanding of the business as compared to that of the specialists and they are able to look at the organization from a 'total system perspective' - to identify and exploit 'leverage points' - those points/areas/factors in the system where a small change made can have a huge impact on the overall system/business.

Another reason for my increased respect for HR generalists is a gradual shift in my definition of 'what really makes a difference'. These days, I am more inclined to think that unless what an HR professional does makes a difference at the level of individuals, it is not making much of a difference. Of course, I agree that often a system level intervention is needed to impact a large number of individuals and that the definition of individuals is not limited to particular employees. But I have seen that technically perfect work (or 'high-end HR work') done at the system level does not always translate into making a difference at the individual level (to the individual stakeholders).

From a diagnosis and solution design point of view, it is required to go beyond the immediate appearance of people related problems/issues and look at the 'underlying form/patterns/principles'. But, we need to ensure that these solutions designed at the 'pattern/underlying form/principle/theory' level, need to be converted back to the level of individuals - solutions to the actual problems/issues that we had started our analysis with.

This is similar to the 'physical problem-mathematical model of the problem-mathematical solution-physical solution' process used in approaches like Six Sigma. Since specialists work mostly at the pattern/principles/system level (similar to the mathematical/'ethereal' part mentioned above), generalists are required to bring the solutions to the ground level - to make them 'real' - as solutions to the actual problems of particular individuals.

Specialists enjoy an advantage over the generalists - specialists usually support more than one client group, where as the generalists are often embedded in a particular client group. So it becomes relatively easy for a specialist to take a objective/neutral perspective as compared to a generalist. Thus balancing the interests of the particular client group that one is supporting with that of the larger organization becomes a more difficult task for the generalists.

There is another tricky balancing act that HR generalists (especially at senior levels) often have to do. Many of these generalists have a good amount of specialist functional expertise and there is one part in their personality that craves for technical perfection of the solutions. But their roles demand that the solutions should be pragmatic/workable/easy to communicate and implement - keeping in mind the organizational constraints. Also, because of their greater proximity to the particular businesses they are supporting, HR generalists are much more aware of the organizational constraints (especially the tacit ones) as compared to specialists.

This leads to an interesting situation when these generalists are the internal customers of specialists roles in HR. When the specialists push for technical perfection of a solution, the generalists often have to push back - to keep the solutions implementable. This would mean that in addition to arguing with the specialists, they also have to argue with themselves (i.e. the specialist part of their personality). Believe me, this is not a very enjoyable situation to be in! Of course, specialists also face these kind of issues as they grow in their careers. Please see 'Of specialists and business alignment'.

Overall, I feel that HR generalists roles are more 'messy' as compared to specialist roles. Often, HR generalists have to act as the 'face of the organization' when it comes to communicating unpleasant decisions (like disciplinary actions, layoffs, reduction in employee benefits etc.) to the employees. It becomes a challenge to maintain integrity (at the intrapersonal and at the interpersonal levels) when an HR generalist has to to stand in front of the same group employees -within the short span of time - first to announce employee engagement initiatives and then to announce a layoff.

As I have mentioned earlier (Please see 'At the receiving end of change management'), even in the case of major changes in the organization that have significant impact on the organization structure, jobs and on the employees, often the HR generalists are able to get involved only when it is too late. By that time 'emotional wounds' have already been created and what is left is more of communication and 'dressing of wounds'. This is definitely not the 'strategic change management' role that they were supposed to do. Now, I am not saying that these 'organizational scavenger' (or 'organizational earthworm') kind of roles played by HR generalists are not important. Actually they are very critical for maintaining the health and vitality of the organizations (just like earthworms increase the vitality of the soil/scavengers help to maintain the health of the ecosystem). My point is that these aspects of HR generalist roles are often very messy.

Again, since HR generalists often have to respond quickly there might not be enough time to come up with neat solutions. The specialists also have their own battles to fight in organizations and there is always the risk of 'injuries'(Since these are 'organization battles', these injuries are unlikely to be physical in nature - but they can really hurt. Please see 'Leaders and battle scars' for a related discussion.). The 'injuries' sustained in 'specialist battles' are more likely to be similar to 'cuts' , whereas those sustained in 'generalist battles' are more likely to resemble 'wounds'. It is important to note that here we are talking not just about the 'injuries' sustained by HR specialists/generalists. We are also talking about the 'injuries' to the other players in the organization and to the relationships - the relationships between HR professionals and business leaders/managers that are very important (especially for the HR generalists) to get their work done! In general, 'cuts' tend to heal faster (and neater/with less scarring !) than 'wounds' !

Another factor here is that the boundaries of generalist roles are often not well-defined and hence all kinds of tasks/problems (especially those no one wants to touch) can get dumped on the generalists. In some contexts this can also imply that HR generalists are 'on call' 24x7. Work can become a series of small activities with nothing substantial to show (or to add to the CV !) at the end of the year. Again, there is the greater need to walk the thin line between confidentiality and openness, empathy and objectivity, cooperation and capitulation, emotional intelligence and emotional manipulation etc. One can even end up feeling like a 'mouse in a maze' - running here and there, feeling extremely busy- but not reaching anywhere! Now, what amazes me is that I have seen many HR generalists being effective and producing very 'neat' work in such a 'messy' situation. So how can I stop myself from writing this post - 'in praise of HR generalists'?

Any comments/observations?

Saturday, May 31, 2008

Job and identity

Recently, I left the job that I had been doing for the past three years and took up a different type of job with another organization. I also got the opportunity to take a 3-week break in between - the first in my career that I have done so. I spent most of this time outside Bangalore - with some of my close relatives. This also meant that I met a lot people (the friends/relatives of my relatives) - and I was meeting most of them for the first time. One side effect of this was that I had to answer the question "So Prasad, what are you doing now?" - roughly 3 times/day - about 40 times in total, over a two week period.

Initially, I tried the answer "I am on vacation" - but that did not seem to work. People would wait for me to say more and if I did not say anything more they would ask me something like "What do you do for a living?". To this I tried to give the answer "I work mainly in the area of Organization Development". But even that answer did not seem satisfactory. Sooner or later people would ask me "Which company do you work for?". To this I tried answering "I am in between jobs" (or "I am taking a break") - but this also did not appear to work well (and sometimes this answer elicited a confused and/or sympathetic look/expression also). So finally I was forced to answer "I was working for company 'C1' till date ' d1' and I would be joining company 'C2' on date 'd2' ". While this turned out to be 'satisfactory answer' (from a social perspective), I did feel quite uneasy.

My uneasiness was mainly at two levels. At the 'social level' I was bothered about how would I have handled this question if I was not in a position to say that "I would be joining company 'C2' on date 'd2' ". At more personal level, I was wondering whether I can articulate a clear answer (just for my own consumption) to our initial question ("So Prasad, what are you doing now ?"), without referring to any of my employers (past, present or future!) or to the job titles. After I thought about it for a while, I felt that uneasiness at the first level was not a very important - as it was arising mainly from 'social desirability' and 'norms of polite communication in a particular social group' - and hence it should not bother one unduly so long as the 'economic viability' angle has been taken care of. The uneasiness at the personal level was more difficult to address. Once I resisted the temptation to 'destroy the question' by resorting to philosophical answers (e.g. one should be bothered about 'being' as opposed to 'doing'), the real issue became "Have I wrapped my identity too much into my job/career ?". I feel that this is an important question that needs to be looked at more carefully.

There are conflicting trends operating here. On the one hand, many of us spend a very large part of our waking lives at work. Many of the jobs are very demanding and they occupy a lot of our 'psychological space' - much beyond office space and office hours. Our 'passion for work', might make work and the achievements at the workplace very important for us. It has also been argued that in an environment where the role holder has the opportunity to shape the role to a large extent (and/or where people are expected to be responsible for managing/developing their careers), role identity and career identity are essential for success/effectiveness. On the other hand, these days many people routinely change jobs or even change careers. Again, often people are forced out of their jobs and careers by organizational changes(right sizing, restructuring etc.). Thus, if your identity is wrapped up in what you do, a change of job or a change of careers (especially if they were forced on you) becomes traumatic (much more so in the case of a job loss).

So where does this leave us? Developing and understanding our identity as individuals is essential for personal effectiveness. This would serve an anchor point for us when everything around us are changing. While job and career identities are useful from a job/career effectiveness/success point of view, they can't define who we are as individuals. Jobs and careers are like the cloths that individuals wear and change. Just as we can't let our cloths define us (though some of us might choose to express some aspects of ourselves through the way we dress), we can't let our jobs and careers define us completely. So it is very important for one to examine one's current definition of oneself and if the results don't show anything beyond job and career identity, it is time for investing significant time and effort for expanding the boundaries of those definitions. Of course, developing and understanding our identity as individuals is a lifelong process.

By the way, there is another reason for being careful about this 'sense of identity wrapped up in job' . It has been argued that 'sense of identity wrapped up in job' is one of the factors that could predict the risk of violent behavior at the workplace. So now the relevant questions are - "Are you at risk ?" and "Are you a risk ?" !!!

Related Link: HR carnival at Strategic HCM blog