Posts Tagged ‘micromanagement’

The mission statement and motto of The Quintessential Leader is simple, but it encompasses the totality of quintessential leadership: “Lead people. Manage things.”

While we’d all like to be quintessential leaders and work with quintessential leaders, the reality is that a lot of people in leadership positions are not quintessential leaders.

There are key differences that highlight whether someone in a leadership position is a quintessential leader or not. Today’s post will summarize those differences.

Key differences between quintessential and unquintessential leaders

The first difference is that quintessential leaders lead (macromanage) their teams and unquintessential leaders manage (micromanage) teams. 

Let’s talk about micromanagement and why people are micromanagers. The first issue is that micromanagers don’t trust their teams; in fact, it turns out the only people they trust are themselves.

However, what’s ironic about this is that they apparently only trust even themselves up to a point, because if a person really had confidence in their abilities as leaders, they would have confidence that they built and developed a team they could trust.

The second issue with micromanagers is that they are in people’s faces constantly about every little detail and, by doing that, they smother the flow of productivity and they extinguish any initiative or desire to maximize effort on the part of their teams.

The third issue with micromanagers is their constant need to remind their teams that they are “in charge.” This is what dictators and despots do as well.

This, as you can imagine, doesn’t always set well with grown people who are constantly being treated like young children (before all you parents jump on me, I know this has to be done with tiny kids because they’ll run you over in a heartbeat if they don’t know you’re in charge, but you don’t say it all the time and eventually, you don’t have to say it at all).

So how are macromanagers (quintessential leaders) different?

Macromanagers trust their teams. They also respect their teams. Quintessential leaders build teams carefully and well, and they have confidence in the people they’ve chosen: that they will do the right thing and the best thing in all circumstances.

Macromanagers also look at the big picture and that’s where they keep their focus and invest their energy. They know that staying on top of the big stuff will ensure that their teams can progress and be successful. Instead of hindering productivity and squelching initiative, macromanagers fuel the development of their team members by allowing them to own the process.

Macromanagers never say have to say they are in charge. Their teams know macromanagers lead, guide, and direct them – and, if need be, will jump in and work right beside them or save them if they’re in over their heads – but their teams also know that, first and foremost, macromanagers are part of the team.

There’s no “us” and “them” or “you all” and “me.” Instead, there is only “we.”

Another key difference between people who are quintessential leaders and those who are not is in how they approach projects and goals.

Unquintessential leaders always present goals and projects as closed, detailed plans that are set in stone with nothing left for the team members to do except execute rote tasks. This is that mind-numbing work that all of us hate – it’s necessary at times, but no one enjoys it – and it kills enthusiasm and initiative.

It also prevents growth, change, and innovation, ensuring that things continue to be done the same way because that’s the way it’s always been done. This is a death knell to any organization. It may take a while, but the organization will eventually die because it stagnates and becomes obsolete.

framework for goals and projectsQuintessential leaders, on the other hand, always present goals and projects as a framework (much like builders do when they frame a house). This frame has established parameters, major milestones, and what the end result should look like completed, but everything else is in the hands of the team to conceptualize and complete.

Why? Although there are many reasons, I’ll give a couple here.

One reason is to develop the talents and abilities of the team, giving them a safe environment in which to try new ideas – and there will be failures, but each time there is a failure, there is also a learning opportunity – and bring some originality to the table.

The other reason is that quintessential leaders intentionally build their teams with people who are smarter than they are and who know more than they know. They know these people can find better, faster, more efficient, more effective, and more profitable ways to complete goals and projects. And, seriously, what’s the point of having all that intelligence, knowledge, and talent if you’re not going to use it?

A third key difference between quintessential leaders and unquintessential leaders is how they approach their teams.

Unquintessential leaders alway practice control of their teams. They dictate everything to their teams and they don’t allow any deviation from what they dictate. Team members who dare to deviate are resoundingly condemned and usually punished and humiliated publicly as a warning to the rest of the team that unless they stay in line, they will suffer the same fate. 

