Site icon Kellblog

Defending Weak People

I had lunch last week with a senior executive at a major software vendor.  I asked him how one of my former (non-MarkLogic) colleagues was doing.  His reply:

“Not so well.  Expectations were set very high because of his past experience and in the end he didn’t hire strong direct reports and build a strong organization.  Worse yet, when he was challenged on the quality of those people, instead of accepting that there may have been problems, he defended them.  And defending weak people is the beginning of the death cycle.”

The last sentence caught my attention because it’s a key decision that every manager must make.  When your management comes to you and says “your people are weak,” I think you are faced with two choices.

  1. Say “no they are not” and defend them.
  2. Say “perhaps they are” and upgrade them.

You must be aware that by simply having this conversation that you are, de facto, in deep pucky because a key part of your job is to build a strong organization.  Thus this is one of those conversations that you’re never supposed to have, much like one with your spouse on “what we’re going to do about your dalliance.”

As a contrarian and as someone who thinks he sets high people standards, my natural response is to pick the first option.  But that is de facto perilous because if your management is telling you that your people are weak, then they have presumably already put some thought to it and made up their mind.

It’s basically paradoxical because defending your people opens you to the “worse yet” argument (as in, “and worse yet, poor Joe can’t even see the problem.”)  But not defending people is to admit that they are weak and thus that you have failed to do your job in building a strong organization.  See prior comment about this being a conversation you don’t want to have.

But, as a manager, you’re probably going to have it one day and the higher you are in your organization, the more likely this conversation is to arise.  Why?  Because the higher up you the more everything below you becomes an abstraction.  Much of the abstraction rolls nicely into numbers such as sales, gross margin, and sales/head or profit/head.  But the one thing that doesn’t is your direct reports.

So, given that this is a “have you stopped beating your wife” conversation, I’d argue the best thing you can do is to avoid it.  How?  Through a number of means:

Exit mobile version