The early days of 2017 seem like a perfect time to talk about bad leaders and ways to survive them. I’m not exactly sure why this thought came to me, but what the heck — somehow it just feels appropriate.

“Survive,” by the way, doesn’t mean beating bad leaders at their own games. That just turns you into one of them. Survive means maintaining your dignity and professionalism while also succeeding … or at least not failing … in the environment bad leaders create.

As my graduate training was in evolutionary biology, we’ll make this a bestiary — a catalog of unfortunate critters. We’ll start off with …

Howler Monkeys

Howler monkeys are managers who holler a lot. There are two subspecies, Toddlers and Actors.

Toddlers throw tantrums whenever something doesn’t go their way. Why? Because … drumroll … it works. They bellow, and everyone in the vicinity scurries around, doing whatever they can to stop the screaming.

Toddlers learned tantrums work at about the same age they learned to speak. Nothing since then caused them to unlearn the behavior. Actors, in contrast, only pretend to lose their tempers. They learned how well screaming works by watching Toddlers in action, concluding that, as the philosopher said, ’tis better to give than to receive.

Howlers have three goals: To deflect responsibility for whatever happens to have gone wrong; to provoke behavior they can use against you later; and to establish their position in the organizational pecking order … the unofficial organizational chart that describes who kisses who, in what order, and where.

When dealing with a Howler, your worst course of action is to lose your own temper in return. Do this and you lose, because yelling is like the Highlander — there can be only one, and the Howler got there first.

Instead, calmly and deliberately walk away. As you gather your papers and stand up to depart, say something like, “Let me know when you’re ready to have a businesslike conversation and we’ll continue this discussion.”

Unless, that is, you report to the Howler. If you do:

  • Master the art of blandness. That is, ignore the Howler’s volume, tone, and pulsing forehead artery, and pay attention only to the content. Control your own body language, repeating to yourself, over and over, “I’m relaxed, professional, and unimpressed.”

To help you keep your cool, take notes ostentatiously, which emphasizes the close attention you’re paying to the serious issues the Howler is raising with such force and sincerity.

  • Take control at the optimal moment. What follows is for group situations. You’ll need equivalent tactics when you find yourself on the receiving end of one-on-one screaming. To take control:

When, and not until the Howler starts to repeat the same serious and important issues, raise your hand … not in the manner of a child who wants the teacher’s attention, but palm forward, like a crossing guard who needs the pedestrian on the other side of the intersection to stop.

When you have the Howler’s attention, apologize for interrupting, then say something like, “If I understand correctly, we have three issues that need our immediate attention.” Stand up, move to the whiteboard, and write them down from your notes as you list them.

Then continue, “I have suggestions for the first two (if you do) — I think we should xxx. For the last, does anyone else have any thoughts on how we should deal with this?”

  • Document every episode as thoroughly as you can. Don’t plan on doing anything with it. But Howlers are often pretty good at scapegoating too, so you might need documentation if you find yourself on the receiving end of an unearned disciplinary action.
  • Speaking of which, redirect any and all attempts to assign blame by overtly taking it: “What’s our goal right now? If we need someone to take the blame, I’m happy to do this. Now … what do we need to do fix the problem and prevent it from recurring?”

But mostly, leave. Focus your energy on finding a different job with a better manager. Life, not to mention your career, is too short. The longer you live around Howler Monkeys, the more being howled at becomes your normal — you’ll turn into the sort of employee you wouldn’t hire; dispirited, unmotivated, apathetic, and with an ingrained habit of keeping your head down in the Whac-A-Mole game of organizational dynamics.

Or, even worse, you’ll become an Actor — you’ll have learned to lose your temper for fun and profit.

* * *

If this week is an indicator, it appears I’ll need a whole week’s worth of space for each bad leadership critter.

