Showing posts with label Problem solving. Show all posts
Showing posts with label Problem solving. Show all posts

Saturday, September 4, 2010

Renewable resources for thought leadership in HR

About 3 years ago, I wrote a post in this blog on “Thought leadership in HR in India” – based on an informal survey that I had conducted at that time. While the post mentioned that there does not seem to be consensus on the names of thought leaders in HR in India, it ended with a rather positive inference (especially for the people who want be thought leaders) that “There are a wide range of definitions of thought leadership. It seems that there is room for many types of 'thought leadership' and for many types of thought leaders in HR! This gives many of us a chance to become some sort of 'thought leaders' (or at least to 'call ourselves thought leaders’!) in some HR related domain, in some industry, at some point in our careers”. That post also raised an important ‘philosophical’ question - “Can leadership (including thought leadership) exist without followers?”

The objective of this post is to outline how my thoughts on some of the aspects covered in the previous post have evolved during the last three years. I hope that my thinking on this topic will continue to evolve (and that I will be writing another post 3 years from now).

At this point, what interests me more is the ‘nature of thought leadership’ in HR as opposed to the names of thought leaders in HR. Obviously, these two are not unrelated. A particular interpretation of the nature of thought leadership in HR will result in a particular list of thought leaders and vice versa.

Let us start by taking a closer look at the ‘philosophical’ question that was mentioned above - “Can leadership (including thought leadership) exist without followers?” This will depend on the definition of leadership. My preference these days is to think about leadership as an emergent phenomenon that takes place in the context of a relationship (or in the context of a set of interactions – face to face and/or virtual – including indirect interactions). Going by this definition, leadership can’t exist without followers*. So the focus of this post is on thought leadership in HR that others (e.g. fellow HR professionals, Business Managers etc.) find useful.

From this perspective, thought leadership in HR has to deal with key challenges and opportunities related to people management. It also has to focus on those aspects where others (potential followers) feel the need for such thought leadership. Hence ‘core’ ‘messy’ areas in HR – where standard/algorithmic solutions are not feasible - are good candidates as domains for thought leadership. Often, this path can lead to the key ‘Paradoxes in HR’ that we have discussed often in this blog (see here, here, here, here and here for some examples).

Attempting ‘thought leadership’ in these areas related to Paradoxes in HR has interesting implications for the nature of thought leadership. As mentioned above, it won’t be feasible to prescribe effective standard/algorithmic solutions (that can apply to a wide range of contexts) in these areas. The kind of thought leadership that is likely to be useful here will be more in terms of providing a new perspective, deepening the richness & understanding of the paradox, providing an experience that provides company (‘provide a feeling of being understood’/ demonstrate compassion) hope and amusement to the people grappling with the paradox etc. It can also be inferred that this kind of thought leadership need not necessarily involve providing any sort of 'answers' - it can exist purely in the form of providing questions - questions that would help others to see the problem/paradox in a new way - which in turn could enhance their understanding and trigger solutions in their mind. Thus, the purpose of thought leadership in these cases will be to trigger solutions in the mind of people dealing with the paradoxes as opposed to prescribing solutions directly. Since these questions are about the essential nature of the issues involved, they might sound like riddles (or even like koans in Zen) that can be solved only by struggling with the same for an extended period of time to reach a level of understanding/awareness where the solution presents itself.

Obviously, this creates difficulties in terms of mass-production and marketing. But there is also an advantage here. The basic paradoxes in HR (and hence the pains/problems created by them) are unlikely to be ‘resolved’ (in terms of having a final and permanent solution). With effective thought and action (possibly aided by thought leadership!) they can be ‘managed’ (if we use the term 'manage' to mean ‘to cope with’) and even celebrated. But these paradoxes/problems/ needs won’t go away. Thus, these are the ‘renewable resources for thought leadership in HR’ – where solutions to problems will create new problems to solve -that will continue to provide opportunities for thought leadership – that will sustain an entire ecosystem of ‘HR Managers, Consultants and Thought Leaders’ - for a long time!**

Now over to you for your comments/thoughts/ideas!

* Note 1: Technically speaking, this does not preclude the possibility of ‘self-leadership’ as ‘interactions with self’ can also be interpreted as interactions. Moreover, the question “Will I follow my own advice if it came from someone else?” can serve as a useful reality check – to guard against some types of ‘delusion’ that can affect some of the thought leaders.

**Note 2: I feel that these paradoxes/problems won’t go away in the foreseeable future as these arise directly from the very nature of people management as it is practiced today. Hence, unless there is a fundamental change in the nature and philosophy of people management, they will continue to exist.

Tuesday, January 8, 2008

Paradox of 'HR Systems'

"But I don't need HR systems", said the senior business manager. I had gone to this gentleman to seek his buy-in (and sponsorship, if possible) for implementing an internal HR product/ solution that I was managing at that time. The main selling point for the HR product was that it would improve the effectiveness of core HR systems in the organization (like Staffing, Rewards and Training). I had just finished my sales pitch and then I was hit with this response. Actually, he was not being difficult. He had a point. This gentleman was managing one of the most profitable units in the organization. This unit had a relatively small number (as compared to the total headcount in the organization) of employees - but with a highly specialized (and difficult to find/retain) skill set. His point was that because of the nature of the skill set and high business impact of the positions in his unit, key people related decisions (hiring, rewarding, training etc.) are directly handled by him and his direct reports in a highly individualized manner and this has been working very well. So any (standardized) HR system/process would be more of a hindrance for him in running his unit !

While the above scenario is not representative of the typical organization context in which HR systems function, it brings us to an interesting paradox in 'Human Resource Systems/ Processes'. There is a clue in the name itself. The words 'system' or 'process' convey an impression of standardization/ consistency. The word 'human' implies a unique individual. As I have mentioned earlier (while discussing the various terms used for HRM), the new business environment has forced organizations to pay more attention to the 'human' part (as opposed to the 'resource' part) of 'human resource management'. This has resulted in a quest for more individualized approaches for managing people (See here for an example in the domain of career development. Another example could be the shift/progression from 'level/grade-based' to 'position-based'' to profile-based' to 'individual-based' approach in compensation and benefits management.). Now the question is that "how can standardized processes/systems be effective in managing unique individuals?" But we can't jump to the conclusion that HR systems/ processes are not required. Absolute chaos can result if there are no HR systems/processes - especially in the case of large organizations. Moreover, how can we forget what we have learned about 'procedural justice' ! However, it has also been established that human beings are managed most effectively in small units. This again brings us back to the importance of customised approaches to managing people - at individual and small group levels - even as many organizations are becoming larger in size. Thus we have a paradox in the true meaning of the term - multiple perspectives/opinions (doxa) that exist alongside (para)- each of which is true - but they appear to contradict/to be in conflict with one another.

One 'solution' that has evolved/emerged in response to this paradox (which is often seen in MNCs) is to establish well-defined processes across the organization and also to give a lot of decision making power to the managers. For example, the process (steps/procedure) for giving a salary increase (or a promotion) would be very clearly defined; but the manager has absolute freedom to decide on the quantum of salary increase for a particular employee (or to decide whether or not to promote a particular employee) subject to an overall salary increase/ cost of workforce budget for the entire team. Thus, highly individualized approach can be taken for managing a particular employee while maintaining standardization at the group level.

People management is a field which is full of paradoxes (for more examples of such paradoxes please see paradox of 'hiring good people and letting them decide' and paradox of potential assessment). . The 'human' dimension of the issues in this domain is one of the main contributing factors. Also, any system (including a human system), when it becomes sufficiently complex, becomes difficult to 'manage' in the normal sense of the term 'manage'. As I have mentioned earlier (while exploring the behavioral science foundations of HR), a key prerequisite for managing is the ability to predict. In the case of complex systems, we face a dilemma - predictions about the behavior of the system that can be made accurately are not very relevant/helpful in managing the system and predictions that are relevant/helpful in managing the system can't be made very accurately ! However, a paradox per se is not a bad thing. If there were neat/linear solutions to problems in people management there wouldn't have been many deep-specialist jobs in HR (which in turn would have forced many of us to look for jobs in other domains !). Paradoxes also contribute to the richness of the domain. However, managing paradoxes might require approaches that are different from traditional problem solving methods. They might need approaches similar to those that I have described in posts like 'Making problems disappear' , 'Wisdom-level consulting' and 'Of problems, paradoxes, koans and wisdom' - approaches that reflect simplicity at the other side of complexity !

Any ideas/comments?

Related posts : See here and here for related posts.

Monday, May 7, 2007

Of problems, paradoxes, koans and wisdom

This post was triggered by a comment on one of my previous posts (see making problems disappear ). The comment also contained a request that I discuss 'other problem solving methods that I know'. I must admit that while I do have a basic understanding about the problem solving methods (that can be used to solve the problems that can be solved in the usual meaning of the term 'solve'), I don't really have any thing special to say on that matter at this point. So what I am trying to do in this post is to talk about a couple of ideas related to problems and problem solving and link them to the basic theme for this blog - 'simplicity at the other side of complexity'.

A few months ago, I had written a post called U-curve and simplicity at the other side of complexity which mentioned that many phenomena follow a pattern that resembles a 'U' - shaped curve over a period of time. They start in one state (i.e. in a particular manner), then move towards the other end (i.e. the opposite manner/state) and then they come back to the original state at a higher level/plane. I feel that something similar might be involved in the case of many of the complex problems. It works something like this. The first stage is when one does not recognise that a problem exists. Here one does not (have to) do anything/exists in blissful ignorance. In the next stage the pendulum swings to the other side and the existence of the problem is recognised. This is also accompanied by a powerful desire (bordering on compulsion) to find a neat solution to the problem immediately. In the case of complex problems often these attempts to find a neat solution fails and this makes the pendulum swing to the other side. In this phase, the existence of a paradox (and not just a problem) is recognised and the nature of attempts to resolve the problem shifts from traditional problem solving to methods similar to making problems disappear. It is interesting to note that one of the definitions of wisdom is 'the understanding of paradoxes'. This in turn leads to approaches like wisdom-level consulting.

I have always been fascinated by Zen- especially the koans in Zen. Initially, I used to think of koans just as 'impossible problems' that are used to break the logical mind. Only recently I came to know that each koan has a more or less unique solution. The critical point here is that these 'solutions' make sense only at a particular state of awareness, which is reached by working on the koan for a long time. Of course, in this context, what is important is the 'achievement of the particular state of awareness' and not the koan or it solution per se.

Thursday, January 4, 2007

U-curve and simplicity at the other side of complexity

A few years ago I came across the concept of a 'U - curve' in anthropology. The basic idea is something like this: Many phenomena follow a pattern that resembles a 'U' - shaped curve over a period of time. They start in one state (i.e. in a particular manner/fashion), then gradually move towards the other end (i.e. the opposite manner/fashion/state) and then they come back to the original state at a higher level/plane. For example, early humans were naked because they did not have any cloths. Then, over a large span of time, humans moved to the other extreme of very elaborate clothing. Over a period of time this in turn has changed to the recent tendency to wear less cloths. Now if we look only at the outward appearance, the third state looks similar to the first state(wearing less cloths). But the third state is, in essence, very much different from the first state because in third state 'wearing less cloths' is a matter of choice which was not the case in the first state.

I remembered this concept while I was thinking about 'simplicity at the other side of complexity' which is the theme for this post(and in a broad sense the theme for this blog). In the case of complex non-linear systems (most of the human systems and business contexts are likely to fall in this category) there is simplicity at both sides of the complexity. Of course the apparent/obvious simplicity is 'simplistic' and it often comes out of the inability and/or unwillingness to appreciate the complexity. This leads to quick-fix solutions and fads (which essentially say "follow these 'x' steps to arrive at the solution") that do not really work in the long term.

However there is a simplicity that is achieved after working through the complexity. This simplicity is at the level of patterns underlying complexity. These patterns can be used to manage the complexity effectively. However there are two difficulties:
(1) One has to work through the complexity to uncover these patterns
(2) These patterns lead to 'directionally correct steps' and not to instant solutions
But these difficulties are the dues we have to pay for operating effectively in a complex world. While we can learn/benefit from the patterns discovered by others, often we have to 'rediscover' the patterns ourselves to fully understand/appreciate the patterns. The dynamic nature of the situation and hence the patterns makes it necessity to learn the patterns through personal experience (often the 'hard way'). The novel 'Siddhartha' by Herman Hesse provides a beautiful illustration of this point.

Related Link : See here for more discussion on this topic.

Wednesday, December 20, 2006

Making problems disappear

Problem solving is the central activity of business and life. If we look at the behavioral training catalog/calender of any organization we are highly likely to find at least one course on problem solving. While I fully agree with the importance of developing problem solving skills, I feel that there are 'many levels of problems and problem solving' and that the traditional problem solving techniques/approaches are suitable for addressing only one type (level) of problems. These are problems that are resolved best by solving them (in the normal meaning of the word 'solving').

But there are some other problems (at a different level) that are resolved best not by solving them but by 'swamping them' (e.g. by putting them in the larger perspective of time, situation etc.), 'evaporating them' (e.g. by reducing the criticality/relevance) or even by 'making them disappear'.

This post deals with the third category(problems that are best resolved by making them disappear). While the details of this approach would require much longer/ more extensive treatment than what I plan to discuss here the essential idea is that this kind of problems are resolved by grappling/struggling with the problem unsuccessfully (over a significant period of time, somewhat similar to working on a Zen 'koan') and from that struggle developing/reaching a level of awareness which would make the problem disappear. Without getting into the details, let me tell a small story that illustrates this(although in a simplified manner).

While I was studying at XLRI for my MBA there was an elective on 'Management of Relationships(Applied Psychoanalysis)'. As part of that course we were given many case studies(actually these cases were highly sought after by those students who did not take that elective - because of the 'porn' value of psychoanalysis cases).

One of the case studies dealt with a woman who exhibited a 'strange' pattern of behavior. In some situations she behaved in a virtuous way and in some other situations she behaved in an immoral way. We were split into sub-groups and the task given to us was to make a presentation(in 45 minutes) on whether she was a 'Devi' (a goddess) or a 'Vesya' (a prostitute). Naturally, this kind of a discussion is unlikely to reach any conclusion - with some members arguing for one position and the others for the opposite position. While most of us were enjoying the discussion one of my friends (who was the most sincere and result oriented among us) was getting increasingly uneasy because we were nearing the time limit set by the professor while being nowhere near any consensus/agreement on the answer to the question posed to us. Finally he could take it no more and he said "OK, OK let us agree that she is 70% Devi and 30% Vesya". While there was some 'logical' merit in this solution' (i.e. if one were to analyze each of the incidents given in the case, one will find that in most of the incidents she behaved in a virtuous manner), in a way it completely missed the point. The 'real' purpose (though it was not stated explicitly) for giving us the case was not to solve it. The purpose was to develop our awareness of the paradoxical nature of the issue (and also to be aware of the tendency/compulsion of Indians to classify a woman either as a Devi or as a Vesya). So the solution was to grapple with the problem unsuccessfully and from that struggle develop/reach a level of awareness which would make the problem disappear.

Related Link : For further discussion on the topic, see here