creativity quintessential leaderQuintessential leaders, on the other hand, encourage creativity. They recognize that each person on the team is unique and brings something unique – that’s why they are on the team! – to the team and to processes. Quintessential leaders also realize that creativity leads to innovation and innovation can lead to positive changes.

Another key difference between quintessential leaders and unquintessential leaders is how they view input from their teams.

Unquintessential leaders, as we’ve seen, know everything already, are in charge, and dictate everything, so it’s no surprise they don’t want any input from their teams. But they go a step further by banning their teams from giving them any input.

The message this sends is that unquintessential leaders don’t even need their teams, but they got stuck with them anyway, so they’re making the best of it by keeping them invisible and quiet.

Quintessential leaders, on the other hand, constantly encourage input from their teams. They know that they don’t have all the answers and they know they’re surrounded by a group of trustworthy and smart and creative people who can work together with them to come up with the right and best answers. 

A fifth key difference between people in leadership positions who are quintessential leaders and those who are not has to do with how they view the minds of their teams.

Unquintessential leaders don’t care what their teams think. They see thinking as dangerous. The way this is manifested is by demanding that their teams do whatever the unquintessential leaders say to do without questioning or thinking about it. And, just so we’re clear, this is what people like Adolph Hitler, Joseph Stalin, Idi Amin, and Robert Mugabe did and do too.

The problem with not knowing what others are thinking is that you really don’t know them at all, so the relationship is, at best, superficial, and, at worst, hostile.

And unspoken hostility is awful to deal with, because although it doesn’t come out in words, there are all these uncomfortable things that you sense and you don’t know why or what they mean and that you touch the edges of without knowing what it is that’s beyond those edges.

Quintessential leaders, in contrast, strongly encourage thinking among their teams. They understand the value of eschewing blind acceptance of anything without proof and conviction.

thinking teams quintessential leaderAnd quintessential leaders also understand that thinking people can help in the process of eliminating bad ideas, wrong ideas, untenable ideas, and unworkable ideas.

Quintessential leaders recognize that none of us exists in a vacuum and, because we’re all prone to making mistakes and missing the obvious, having a thinking team on board can rectify those things before we get so far down the road, investment-wise, with them that it’s very costly and very hard to tear everything down and start over.

The next key difference between quintessential leaders and unquintessential leaders is in what they emphasize and focus on.

Unquintessential leaders always have themselves – how things affect them, how they are treated, how they are perceived, how important they are, and how respected they are – as their primary emphasis and focus. “It’s all about me” is the message they send out over and over again.

Quintessential leaders rarely even think about themselves except within the framework of the team, and their emphasis and focus is always on goals. That means an almost-parallel emphasis and focus is on their teams. Because the team as a unit accomplishes goals. So the welfare of quintessential leaders’ teams is always directly tied to the accomplishment of the teams’ goals. 

The last key difference between people who are quintessential leaders and those who are not is in how they communicate.

Unquintessential leaders overarchingly communicate using language that threatens and intimidates. Most of the time, it’s obvious and in your face, But there’s an interesting phenomenon that occurs sometimes: the threats and intimidation are couched as a sincere desire to help, but when seen as a whole, it becomes obvious what they actually are.

Communication is an area where quintessential leaders tend to be very good. They say what they mean and they mean what they say. However, quintessential leaders always use language that encourages and motivates, even when they’re correcting a problem or coaching a team member whose performance needs to improve. 

The thought I’ll leave you with today requires looking in the mirror at ourselves instead of through the window at everybody else.

Let’s take these key areas and see which side of the equation we fall on. We may be quintessential leaders in all but one of them. Or we may be quintessential leaders in half of them. Or we may be quintessential leaders in less than half of them.

Recognizing and acknowledging honestly where we are is the first step to change. None of us are perfect. None of us are not guilty, somewhere in the course of our lives, of being unquintessential leaders. That includes me.

But just because we were – or maybe still are in some areas – doesn’t mean that we have to stay there. There’s no time like today to start the process of change.

And it is a process. We didn’t get here overnight and we won’t change from where we are overnight.

But we commit to change and we start taking steps forward to put that into action.

