What to Manage: Workers? Or the Links Between Them?

I’ve been reading an article (HBR, Competent Management) which mentioned “obstacles that often prevent executives from devoting sufficient resources to improving management skills and practices”. The research they reported made it clear that better management skills lead to higher competitiveness and better performance all around. So, understanding obstacles to good management is a good idea.

What are the “obstacles”? First, overconfidence: managers think they’re already doing a good job. Another obstacle is that many managers can’t make an objective judgment about how well things are really going. The article included several other obstacles, but the whole list made me recall the most frequent problem I encountered in my career as a management consultant: managing the people and their activities. That’s not what needs to be managed.

I learned about that obstacle very early in my career, from the CEO of a non-profit firm. I saw a need for better management practices – aligning people on goals, measures, tracking and reporting. Two of his groups were making mistakes in the products and communications they were sending out to the firm’s members, prospects and customers and the reason was they were not collaborating with one another at all. When I suggested to the CEO that it would be useful if his Marketing team and his Communications Office got together at least once a month to clarify what each of them needed or wanted from the other, he banged his fist on his desk and shouted at me, “They should already know their jobs!”

Omigosh – he was watching what his people DO instead of what they DELIVER to others! Wow.

I was startled that he shouted at me, of course. But it was difficult to believe he did not have a process for ensuring that different units in his organization had an opportunity to talk with each other to stay updated on the products, services and communications they produced, sent out, and/or exchanged with one another. That would have given the Marketing team an opportunity to find out what the Communications Office was sending out to the firm’s prospective members, which would have helped Marketing do a better job of recruiting new members.

The CEO couldn’t see that the Marketing team needed information from the Communications Office and vice versa. Instead of supporting effective and goal-oriented communications between groups, he was watching what goes on inside those groups, as if they were stand-alone entities. As I went through my whole career, that was something I came to see as a frequent cause of misunderstandings in organizations. It was also a source of blaming “those people” for not knowing what they’re doing.

The mistake was the focus on what people were “Doing”, which isn’t what I was watching for at all. I focused on what moved from one group to another or went out to a customer: the products, services and communications that go out of Group 1 and into Group 9, then on to a user/customer. This allowed me to start at the end of the line, getting ideas from the Receiver of a delivery about how they evaluate or measure the quality and effectiveness of what they received. Then I could work with the Sender to obtain and use that feedback from the Receiver on a regular basis. I admit, it was sometimes touchy, especially if the Receiver was unhappy with what they got from the Sender. But I was the “ambassador”, carrying feedback to the Sender and assisting them in finding ways to put it to work. Ultimately, though, the two groups would establish a productive relationship and better products, services and communications were then available to all.

I was surprised to find that almost no manager watches the links between Senders and Receivers. They’re watching the “job”, the “work”, the people and their activities – but that’s not where the leverage is. Just sending something from one place to another doesn’t mean you’re getting the job done. You need to get the Receiver’s feedback on how well it worked. Was it the right quantity or size? Was the quality what they wanted or needed? Did it arrive on time? Does it perform properly, producing the effects the Receiver desired?

Getting feedback requires establishing a reliable communication link between Sender and Receiver, an easy management practice to implement. And, according to the article, good management practices will pay off in a big way, delivering better overall organization performance. That non-profit CEO actually learned how to improve the whole network of teams in his firm.

Even though that article I read didn’t focus on the links between groups, it had a lot of smart things to say about competent management. One valuable point was that companies think strategy is more important than management. I haven’t seen this discussed for over a decade, and the research reported in this article clarified that management competence is more important than strategy. It’s a good read, even if it is over 3 years old. Check it out: (HBR, Competent Management).

One Management Trainer’s Advice – and Why I Think He’s Wrong

I’ve been clearing out – very slowly – the client files from my career as a management consultant. I found some notes on what one workshop leader – I’ll call him Alex – said about “how to be a good manager”, and as you’ll see below, I didn’t agree with him on several of his ideas.