You’re invited to contribute. What I’d like from you are:

  • Species: A type of bad leader or manager, associated with an unpleasant creature, whether alive, extinct, or mythical. I’ll also consider unpleasant ecosystems if you come up with a nasty organization type instead.
  • Root Cause: What you think leads to the character flaws you’re describing.
  • Solution: What, in your personal experience, works to help an employee survive unscathed and without being mutated in the process.
  • Permission: This includes permission to give you credit for the idea, if you’d like that, or instructions not to. It also includes permission to use your ideas intact, or to modify both your thoughts and your writing as I see fit. Please don’t take offense if I do. Even if I like your writing that doesn’t mean it fits KJR. And if I disagree with your thinking … well, my name will be on the final result. I’ll do my best to give proper credit without burdening your good name with my opinions.

Somewhere in the business you support is a manager who needs to do things more effectively. The alternatives:

  • Shovel a request into the IT request queue.
  • Ask Clyde, who’s “good with PCs” to do something magical with Excel.
  • Bring in a local IT services company to build a system that helps do things more effectively.
  • Find some inexpensive off-the-shelf software that will help do things more effectively, then badger IT into allowing its installation.
  • Contract with a SaaS vendor whose software will help do things more effectively and don’t tell IT anything about it.
  • Sigh a great sigh and give up on making things happen more effectively.

The first bullet is The Right Way To Do Things.

The remaining bullets are all some form of end-user computing (EUC) or the dreaded shadow IT.

Except for the last bullet, that is. The Great Sigh is a key reason entrepreneurships are able to beat, or at least hold their own against their giant competitors.

Let’s add a dimension to this mess exciting array of alternatives: The backbone and hub of your enterprise technical architecture is one of the major commercial ERP suites. What the manager needs would, most logically, be implemented as a customization to one of the ERP suite’s modules.

Nope. Can’t have that. So option #1 — the right way to do things — is off the table, leaving only end-user computing (EUC), Shadow IT, or sighing deep sighs on the table for our sadly un-mythical manager to choose from.

Compared to the rest of the population, KJR’s readers are, disproportionately, metrics nerds, so let’s add a nerdy metrical dimension as well.

The metrics your average business manager cares about in this situation are, in descending order of importance:
1. Cycle time: Start the stopwatch the moment the manager first develops a reasonably clear idea of what’s needed. Stop it when the software is in production and the manager’s employees are doing things the new way. More than anything else, managers want this cycle time to be short.
2. Quality: No, not being bug free, although that’s nice too. Quality isn’t just the absence of defects. It’s also adherence to specifications – whether the software does what the manager needs it to do. By this definition, the plain-vanilla version of the ERP suite’s module is a low-quality solution. It doesn’t do what the manager needs it to do, because if it did, the manager wouldn’t be submitting the request. Q.E.D.
3. Fixed cost: This is the initial spend – how much the manager will have to pay for the solution. This matters because above a certain amount the software becomes a capital acquisition, which means the manager would have to go through the company’s CapEx approval process … a governance process that makes the IT request queue seem downright friendly and inviting in comparison.
IT’s priorities, presumably reflected in your company’s IT request governance, are quite different, usually along the lines of:

1. Financial Value: Amortize the fixed project costs over some reasonable number of useful years of software service. Add the expected cost of ongoing maintenance. Subtract from the business benefits that will come from doing things the new way. Divide by total cost to turn the result into a percentage. (Yes, yes, multiply by 100. Don’t be pedantic. Oh, I forgot — you’re a metrics nerd too. Okay.)

If the result is a positive number, rank it against all the other requests that have to compete for IT’s time and attention.

2. Political Value: Don’t be shocked. Also, don’t be outraged. The Financial Value undervalues a lot of what are, in polite company, called “intangible benefits.” (In less polite company they’re called “warm fuzzies”; also, “Don’t be ridiculous!”)

As minor matters like customer satisfaction usually fall into the intangibles bucket, there’s often value in political value — for someone standing up for what matters most, even if it’s hard to put a number to it.

3. Strategic Value: Some projects are part of the strategic plan — they advance the strategy. Others aren’t part of the plan but they are consistent with strategic intent. There are no others — any manager worth his or her salt knows how to write the obligatory two-paragraph account of how their pet project fits into the company strategy.

Compare the two sets of priorities and it should be clear why, for most managers, and especially for smaller efforts, EUC and shadow IT are the preferred ways to go.

Doing things the so-called right way might make a manager a good corporate citizen.

But EUC and shadow IT are what get the annual bonus.