There will be falls. There will be setbacks. There may even be a few disasters along the way.

But the key to successful change is to get back up each time and start moving forward again.

If we fall and don’t get up, or if we decide it’s just too hard and too much work and we quit, then we have failed in reaching our potential and our goal of being quintessential leaders. Let’s not fail!

These value-priced quintessential leadership eBooks are available for download on The Quintessential Leader blog’s business website:

Building Trust and Being TrustworthyBuilding Trust and Being Trustworthy is also available from Amazon in print and Kindle versions.

If you don’t read another book this year, I highly recommend that you read Building Trust and Being Trustworthy. These are not just leadership or quintessential leadership principles. These are essential life principles that each of us should be incorporating into who we are and who we are becoming. Each of us. You. Me. Our children. Our grandchildren. Because we are all current quintessential leaders and we are responsible for cultivating, mentoring, and growing future quintessential leaders.

A mother shared these words with me after reading Building Trust and Being Trustworthy: “Just finished reading this book….EXCELLENT! In fact I’m going to make it a required read for my girls this year! Mine’s all marked in and highlighted…so I may have to get a new copy for them! Thank you, Sandra, for all the time and effort you put into this book or manual for life!”

Building Trust and Being Trustworthy is written for all of us in quintessential leadership positions: leaders of organizations, leaders of business units, leaders of teams, leaders of education, leaders of congregations, leaders of social organizations, leaders of civic organizations, leaders of families, leaders of ourselves, and those we lead.

I have worked with one person who was a quintessential leader. The next post will be about that person and how grateful I am that our paths intersected early in my career, because I learned a lot from him not only about what quintessential leadership looks like in practice, but also about having the highest standards of integrity and practicing what a person says he or she believes.

The rest of the people in leadership positions throughout my career so far have been managers (and not stellar in even that arena) and non-quintessential leaders. Some were decent people personally, but had no leadership skills. Others were not decent people personally and also had no leadership skills. As I’ve sorted through the names, faces, and experiences, contrasting and comparing them all, one person leads the way in non-quintessential leadership and I will point out the areas in which this became glaringly obvious.

You may recognize these characteristics in someone you know and/or have worked with. And the more of these symptoms that are evident, the more toxic the work environment and the lower the morale will be. If you are experiencing burn-out and all that encompasses, then you probably have a non-quintessential leader like this.

He had a reputation when I got hired and I quickly heard that he was a “yes” man, a suck-up to those above him – and a tyrant to those who worked for him, and wishy-washy, going with whatever the prevailing winds moved the executive leadership of the organization, which left his teams in constant disarray.

Ironically, he did not want me to be hired because he thought I was too assertive and too committed to changing things drastically. In the conservative mindset of the organization, change was viewed with suspicion and resistance, and if anything did actually change (very few of the fundamental changes that needed to be made to become efficient, effective, and productive were made while I was there or have been made since), it was only after going through layers and layers of committees, organizational red tape, and many hoops held up by the executive staff to jump there. Change – or the attempt to change – was thoroughly exhausting and was mostly an exercise in futility.

He was ignored (and I didn’t find this out until later, but I realistically know that it was only a small contributor to the tenor of the relationship he and I had, because I know I shared the same kind of relationship with him in general that all his other team leaders did) and the CTO, who liked me personally and professionally and wanted someone who would shake things up in a positive and productive way, made the offer of employment to me, which I accepted.

As I began the job and was observing, evaluating, and listening to my team members and my peers, I also observed, evaluated, and listened to those who were responsible for overseeing all of us. The first thing I noticed about this man was that he had gotten where he was not because he was qualified for a leadership position, but because he was skilled in playing the elaborate political games this organization reeked with. He ingratiated himself with the people who wielded power in their respective business units and who had the unqualified support of the CEO.

They were like gods to him and he bowed at their altars regularly, slavishly acquiescing to their every whim and demand, whether it made sense or not, was reasonable or not, was right or not, to the exclusion of the majority of the organization’s other employees.