Thoughts on a Workshop about “How to Be a Good Manager”

HE SAID

SHE SAID

1.  Have one-on-one meetings with each of your staff members to establish performance expectations. 1.   Have weekly group meetings with your whole team to review goals, clarify assignments and identify obstacles or problems. Don’t use the “expectations” thing.
2.  Rely on relationships and personal connections to get things done. 2.   In any conversation for getting something done, (a) state the objective and the value in succeeding, (b) establish agreements on who will do what by when, then (c) take responsibility for the follow-through with everyone. Build productive relationships, not “connections”.
3.  Influence and motivate your people rather than using your “power position” or your title. 3.   Rely on productive communication – dialogue to clarify goals and measures, clear requests and promises to establish agreements, and follow-up to review progress on agreements – to generate engagement and momentum.
4.  Encourage planning all schedules and activities based on priorities. 4.   It is important to be clear about priorities but recognize they may change quickly and often. “Planning” is a process of (a) identifying intended results and outcomes, (b) formulating the processes and actions that will produce those results, and (c) establishing timelines and assignments for accomplishing them. “Priority” can be fleeting and is not always a reliable management tool.
5.  Resolve conflicts and deal with emotional behavior promptly. 5.   Dealing with conflicts and emotional behavior is best based in policy rather than playing therapist to resolve them. Your people should understand that they will participate in resolving conflicts, including problems with emotional behavior. A manager is not a den-mother.

Mary Parker Folet, a 1920’s management guru, said, “Management is getting things done through other people.” She did not say, however, that management needs to focus on the people, but that is where management theory has taken us. This people-focus, visible in each of Alex’s pieces of advice, has given us a people-oriented vocabulary that has taken over management thinking. Here it is:

One-on-one meetings” focus on an individual rather than promoting coordinated teamwork. They are often seen as making someone feel “special”, or an opportunity for “development” of some kind. Sometimes it develops teacher’s pets, though, which can cause ill feelings among team members.

Expectations”? They are subjective – they live in your head and can change in a flash. Further, it can sound a little demeaning to tell people, “Here’s what I expect from you.” Simply state the goal, then discuss it until you are you are confident there is a shared understanding of what success looks like.

And “performance”? The word literally means “provide thoroughly”, but we have turned it into a code for evaluating people. If it’s not quantitative or visible, it may not be performance at all.

“Connections” are personal relationships, not necessarily productive ones. For a manager, it is more useful to learn how to make agreements to produce specific results and support staff people in committing to do or produce a certain result by a specific due date. Using a personal relationship to get a performance promise from someone may be seen as manipulating them into doing you a favor. Why not keep things a more professional?

And how about “influence”? This is another interpersonal game, like “expectations” and “connections”, and it relies on personalities. First, “influence” is a vague concept: how do I know whether you are influencing me or I am influencing you? But influence can also be very short-lived (ending when the Influencer leaves the room), and may not produce any genuine engagement or commitment. Maybe people don’t like being “influenced”, experiencing the process as a form of bossiness.

“Motivation” – we talk about it like it’s a thing, as if it can be passed from one person to another. But your motivation is for you to generate, not mine to give to you. I can’t motivate anybody but myself. I’ve seen managers work to “motivate” their people, expecting some response that seldom arrives. I’ve also talked with the people who have been the object of those attempts and are often not inspired. One person said, crossly, “I don’t want her to try to motivate me. She should just talk straight.”

“Priorities” are individual interpretations that are unlikely to communicate anything specific about the desired due date, the product quality or quantity. “Priority” is just a code for saying something is important and/or urgent and a priority can change quickly if something else happens. Stick with performance agreements and follow-through, including the details of what is wanted and needed by when.

“Resolve conflicts and deal with emotional behavior promptly” – this last one is the icing on the cake of management’s “people-talk”. It fails to draw the line between the rigor of clarifying agreements and holding a psychotherapy session. Both conflicts and emotional behavior should be rare phenomena in the workplace, and this suggestion from Alex takes us back to the beginning: hold group meetings, encourage people to work together in pairs or sub-groups to get things done, and deal with the whole picture of what all team members are doing and where people need help or resources. The team can solve problems, including some personal ones. Create transparency wherever possible, without releasing confidential material, and people will support one another.

