Of Espoused Competencies, Enacted Competencies and Janus-faced Leaders

"All models are wrong, but some are useful!"

We often talk about espoused values (professed/stated values of the organization), enacted values (the values the organization actually lives by) and the ‘cognitive dissonance’ that the employees/stakeholders experience because of the difference between the two (Please see ’Of espoused values and enacted values’ for more). A similar point can be made in the case of leadership competency frameworks also.

Most of the companies have leadership competency frameworks. They are supposed to outline the competencies that will make one successful as a leader in the organization (see 'Of competencies and carbohydrates' for more on competencies). They also serve as the basis for leadership development, leadership hiring, leadership succession and performance management for leaders. 

The above mentioned ‘cognitive dissonance’ occurs here also when one compares the ‘demonstrated/enacted competencies’ of the successful leaders in the organization (what is actually required to be successful as a leader in the organization) with the competencies mentioned in the leadership competency framework (the stated competencies) and find that there are significant differences between the two. 

In addition to causing confusion, this also implies that leadership hiring, leadership development, leadership succession, performance management for leaders etc. are being done based on wrong assumptions. This can adversely affect organization effectiveness, apart from wasting time and money and causing avoidable human suffering in organizations. Therefore, we need to look into this in a bit more detail.

Organizations meticulously craft leadership competency frameworks that delineate the behaviors considered vital for a leader’s success in the organization. These frameworks are replete with ideals such as integrity, communication, strategic thinking, and empathy. However, beyond these polished documents, lies an unspoken truth: leaders who are most 'successful' in the organization (as indicated by rewards and career growth) often exhibit traits that are sometimes contrary to these prescribed competencies. This situation can arise from problems in the approach used to arrive at the leadership competency model. For example, the leadership competency model might have been created based on a 'wish list' of competencies as opposed to developing it through on a structured competency mapping exercise based on the actual leadership behaviors and their degree of success in the organization. This can make the leadership competency framework more of a 'convenient collective delusion'.   

Now let's come to the leaders who are very successful in the organization, without demonstrating most the competencies outlined in the leadership competency model. One interesting category among these leaders are the 'Janus-faced leaders' – those who embody dichotomies in their leadership styles and are rewarded for it. These kinds of leaders are most commonly found in hierarchical organizations. Janus, the Roman god with two faces, one looking to the future and one to the past, provides a fitting metaphor for this kind of leadership. In modern terms, Janus-faced leaders adeptly navigate upward and downward relationships in dramatically different manners. They may present a facade of deference and subservience to their superiors while simultaneously displaying a demanding and exacting approach to their own teams (please see 'Followership behaviors of leaders' for more)

These leaders are often perceived as highly effective by their superiors because they create the impression that they are ‘squeezing out maximum performance from their team’ and because they shield upper management from unpleasant realities of organization life. They are also amazingly good in taking credit when something good happens and blaming their team (or restructuring their team) when something goes wrong. Of course, this comes at the cost of team morale and trust. However, if the Janus-faced leader is able to create the impression that the team is not competent and are being to deliver only because of the ‘tough love’ of the leader, this might not matter to the senior leadership.

Another unacknowledged 'competency' that often characterizes successful leaders is the ability to "suffer in silence". Leaders are expected to bear the weight of responsibility without complaint, to absorb the pressures of high-stakes decision-making, and to manage their own stress without it spilling over onto their teams or affecting their performance. This stoic disposition is seldom featured in leadership models, but it is an unspoken expectation and a reality for many at the top. This can lead to emotional labor and even to 'smiling depression' among the leaders. 

The irony here is not that these unspoken competencies exist, but rather that organizations continue to espouse frameworks that do not fully capture the reality of leadership success. There is a need for a more holistic and perhaps more candid conversation about what effective leadership really entails – including both the noble and the ignoble traits (the bright and the dark sides of leadership).

Having highlighted this, let’s look at a couple of counter arguments. It can be argued that that the competencies mentioned in the framework are aspirational/futuristic – competencies required to be successful as a leader in the future. This is sort of ‘what got you here won’t get you there’ kind of argument. The problem happens when the ‘future’ never arrives!  Another counter argument is that we shouldn’t reinforce negative aspects of successful leadership in the organization, by highlighting them (or 'institutionalizing them' by including them in the leadership competency framework). This definitely has merit. The problem is just that by pushing these negative aspects of successful leaders under the carpet, we reduce the chance that they will ever be addressed! Of course, this requires a deep and often tricky intervention to address (See 'Organization Development Managers as Court Jesters' for an approach that might be helpful in this context).

