Eight to Late

Sensemaking and Analytics for Organizations

Archive for the ‘Leadership’ Category

Macrovisions and micromanagement

with 8 comments

Introduction

Much has been written about leadershipmanagement and the difference between them.   The former is associated with creating a shared vision and strategy for the future whereas the latter has administrative and bureaucratic connotations. Most organisations  celebrate leadership but consider management to be little more than an operational necessity.

In view of the exaggerated rhetoric regarding leadership it is of interest to ask how it is actually practiced on the ground.  This question was investigated by Mats Alvesson and Sven Sveningsson in a brilliant paper entitled, Good Visions, Bad Micro-management and Ugly Ambiguity: Contradictions of (Non-) Leadership in a Knowledge-Intensive Organization.  In this post I elaborate on one of their key conclusions:  that there is a gap between  the espoused view of leadership and its practice.

Leadership in theory

The emphasis on leadership in management theory  has lead to the widely accepted notion that leaders matter and that their actions can affect organizational performance and effect change in a positive way. Moreover it is also assumed that it is straightforward to identify leadership qualities in people as these manifest themselves through a set of well-defined behaviours and attitudes. In other words, leadership is a stable and robust concept. The main aim of the authors was to find out how well this theoretical conception of leadership holds up in the real world.

The case study and research methodology

The authors conducted a detailed study of how managers in a knowledge-intensive organisation viewed and practiced leadership.  The study consisted of extensive, multiple interviews with managers at different levels in the company (from the CEO to project managers) supplemented by observations made at management meetings.  Two rounds of interviews were conducted. In the first round, the authors asked the interviewees what their jobs entailed. Most responses centered on vision, leadership and strategy.  However, when asked to elaborate on their responses, most managers described their day-to-day work in terms of administrative and bureaucratic managerial procedures. This pointed to a gap between espoused leadership and how it is actually practiced. In the second round of interviews, the authors attempted to gain some insights into the reasons for the gap.

Macrovisions: the espoused view of leadership

The authors observed that when asked questions about their jobs, most managers spoke of leadership and how they practiced it. Big picture topics such as vision and strategy – what I call macrovisions –  were recurrent themes in their responses . Most managers claimed that their job was to articulate such macrovisions while leaving the details of day-to-day operations to their subordinates.  As examples, consider the following responses from interviewees:

A strongly knowledge intensive work as ours build on independent and active employees who has (sic)  the ability to take their own initiative.

This is consistent with modern themes of worker autonomy in decision, particularly in knowledge-intensive organisations such as information or biotechnology.  Reinforcing this, another manager said:

 I try not to interfere too much in operations. That would be wrong in every way, no one would benefit from that, but I am available if anyone has an operative question, otherwise it’s more me trying to make myself unavoidable in strategic issues but avoidable in operational issues.

Yet another manager spoke of macrovisions in the following way:

And if you provide the big picture, if there is a sense that these [minor decisions] are in the context of the wider strategy and it is not just, bang, bang [shooting with finger from the hip] we shoot this one and now we shoot that one, and now we gallop off in some other direction; if it fits a bigger picture, then I think we can manage. But that is where leadership comes in I think, we need to provide that context and the picture and the overall direction, to say “we are not here in the middle and you cannot [be allowed to] ride off in just any direction.

Macrovisions thus appeared to provide a broad framework within which employees had the freedom to make decisions that were broadly consistent with the organisation’s strategy.

Again, it is important to emphasise that managers were not specifically asked about visions, strategy or leadership, yet their responses invariably alluded to these themes.  The responses suggest that most managers in the company viewed leadership rather than management as their primary role.

This was consistent with the overall management vision set by senior executives.  As the authors put it:

The expectations formulated by higher-level senior managers and made explicit by the CEO on various occasions, is that managers should refrain from detailed management

Indeed, some managers spoke of managing details in derogatory terms. Consider the following response:

Requesting detail which is of no value to your personal job or position, and that can be detail about a specific office, budget thing through to really me going down to the project level and saying, “Well, how are we doing on that project and I really want to know”, so it is about the ability not to do that, and delegate and trust the people.