Management is often misunderstood to be all about people – getting people to do things and having them behave “properly” to support a productive environment. But you can make management about getting things done with group discussion on the specifics of what, when, and who, which gets an actionable message across. Then, if you add respect, good manners and some friendliness or humor, you’ll also make room for everyone to be more responsible for their commitments to “provide thoroughly”. Do we have an agreement?

A Close-Up Look at Micro-Management

When I was a management consultant, clients sometimes complained about “micro-management” in their organizations. I had to look it up, because I thought it just meant someone was paying too much attention to details. I learned that it’s much worse than that, but now I have been educated in real life, because I have now been micro-managed.

I am working, post-retirement, as a volunteer in a small organization. I support three Committees, each of which has a Chairman, so I take my job to be assisting those Chairmen in setting and attaining goals as well as supporting the Committee members in working as a team and being productive and effective. All was going smoothly until one Chairman resigned and was replaced by Captain Micro.

The Captain watched every action I took, heard every idea I offered and saw every communication I delivered to Members. He then criticized each of those things, saying this email to members was “too complicated”, and that idea was “inappropriate”. His instructions to me were specific but piecemeal, and I wasn’t always able to assemble them into a meaningful whole. I confess to having lost my sense of humor at one point, telling him that his latest instruction was “another piece of our communication problem”, which was the first time I had let him know how I saw the situation.

Another annoyance was that he wanted me to check with him about every little thing before I took any action, as if I couldn’t see for myself what would work. He gave me miniature assignments – send out this email to the members, forward him a copy of Aaron’s article from last week, etc. And he often messed up my schedule by giving me several different due-dates and times for each request. Multiple emails and phone calls showered down in the first week of working with him, which became annoying. I suspect he could hear the impatience in my voice by that Friday afternoon.

Week Two didn’t gain any momentum. Fewer calls and emails, but he was still stalling on taking any substantive action for the Committee and was not allowing me to make any decisions (or he corrected the ones I had already made). What had been an unfolding project for the Committee was now a mute folder lying on my desk waiting for attention, and I couldn’t get him to move ahead. He didn’t seem to know or care what I had done for the prior Chairman nor to have any sense of urgency about moving the members’ teamwork forward to meet the goal everyone had aligned on before his arrival.

It’s over now. Captain Micro won’t work with me – he’s going to do it all himself. Perhaps I’m too headstrong, pushing to finish the Committee’s current project so we could move on to future aspirations. It appears he has decided to take over the facilitation tasks I had been doing – sending out what he chooses to the members, and perhaps also taking notes on their monthly calls and creating an agenda for the next call (though he may not think such tasks are necessary).

Now I’m supporting only two Committees. I initially feared that Captain Micro’s lack of support would undermine the group’s sense of purpose and cohesion, but several members have now been in touch with me, looking for more productive pathways to get what they wanted to accomplish. Captain Micro will go his own way with his new Committee – and I wish them all the best. I’ll continue my accountability for supporting the two remaining Committees as best I can, and be grateful for the trust and respect of their leaders.

 

Manager Tip: Clarify What You Really Want in Every Work Request

One job of a manager is to ask, invite, or demand that other people “do their work”. But people understand the word “work” in three different ways. You may be asking that I “do” something, like you want me to put the appropriate data into a spreadsheet for analysis. That’s not the same as getting something “done”, which is when you tell me to get that spreadsheet finished. And it also doesn’t mean “delivered”, which would be you asking me to send the finished product over to you by close of business today.

When you want something from me, it is important to clarify: Do you want me to work on something? Or produce something? Or bring it to you or someone else? Do – Done – Delivered: do you want to keep me busy, or finish something, or turn my final result over to somebody? Or maybe all three?