It is time for organizations to reflect on the complexity of leadership and recognize that the sanitized version presented in competency frameworks is often at odds with the less savory – yet effective – traits and behaviors that contribute to a leader’s success. Until we can openly discuss and integrate these aspects, we will continue to hire/ prepare leaders for an idealized world that is far removed from the one they actually inhabit.

 Any comments?

Defense against the ‘Dark Arts’ of Job Evaluation: A Crash Course!

Let me start with a confession. I have made a living out of job evaluation – both as an external consultant (who conducts job evaluation and trains/certifies the client team on job evaluation) and as an internal process owner. I have had the opportunity to get trained/certified in three different job evaluation methodologies and practice two of them extensively. Job Evaluation can be a very useful tool to establish the relative size of jobs in a systematic manner and this can serve as an input to various processes like organization design, job banding, rewards, career pathing, talent movements etc.

Now, the question is “why would anyone need to defend against such a useful thing?”. It is because job evaluation requires the investment of time and money and because one can be at the ‘receiving end’ of job evaluation as a Business Leader, HR Business Partner, People Manager or as an employee – when job evaluation becomes more of a hassle than a help. For a Business Leader who values flexibility job evaluation can comes an unnecessary hurdle to pass (See Paradox of HR Systems for a related discussion). In such a case, the business leader might just take a decision on the grade fitment of an employee and ask the HR Business Partner to ‘push it through the HR system’ somehow. Similarly, for a manager (who is trying to keep an employee motivated by providing vertical career growth) or for an employee (who looking for a promotion), job evaluation can become a serious impediment to what one wants to achieve.

Job evaluation is not an exact science. While the job evaluation providers might claim that their methodology has been successfully applied across countries and industry sectors, it is indeed possible that a particular methodology (especially one with fixed factors and factor weightages - most of the popular job evaluation methodologies fall into this category) favors certain types of jobs. This can lead to situations where the job evaluation scores don't accurately reflect the contribution various jobs make to a particular organization. It has been argued that job evaluation is a 'rationalized institutional myth' - 'rationalized' because it has a clearly articulated methodology and a 'myth' because it is accepted as true because it is believed.

Job evaluation involves a significant amount of judgement (which can be subjective, even when guided by a well-defined framework and quality checks). In a way, job evaluation is more of a ‘negotiated agreement’. In such a situation, if one doesn’t have political power, one might be at a significant disadvantage as compared to people who have such power. In extreme circumstances, job evaluation can become a tool for ‘powerplay’. Yes, there are also situations where the job evaluation process owner gets a bad name even when he/she hasn’t done anything wrong.

So, what are some of the options for defending against job evaluation? The following discussion can give you some ideas.

Avoid it if possible

Job Evaluation takes significant time and resources. Job Evaluation makes practical sense only if the jobs are relatively stable. So, if the jobs in your unit haven’t yet stabilized, you have a good case for arguing that job evaluation shouldn’t be applied to your unit at this stage. A similar argument can be made if your operating strategy involves recasting jobs frequently (requiring frequent reevaluation of jobs which can be expensive and time consuming). Also, if job evaluation is not very commonly used by the companies in your industry segment, that can give you a good argument against the applicability of job evaluation.

 There are indeed ways to implement job evaluation in the above-mentioned contexts. It is just that it is a bit more difficult to do so and that the case is less compelling.

Create a lot of exceptions when you can