In short:  most managers felt that their work involved articulating and implementing macrovisions rather than practising micromanagement.

Micromanagement: the practice of “leadership”

A natural question arising from the above is: how did managers actually practice leadership? What are the things they did in their day-to-day work that exemplified leadership?

To answer this question, interviewees were asked what they did in their day-to-day work.  Strangely, most managers reverted to themes they had described in uncomplimentary terms. For example, when asked to elaborate on how he practiced leadership, one manager said:

There are many different ways of working. I think that as a manager here one has to implement significantly more directive ways of handling people, that is, that you say to people that you will spend the next month occupying yourself with this development, I want you to learn about this. I think that you have to have a much more directive way of handling of people in these operations.

This was not an isolated case;  another manager said:

I do get involved from a technical viewpoint, I expect, obviously my knowledge is still developing here, but I expect to understand quite consciously what the group is doing.

Yet another manager, when asked about the leadership tools that he used, referred to things such as budgets, recruitment etc. – things that are usually concerned bureaucratic, administrative procedures. There was little if any reference to activities that one might associate with leadership.

There is thus a clear gap between what the managers professed to practice and what they actually practiced. In the authors’ words:

…the responses brought forth aspects of managerial activities obviously quite far removed from most understandings of leadership in contemporary management literature and also from the more ‘grandiose’ ideas on the subject that they also claim to believe in and base their work on. Managers therefore talk of themselves as leaders without doing much that clearly and strongly refers to ‘leadership activities’. The case study exhibits the contrary: the activities of managers are more closely related to what is understood as micro-management…

Indeed this view was confirmed when the authors spoke with lower level managers. A project manager said:

Perhaps there’s a dialogue about that (leadership) that doesn’t really percolate down to those in production and it tends to become reactive. And micro-management, there’s a will to know too much in detail, when perhaps they should really be working with empowerment, that people are able to take responsibility, to send responsibility for the budget to me and have faith that I take responsibility for my colleagues, and all the positive talk such as “we are going to be the company of choice”, how are we going to realize all that, there’s too much administrative detail going through my superior.

…so much for all the talk of leadership.

The rhetoric and reality of leadership

From the above it is clear that we have a paradoxical situation:  managers believed they were being leaders when they are actually weren’t leading at all. The question is: why did this happen?

The authors offer a number of speculations for this, which I briefly outline below.

Firstly, leadership qualities are generally seen as desirable. Management literature and education tends to place leadership at the pinnacle of managerial practice. Consequently, there is considerable pressure on managers at the middle and senior levels to display these qualities.

Secondly, there is the issue of identity; how managers see themselves. Like those described in the case study, most managers would like to view what they do as leadership rather than “mere” management or administration. As a result, they may unconsciously describe what they do in the flattering language of leadership rather than the mundane terms of management.  However, as the authors stated in the paper, “Leadership talk and fantasies seem to leave a thin spray of grandiosity on the ‘leaders’” Clearly,  this may be of more use in bolstering managerial self-esteem than anything else.

Thirdly, managers often have to deal with conflicting agendas and requirements. In the case study managers were expected to display leader-like behaviour. However, at the same time, they were held responsible for specific and very tangible results. To deliver on the latter, they often felt they had to keep track of the details of what their teams were doing and step in when things were going wrong. There was a continual pressure to get involved in detail while maintaining the illusion of being leaders.

Another point that the authors do not mention explicitly is that middle and frontline managers are often expected to lead without being given the autonomy to do so.

It is likely that some or all of the above factors lead to a divergence between the rhetoric and reality of leadership.

Conclusion

The central message of the paper is that the concept of leadership is an idealization that is often compromised in practice.  Most people who work in organisations will not find this surprising: managers are generally  aware that their day-to-day work has little in common with the  rarefied notions of leadership promoted by management schools, while  others are likely to have worked with  micromanagers  who are masquerading as macrovisionaries.

Written by K

October 20, 2011 at 7:35 am

Assumptions of competence

with 2 comments

In a recent post, I wrote: “…most folks don’t really need to be managed because they’re competent at what they do, and go about doing their jobs in a generally diligent manner.”

