Epic Management Fails

“who’s able here to honestly say ‘I have a great boss’?” two hands raised… 320 persons in the room… Via Daniel Glazman on Twitter

Although I always identify myself as a technologist, I’ve been managing people for a while and that is the primary focus of my full-time work. Managing people is an art, not a science. It’s very hard work, and I didn’t completely understand this before becoming a manager. Honestly, I don’t think most people — even managers — understand how hard of a job this can be.

I think that I’ve become a pretty good manager — with time and experience, with feedback and mentoring. There were times when I wasn’t so great, though. In an attempt at radical honesty (hat tip to Erica O’Grady), here is a list of my epic management fails and what I’ve learned from them.

Do you recognize any of these epic fails, either personally or in a manager you’ve worked with? Does your organization have a strong culture of coaching and mentoring managers to prevent against these and other fails? Share your story below for others to learn from. I’ll share my epic wins later!

Comments

  1. Wonderful post and humbling as well – Though I haven’t been in a staff management role in 7 or 8 years I’ve recently been thrown into a more educational role and I see strong parallels as I deal with my students. Failure in some level should probably be exepcted, it’s just a nice reminder to hear others are in the same boat and that there should be some ackowlwdgement from the top (so those staffers or students don’t always think it’s their fault).

  2. Thanks, Chris! I have a slew of epic teaching fail as well, and you’re right, much of that list would overlap with this one. But I can only admit so much fail at a time. ;)

  3. Two comments based on ~3 years managing at a large web outfit and another 6 or so off and on at various small or startup outfits:

    • Knowing your directs’ goals — in this job, in their career, and in the broader context of their life (i.e. do they love their career or is it just a means to an end) — can cover a lot of other ills, and makes many of the difficult situations easier. Knowing your team’s goals can help you keep them motivated when the work gets dull, or through layoffs, or reorgs, or pay freezes. It can keep you prepared for those 1:1s (‘so, you said you wanted to do more of X this year, how do you think that’s going?’). It can even help with hiring decisions: you want a mix of people with different priorities so everyone isn’t competing for the same promotion/raise/project. Your team members’ individual goals are probably the most important things you need to know as a manager.

    • Spolsky has it dead on when it comes to hiring: after the interview, when it’s time to make the hire/no hire call, it’s a binary choice: ‘yes’ or ‘no’. No middle gound. ‘Yes, but’ = ‘no’. ‘Yes, if’ = ‘no’. ‘Yes in a different role’ = ‘no’. No exceptions. The only bad hires I’ve made — and I’ve made a few betting on potential rather than demonstrated ability — were those I had reservations on, where it was ‘yes, but’. Or ‘yes, because we really need someone now’.

    That last, in particular, is insidious: never, ever, ever hire just because ‘we need someone right now darnit!‘ That’s what contractors are for. They may be a big, ugly number on the wrong line of the balance sheet now, but they are far, far cheaper than a wrong hire in the medium–long term. As much as 10x or more depending on the situation.

    • My biggest (recent) FAIL: own your decisions, even when they’re not yours. Particularly at big companies, you will be forced to implement policies or (forfend!) mete out negative feedback/’discipline’ with which you disagree. Tough. That’s why you get paid more than your team, why you get a different bonus scheme, or a phone, or whatever perks your company gives you. When you accepted the promotion (or the job), you accepted the responsibility of carrying upper management’s (or the board members’ or whomever’s) water. You need to do it, and do it wholeheartedly. By all means, push back as hard as you can against decisions with which you disagree, but do it in private, not in front of your team. Once the decision is made, when you’ve fought the good fight and lost, you can’t kvetch about how you don’t like it or are being forced into it. You need to sell it to the team. That’s your job. And if you can’t do your job, then it’s time to find a new one.

    • And my second biggest: trust your team. Even if your gut says otherwise. You trusted these people enough to hire them, now trust them to know and do their jobs (new teams you’re taking over but didn’t choose are different; they need to earn your trust and vice versa). When another manager (even your boss) raises concerns about the team — and I mean the team as a whole, not just one individual; one individual is always fallible — trust the team's assessment. Or at the very least, use it as your starting point for investigating further, and don't stop digging (or learning — you may need to learn new technical skills if you're a bit rusty) until you now enough to be absolutely 100% certain your team is wrong. Then investigate a bit more to be sure. Really. The thing that will sink you as a manager fastest is if you lose the trust of your team, and the surest way to lose that is to fail to support them when they're right. Most always, if the team really does have a problem they need to correct they know it and they may grouse, but it’ll be defensive and half-hearted.

    Squaring those last two is, of course, a bitch. That’s why management is such a hard job: sometimes, there really is no way to win.