Here the idea is to be a bit generous with the grade-fitment of the employees before job evaluation becomes applicable to your unit. Sometimes, this happens automatically. For example, for a new unit that is doing a lot of hiring, this helps to attract better talent.  Once job evaluation takes place, these employees will become ‘red circled’ (exceptions where the jobholder's grade is higher than what the job is evaluated at). However, it is very unlikely that the organization will reduce the grade of an existing employee in such cases. Therefore, it continues till the employee continues on the same job. Another option here is to get a ‘powerful leader’ (competent authority) to grant exceptions – to allow an employee to be hired/fitted at a level that is higher than that indicated by the job evaluation results. If there are a very large percentage of exceptions, it adversely impacts the credibility of job evaluation process. Therefore, each exception can make the next exception a bit easier!

Of course, these kinds of strategies can create long-term issues and inefficiencies for the unit and hence they can backfire from a long-term point of view.

Rob Peter to pay Paul but do pay Peter back with interest when Peter’s job is being evaluated

This involves shifting some of the responsibilities handled by one employee to another employee when the latter’s job is being evaluated and then more than reversing the process (by moving even more responsibilities back to the former employee) when the former’s job is being evaluated!  Yes, this can be a complicated process and lead to ‘red-circled’ employees if the job evaluation is practiced in the company in a strict manner (which involves reevaluating all the impacted jobs when there is a change in responsibilities of a particular job/when a new job is created necessitating the job evaluation). However, this takes a lot of effort to track changes and reevaluate on an ongoing basis – especially if these changes are done carefully over a period of time.

Such a complicated process is required as ‘simply inflating the responsibilities’ is unlikely to work. Job evaluation supposed to be done based on approved job descriptions and hence just being creative about the job responsibilities won’t do -unless there is no such validation/approval process for job descriptions in place. Also, job evaluation is done top-down and a job is evaluated in the context of the constellation of jobs surrounding it (especially the job of the reporting manager) and hence inflating the job responsibilities can lead to easily noticeable overlaps that serve as a red flag to the person evaluating the job. 

If you can't convince them confuse them

If the person doing the job evaluation doesn’t put in enough effort to understand the organization context and the responsibilities of the other jobs around the role being evaluated, one might have a decent chance of getting a higher job evaluation by confusing the job evaluator on the contribution the particular job makes! A liberal use of organization-specific jargon might not also be a bad idea!

Other tricks of the trade

Positioning the job as a clear successor position to the manager’s job and arguing that the overlaps with the manager’s role are by design (because of the requirements of the particular context) might work in some cases! In most of the job evaluation methodologies, some of the factors tend to be hierarchical and hence the evaluations on those factors are constrained by the evaluation of the manager's job on the same factors). Hence, this approach is not always so easy. 

Most of the job evaluation systems work in such a way that ‘stealing responsibilities from the jobs of the subordinates’ won’t have any beneficial impact on the job evaluation score of the job being evaluated. Hence the attempt to steal responsibilities from the jobs of the peers and the manager!

Being in the good books of the ‘job evaluation overlord’ can also be highly beneficial because of the judgement and discretion involved in job evaluation. This might reduce the chances of the 'overlord' exercising his/her 'negative power' (the power to block) in the cases of imperfections in the job descriptions and/or in the rationale to justify a particular evaluation. In most contexts, often there are imperfections in the job descriptions and the rationales and even the ‘job evaluation overlord’ has to pick and choose the battles he/she wants to fight to avoid being seen as too bureaucratic/unrealistic. 

In lieu of a conclusion

So, where does this discussion leave us? Job evaluation, like most things in life and work-life is a mixed blessing. Job evaluation not an exact science (it is both a science and an art). It is resource intensive and can introduce rigidity into the system. However, job evaluation can serve as a very valuable input to organization design, job banding, rewards, career pathing and inter-unit talent movements.  

As we have seen above, it has been argued that job evaluation is a rationalized institutional myth. One of the key functions served by a myth is the maintenance of social order (order in the social system called the organization, in this case). In this sense, job evaluation elevates the decisions on aspects like band-fitment from the realm of 'common sense' to the realm of the ‘scientific'. It provides an explanation and justification for an organizational hierarchy that might otherwise have been difficult to explain. Job evaluation signals to the employees the notion that the current structure of inequality is right and just! Yes, organization reality is socially constructed to a large extent and maintenance of social order is very important in business organizations too!

Therefore, for an organization the key question is whether it adds net value in the particular context – considering the benefits, the cost, the effort required and the possible side effects. Of course, for an individual it is essentially a matter of whether it is a help or a hassle for him/her and hence the decision on ‘whether or not to attempt a defense against job evaluation’ is likely to depend on that (moderated by altruistic and masochistic tendencies)!

 Any comments/thoughts?