On reading this an old friend wrote to me saying, “I am sincerely of the opinion that most people are not competent at their jobs…”  And a bit later in the same message, “If you are looking for quality and excellence, don’t expect to find it in business and corporate culture.”

Incidentally, he is an independent consultant with over fifteen years experience, much of it gained in  large corporations . His observations regarding the general lack of competence and quality in the business world must, therefore,  be taken seriously.  Nevertheless, I reckon he’s at least partly off the mark: I believe it behooves managers to  begin with the assumption that people are competent, and that they want to do high-quality work.

Let me start my case with three stories which may sound familiar:

Jim is a developer at the regional office of a large multinational. He is overloaded with work, typically working on at least two (often three) major projects concurrently. As a consequence he cannot do justice to any of them.  It is clear that Jim will not meet the deadlines on any of the projects. Though it is clear that his situation has been caused by poor management, he’ll be the one carrying the can.

Tracy is an experienced database programmer working on a large project. She has worked on similar projects before, and is arguably the best person to provide technical input regarding the design and implementation of database program modules for the product. Yet, her manager insists that every suggestion she makes be approved by him prior to presentation to the team, often adding his two-cents to her designs.  Of late the team has noticed that Tracy has been unusually quiet during project meetings.

Sanjay has been working as an ERP adminstrator for a while.  He has the job well under control, and is looking to pick up some new skills. The company he works for has just purchased a large number of licenses for a major business intelligence platform, so there’s going to be plenty of work building new reports.   Sanjay knows this area is under-resourced: there’s only one person working on the new platform, right from metadata design to creating reports. Clearly, this person could use some help, and it’s a perfect opportunity for Sanjay to pick up new skills.  Sanjay approaches his manager for permission to get involved,  but the manager refuses outright.

Sooner or later…

Jim’s blamed for the failure of his project(s).

Tracy has lost interest in her job.

Sanjay’s administering his ERP system competently enough, but spends his (considerable) free time surfing the Net. He’s bored, and makes no effort to hide it.

To a casual onlooker it may appear that Jim, Tracy and Sanjay “are not competent at their jobs”, but that is a superficial observation. The real problem is that they are no longer motivated by their work. The basic reason for their demotivation is bad management. More specifically:

Jim’s expected to achieve the unreasonable or impossible.

Tracy isn’t empowered to make decisions that affect her work.

Sanjay isn’t given the opportunity to learn new skills.

Fact of the matter is, these folks want to succeed at their jobs and even go beyond  their job description, but they aren’t given the support, opportunity and / or the means to do so.

I did say my friend’s partially right, and he is: with a demotivated team, quality and excellence and all those wonderful things we’re supposed to strive for in the workplace aren’t going to happen.  The question is, who is responsible?  As Deming mentions in his management / quality classic, Out of The Crisis, the fault lies largely with management.  I agree, but many don’t.  I’d be  interested in hearing what you think. Do let me know through your comments.

Written by K

October 28, 2008 at 11:03 pm

People-first management

with one comment

Edwards Deming believed that work quotas and management by objectives (MBO) are counterproductive because they have a detrimental effect on quality – i.e they emphasise quantity over quality (see point 11 of Deming’s 14 principles).  Despite this, quotas and “objective” performance indicators advocated by MBO   continue to be popular in many organisations. I have had several discussions with assorted managers  from diverse organisations about this,  and although some concede the shortcomings of MBO,  many continue to believe it is the best available method for managing people because it “eliminates” subjectivity.

Now, the alleged objectivity of MBO can be debated, but it’s probably not going to make a whit of a difference: performance measurement systems and those oh-so SMART objectives are here to stay.   Which brings me to my point: performance measurement systems tend distort the behaviour of many managers who, in the push to achieve their objectives,  drive their teams beyond reasonable limits.  In the long run this is counter-productive: folks suffer burnout, lose respect for the manager or, if things get too much,  simply up sticks and leave for pastures of a better shade. This is a loss for the organisation. There is another way – one which  maintains employee motivation and engagement in the workplace whilst also getting the best possible results. Honestly, there’s no rocket science involved; just a small shift in perspective. It can be summed up follows: put people first and results will naturally follow.