Good work typically generates a specific product, service, or communication that calls for all three: to be produced, completed, and delivered to someone who will use it and/or value it. The best way to produce results – to perform well – is to focus on those “deliverables”.

A focus on deliverables, sometimes called “Do-Dues”, requires giving attention to the desired outcome(s) – the products, services, and communications to be provided to another individual or group. Deliverable results always have:

  1. Specific characteristics such as production processes, amounts, formats, and other attributes or qualities,
  2. A producer/sender and a user/receiver,
  3. A due date and time it will be sent or received, and
  4. Some value or benefit that will serve others.

Both the work-requester and the Doer-Deliverer should clarify – and agree on – these four aspects of what a “good result” will look like.

If you want to improve someone’s “performance”, don’t focus on what they should do. Start by being clear on the specifications, requirements, and conditions for what will be sent and received, to and from others. This seemingly small shift in attention – from what people are doing to the outcome of what they do – is actually very useful. If you add the information of who will receive it and why it matters to them, you have added value to people’s “doing-work” and to the result it produces. Magically, their “work performance” will improve too.

 

How Reliable are “Expectations” for Getting Good Performance?

Answer: Not very. Why? Because expectations live in your head. If they are not put into a conversation with the person you “expect” will take action, those expectations have no way to get out of your head and into theirs. At least put them on a post-it and hand it to that person. That will increase the likelihood the person will take some action, all the way from 7% up to 24%.

OK, I made those statistics up. But in the past two days, I have heard three different people refer to “expectations” as if such a thing existed and are as real as a sign in the hallway or a billboard along the road – visible, in big bold print, where everyone can’t help but see them, and they know what to do. Here is one of those conversations:

Karyn, the head of an IT project management team, saw her boss in the hallway. He stopped her and said, I want you to gather the data on project performance over the last six months and prepare a report on what you find by the end of this month.” Karyn told him she would do that, and they went their separate ways.

Later that month, Karyn told me her boss was really cross with her because she had not delivered the report. “It wasn’t the end of the month”, she told me. “I thought he wanted me to prepare the report, but I didn’t know he wanted me to deliver it to him! Plus, I really had no idea that for him, the end of the month is really the middle of the month. He must think I am a mind reader.”

Karyn’s boss had “expectations”, thinking that she would know – of course – that “prepare a report” means “prepare a report and bring it to me”, and that she knew he meant the end of the company’s financial month, which was on the 15th of every month. Karyn was bothered by this, and by not seeing any way to tell her boss that he was making assumptions that weren’t valid.

I’m reminded of a former client’s response when I told him that the Marketing Department team was not giving the Customer Service office the information that they needed to keep customers informed about new options for different service packages. I thought he would help me be sure the communications between the two groups was workable for both of them. Instead, he banged his fist on his desktop and shouted, “They should know their jobs!” He apparently didn’t realize that jobs change faster these days due to technology and communication improvements, and that what it says on most people’s “job descriptions” (if they even have them) is usually way out of date.

So, if you have expectations for someone, whether a co-worker or a family member, it will be helpful to explain those expectations to the people you expect to perform in a particular way. If you explain what you want, when you want it and maybe even tell them why you want it that way… AND if they agree to that, then you have an agreement between you. If they don’t volunteer an agreement, ask them if they will agree to do what you ask.

You at least need a clear statement of what you want, and when – plus a “yes”, before you are entitled to have an “expectation”. What’s inside our head is less obvious to others than we think.

 

The Management vs. Leadership Debate

I’m sorry to weigh in on this, but I can’t ignore it any longer due to a current writing assignment on management. I worked with executives and managers for my whole career of 35+ years and came to have very high regard for them, thinking of them all as “managers”. I never thought of that as a derogatory term in any way.

But apparently Abraham Zaleznik (in the Harvard Business Review of May-June 1977) asked the question, “Managers and Leaders: Are They Different?”  That launched a 40-year discussion of putting down management as simplistic and dealing only with the routine, while elevating leadership as… drumroll, please… visionary and inspiring.