In disputes in which they leveled charges against his employees, they were always true and right and his employees were always dishonest and wrong. He never checked facts and never investigated a situation before drawing a conclusion. He simply took their word at face value and supported them. Not once in all the time I was there did I ever see him support or go to bat for one of his employees.  Ever.

For context, it is important to note that the people he cowtowed to and curried favor with were an ivory-tower group of people who were prima donnas and consistently made mountains out of mole hills, if there was an issue, and if there was not an issue, but they decided a person wasn’t paying them enough attention or being subservient enough, they fabricated issues.

And this group of people was who he always threw his support behind. He was more interested in himself – and his career, because he was a lifer at this organization – than he ever was with his teams. And that was reinforced time and again.

His climb up the ladder was the result of his own self-centeredness and kissing up to the right people. He did not have any leadership skills and was not even that knowledgeable about the technical areas he was responsible for. But he had teams that made him look good and he never had any problem taking all the credit himself and promoting himself when things went right.

Equally, when things went wrong – both because of poor leadership on his part and because he constantly agreed to things that either couldn’t be done the way he agreed to them or couldn’t be done in the unrealistic timeframes he agreed to or both – he never took any responsibility, instead placing all the blame and castigation – he was quite adept at that – on his teams.

He was neither respected nor liked by any of us. But we were stuck with him, so we did our best to do our jobs in spite of him. It was never easy. The turnover rate of his teams was (and still is) the highest in the organization and yet no one ever questioned it nor did anything to address it. Those who’ve endured had other personal reasons for staying, but it has not been without a lot of grief and heartache and ulcers along the way.

Toward the end of my tenure there – when he’d crossed a major line by calling me into a “meeting,” closing the door, and proceeding to yell and scream at me, getting worked up into a full rage which had him standing banging on his desk and threatening me (I was alarmed enough for my physical safety that I was trying to assess how close I was to the door and whether I could get out fast enough if he came after me), and the administrative assistants sitting outside the door were “frightened” (I heard this after the fact) for me and went to alert the CTO, who shrugged and did nothing – I spelled it out to him (I refused to meet with him alone anymore after this meeting, and after three months, he couldn’t remember what he did and after I told him, could not understand why I was so upset about it).

Prior to my last annual performance review there, I wrote a document and gave it to him and told him we would not do my performance review until he had read it. Performance reviews with him were a nightmare. They lasted a full day and consisted of him haranguing all of us over our deficits. None of us ever got more than a cumulative “meets expectations,” and, of course, raises were tied to that, so none of us ever got much, if any, of a raise. Early on, after talking with one of my peers who also became a good friend (we were complete opposites in temperament and approaches, but together we made a very successful team), I discovered that our director blasted me for not doing more of what he criticized my peer for doing and he blasted my peer for not doing more of what he criticized me for doing. That’s an impossible situation to try to navigate.

He kept delaying my last performance review and one day I got a call from the CTO saying he wanted to meet with me. In the meeting, he said that my director had tried to read my paper and just couldn’t get through it. The CTO said it was hard for him to get through it, not because it wasn’t well-written, but because it presented a lot of information in a “dense,” high-level way that, although it was completely understandable, required a higher level of intelligence and capability than this director had. I then aired my professional grievances against him and the CTO’s response was disappointing. He said that this director had a “limited range of responses” and it was my responsibility to just deal with it.

By then, I was seriously pursuing other career opportunities, so I just walked out and finally did the performance review, which netted me the usual “meets expectations.”

When I submitted my “burn-no-bridges” resignation letter to this director, he was genuinely surprised. He was so enmeshed in the organizational mindset of “you stay here until you die or are fired (which rarely happened)” that he could not wrap his brain around the fact that someone would actually leave by choice. He did not ask me why I was leaving, nor did he express any regret (and although 200 or so people showed up at my going-away party, he did not). My last action of significance, though, was making sure that the person I had groomed to replace me and who I knew would stand toe-to-toe with him just like I did in support of my team members (she was more charming and proficient verbally than I was and, amazingly, he liked her better than most) got my position. I left, knowing that although there was no leadership at the top, that my team members had a leader who was poised to become a quintessential leader.