How might one do that? Here are some concrete actions one can take:

1. Set people up for success, not failure: This is important: ensure that you set realistic objectives for team members, else you’re just setting them up for failure. Yes, I know Realistic is the “R” in SMART, but it’s frequently forgotten.  What do you do if your boss sets you unrealistic goals?  Two words: push back. Longer answer: explain logically (but without getting emotional or excited) why you think the goals are unachievable in the time allotted. By the same token, be prepared to receive similar feedback from your team. If you have to live with MBO, make sure that meeting objectives doesn’t call for superhuman effort. The workplace is no place for heroics.

2. Assume everyone wants to do their best: Some managers start with the assumption that people need to be supervised and monitored continually (as per Theory X) else they will lapse into slackness and indolence. In my experience the opposite is true: people generally want to do well and be recognised as valuable members of the team. This makes a manager’s job easy:give people meaningful work, empower them to make decisions about how they will do it, and  get out of their way; don’t interfere , avoid gratuitous advice (unlike me!), unnecessary recurring meetings and pointless written reports. Monitor progress informally ( MBWA works well for me in this regard). Jump in only when asked to do so, or if intervention is really necessary.

3. Be consistent: Tell a consistent story from day-to-day. What does this mean? Well, it’s a combination of things, including:

  • Not flip-flopping on decisions. I’ve seen managers who’ve changed their minds as often as they’ve changed clothes. Such behaviour confuses and eventually irritates everyone who reports to them.
  • Approaching work and any work-related issues that arise in a consistent way. This amounts to having a set of principles by which you live your professional life. This is particularly important when you’re under stress, because that’s when impulsive or “out of character” decisions are made. At such times remind yourself of the need for consistency: take a step back and examine the decision in the light of your principles.

Consistency is important; any inconsistency, though not apparent to you, will be quite evident to those who report to you.

4.  Treat failures as learning experiences: Despite everyone’s best efforts, there are times when things go wrong; sometimes badly wrong. At such points it is important to remember that mistakes happen.  Identifying and berating a scapegoat may feel good for a moment or two but the satisfaction soon fades, leaving you with a very upset team member.   Instead of looking to anoint a scapegoat, find out what went wrong and why, and what might have been done to avoid it. This should be done dispassionately, with a no-blame attitude even if the offender is responsible for a  mess up.

5. Don’t “crunch credit”: Often a manager will get the credit for work done by his or her team. This is natural because the manager is the public face of the team. Unfortunately in some of these cases, the  manager hogs the credit, barely acknowledging the efforts of his or her team. The right thing to do, of course, is to pass  the plaudits on to the team, ensuring that those involved are recognised and rewarded appropriately. The latter is important: the rewards should be appropriate  (no lucite plaques!).

6. Offer opportunities to learn new skills: Doing the same thing over and over again gets boring. To maintain the interest and engagement of people in their work, it is critical to offer them opportunities to do new things. Ideally you would have the means to send them to external courses, but sometimes that isn’t possible. However, it is always possible to give people a chance to pick up new skills whilst on the job. Admittedly this is somewhat easier in IT, where even a small corporate IT shop would have a range of technologies – certainly enough to offer people something new to learn. However, people need the time (and official sanction) to do this – and that’s where the manager comes in.

7. Empower people to make decisions: People should be able to make decisions regarding how they do their jobs. This helps in two ways:

  • Decisions get made at the level at which work is done.
  • Folks who do the work feel in control of what they do, and are able to fulfil their potential.

See my post entitled Empowered or Not – a litmus test of organisational culture for more.

The points listed above are based on personal experience. They’ve worked well for me in many different contexts ranging from projects to corporate environments. I can attest to their effectiveness in improving  team motivation and morale which,  in turn, leads to improved productivity and results.

To summarise: push people to achieve results and you’ll get neither results nor a happy team; improve team motivation, though, and you’ll get both in spades.

Written by K

October 10, 2008 at 8:20 pm