Unfortunately, that premise was reinforced by otherwise brilliant John Kotter, in his “What do Leaders Really Do?” article in HBR, December 2001. As a result, the people who enjoy an opportunity to take sides between “bad vs. good”, “dullards vs. geniuses”, or any other “better-worse” kind of argument, have an excuse to keep up that artificial and divisive comparison.

I have tried to ignore this, going so far as to tune out the vote of MBA students in Jeffrey’s classroom a few years ago, when they were asked, “Would you rather be a manager or a leader?” The entire class raised their hands for being a leader. Managers, I’m sad to say, have a bad reputation created by “leadership experts”.

But now I must face the flurry, which is, I hope, winding down these days. Here’s a quick summary of the argument:

WHAT MANAGERS DO WHAT LEADERS DO
Planning and budgeting Creating vision and strategy
Focus on routine operational results such as producing products and services Focus on strategic direction and producing useful change
Organizing and staffing to build capacity Aligning people with the vision or strategy
Specialize in structural matters Specialize in communication issues
Control Inspire and motivate
Solve problems Prepare organizations for change
Managers are task-oriented Leaders are people-oriented

Mitch McCrimmon (https://www.lead2xl.com/john-kotter-on-leadership) said, “This was a disaster for our thinking about management from which we have yet to recover.” I agree. The fact is that managers do all those things at different times for different reasons. Humans do not fall into such neatly arranged categories.

Watching managers and leaders in action for over 3 decades, the primary factor in the differences between people in positions of authority is their location in the hierarchy. Those at the very top of an organization – the “C-Suite” and Board members – are called upon to communicate more frequently with “outsiders” who are in civic, community and corporate power positions, rather than focusing first on internal activities and connecting with fewer “outsiders”. Every organization has a level in the hierarchy where communications seldom reach up or down (I’ve seen them, remember?), and both sides of that authority dividing-line don’t know much about the other one.

That gives the top layers of an organization a closer view of the worlds outside the organization, hence a larger context to work with. Unfortunately, it also gives them a smaller view of those toward the middle and bottom of their own organization. The number of CEO’s and Executive Directors who know almost nothing about what their people toward the bottom of the organization are dealing with daily would horrify you. That is also the reason organization change is so problematic, often failing to meet planned deadlines and budgets. The “leaders” simply do not see the realities and challenges that are the facts of work life for those in the bottom rungs.

OK, that’s all I need to say for now. I will get back to my writing assignment, which is on the subject of “management”, i.e., the machinery that operates organizations and a layer of smart people that is a lot more strategic, people-oriented and effective at communication than they are given credit for.

Happy New Year!

The Manager-Staff Gap – And an Idea for Updating the Performance Review

Looking at a file from work with a former client, I found one particularly interesting list of “Top Five” workplace issues for their organization. What made it interesting was that we could see the difference between problems that Managers had, and the problems reported by lower-level Staff members.

The survey was made of 56 Workplace Assessment questions designed to identify their biggest workplace problems; we used the Consultant Subscription to survey different groups at the same time, but instead of defining survey groupings by their department or function, we grouped them by their different levels in the hierarchy. Here’s what we found:

  • The #1 workplace issue for Managers – “Some projects and assignments involve other teams and departments, but it is difficult to get their cooperation and support.”

Okay, that sounds like a reasonable observation, since Managers have to deal with other departments (and their Managers) in a more administrative way than Staff do.  But it was interesting that the Staff did not rank this as being important at all – they simply did not see it as a workplace problem. Perhaps Staff should thank their Managers for protecting them with having to deal with this issue? Another result:

  • The #1 workplace issue for Staff members – “Some people do only the minimum work necessary or don’t do their assigned work, making it hard for others to get their work done.”

This seems reasonable too, since Staff have to deal with finding their way through the jungle of their jobs whenever their workplace contains one or more low-performing Staff members. This Staff issue, however, was ranked very low on the list of problems reported by Managers. Apparently, Managers do not see the performance barriers that Staff are actually dealing with in producing their results.

What did Managers and Staff agree on? Another result:

  • The second-biggest workplace issue for both Managers and Staff – “There are significant differences in the quality of work that people do.”

Interesting to see that both levels notice the “quality difference” of Staff performance, and both find it to be either a problem that uses too much of their time and attention, or a it’s problem they do not know how – or want – to address. What could cause this disparity?  Perhaps it was the 3rd disparity – an issue that Managers ranked as their 3rd-biggest problem, but Staff members didn’t even include in their high-ranking workplace issues list:

  • The Manager issue that was invisible to Staff: “Performance reviews are subjective and not helpful in giving guidance for improvement.”

Wow! Managers and Staff agreed on the variability of work quality, but only Managers saw the problem of subjective performance reviews. Could that be because Staff are resigned to being evaluated in subjective ways on subjective criteria?

The Managers chose to update their performance reviews. They found a person in HR to help them orchestrate several discussions with a group of Managers and Staff supervisors. These were the people directly involved with the way that “performance” actually plays out in the workplace, and they collaborated to specify what they meant by “high-quality work”.  Now this organization focuses on using observable attributes of work performance rather than subjective evaluations based on intuitive criteria.

One Manager’s comment after using their new performance review was, “Now we are evaluating “performance” as an attribute of work and results, rather than evaluating the attributes of individual people. This is a good lesson on how to redefine work quality and performance.”

NOTE: The Consultant Subscription provides the opportunity to use the same Group Assessment survey for different groups at the same time. The choice of how to perform the groupings is up to the Consultant.

Supervisors See Four Kinds of Personnel

Best Employee. Supervisor gives work orders and turns job over to worker. Worker requires only recognition.

  1. Accurate and complete work; Good results.
  2. Accomplishes more jobs; Productive and efficient.
  3. Organized; Knows where things are.
  4. Can do all assignments; No hand-holding needed.
  5. Looks ahead; Thinks how to help; Has good ideas.
  6. Good attitude; Courteous to all.
  7. Volunteers to help team members; Gets involved.

Good Worker. Supervisor recognizes good performance and points out problems. Worker requires support for teamwork.

  1. Willing to learn; Wants to do better and improve skills; Interested in the job.
  2. Takes on any job and does what is asked.
  3. Hard working; Skilled; Paying attention.
  4. On time with results and finishing jobs.
  5. Careful worker; Does complete work.
  6. Keeps work environment in good order, equipment and supplies organized.
  7. Often helps others on the team.

Improving Worker – Supervisor is clear on details and gives encouragement. Worker requires instruction and appreciation.

  1. Doesn’t know all aspects of the job; needs guidance.
  2. Afraid to make decisions without asking what to do.
  3. Results sometimes good, sometimes not.
  4. Willing to learn with supervisor encouragement.
  5. Sometimes doesn’t see to do more than necessary.
  6. Capable, could do more with better results.
  7. Requires attention dealing with sensitivities.

High Maintenance Employee – Supervisor points out everything to do. Worker requires attention.

  1. Late to work or has to be told to do jobs.
  2. Works slowly; Inefficient. Makes small jobs big.
  3. Moody or argumentative; Complains to co-workers.
  4. Messy work area; doesn’t take care of equipment.
  5. Watches others at work; Sometimes distracts them.
  6. Takes easy jobs or waits to be told what to do.
  7. Often turns in work results that require more work or cleanup from others.

Performance Management = Count the Hours Worked? Or the Results Produced?

I love reading The Economist magazine for its useful perspective on the world. Last week an article included a summary of the evolution of “performance management” at work.  Here it is:

  1. Before the industrial age, most people worked in their own farm or workshop and were paid for the amount they produced.
  2. When machines were developed and were more efficient than cottage-industry methods, factories emerged. Suddenly, workers were not paid for their output, but for their time – they were required to clock in and out.
  3. Today, work hours are still the measure, and employees have found ways to make it look like they are working longer hours than they really are. The article mentioned some tricks they play to maintain their image as a performer:
    • Leave a jacket on your office chair;
    • Walk around purposefully with a notebook or clipboard; and/or
    • Send emails at odd hours.

The name for this new phenomenon is “presenteeism”: being present but not productive. This is because, the article states, “managers, who are often no good at judging employees’ performance, use time in the office as a proxy”. Some take the shortcut of “judging” performance based on the hours worked rather than understanding the actual results produced. That decision can create a damaging idea of what workplace “performance” means.

Perform: The original meaning is “To provide thoroughly. To deliver completely, as promised.” That tells us performance is the fulfillment of a promise for an action or delivery of a product, service, or communication. It means a manager has to clarify which results, by whom, and by when – not to mention discussing resources, and identifying relevant key players. It requires thoughtful, productive communication, including a “performance conversation” in which the manager clarifies the results and timelines then gets an agreement – a promise from the employee – to deliver the intended result(s).

Performance is not determined by a judgment based on apparent work hours. It entails tracking promises for results and the results produced and delivered.  But managers who take that performance-judgment shortcut are also short-circuiting the work of management.

A “performance review” is more than checking a time clock or filling out a form. It looks at the promises made and/or revised, promises kept, and promises not kept. It is more objective than subjective, looking at what results each person (or team) actually produced.

It does take time and attention to manage performance in terms of results, so I see why some managers rely on their personal judgment instead. It’s sort of like leaving a jacket on their office chair or walking around purposefully with a notebook or clipboard. Looking busy will often be perceived as being productive.

Leadership? Or Management? What’s the Difference?

An article in The Economist (March 30th, 2019, p. 67) said, in the opening paragraph, “Everyone can think of inspiring leaders from history, but managers who think they can base their style on Nelson Mandela, or Elizabeth I, are suffering from delusions of grandeur.”

First, did the reference to Mandela and Elizabeth I tip you off that The Economist is a British magazine? More importantly, do the words “leaders” and “managers” suggest that leaders are managers? Or that managers aspire to be leaders?  It got me thinking. Which means it nudged me to take out my Etymological Dictionary on the origins of words.

Leader – One who conducts others on a journey or course of action, keeping watch from above and providing defense, protection and guidance for the action below.

Manager – One who handles, controls, or administers a journey or course of action.  Note: the word “manage” is derived from “manus”, Latin for hand, as in “handling or steering a horse”, i.e., holding the reins.

So a manager is in control and steering the action, while a leader is protecting and defending the actors. Sounds like two different roles to me. Which job would you want?

If you are a manager and want to be a leader, here’s a tip from that article: Being “competent” involves one important skill – the ability to have dialogues, or what we call Understanding Conversations. This kind of leadership “communication competence” has three important ingredients:

  1. The ability to listen and understand, sometimes called empathy.  “Team leadership requires having sufficient empathy to understand the concerns of others.”
  2. Dialogue with people ‘below’.  “Employees are more likely to be engaged with their work if they get frequent feedback from their bosses and if they are involved in setting their own goals.”
  3. The ability to course-correct.  “When things go wrong, as they inevitably will, a good leader also needs the flexibility to adjust their strategy.”  This would be done in dialogues with others, both above and below the leader.

The article made some other good points:

  • On competence and charisma: “The biggest mistake is to equate leadership entirely with charisma,” and, “Competence is more important than charisma.”
  • On competence and confidence: “People tend to assume that confident individuals are competent, when there is no actual relationship between the two qualities.”
  • Most fun quote (read it twice): “Charisma plus egomania minus competence is a dangerous formula.” (This reminded me of someone who is much in the media these days.)

The article also mentioned a book by Tomas Chamorro-Premuzic, which should be a best-seller, based on the title alone: “Why Do So Many Incompetent Men Become Leaders? (and how to fix it)”. That one should be jumping off the shelves!