Bob Fires Assholes

Bob Fires Assholes… and you should too!

Bob’s a client, the chief executive of a fairly large company in the Northeast. His name is not really Bob, but he really is a client, and a recent experience prompted me to share this (with Bob’s permission).

At the beginning of my coaching engagement with Bob, I

conducted a 360-degree survey so we could get an idea of how others see him in his day to day activities and interactions. If you haven’t had a 360 survey—a real one—done for you, you should. It’s almost always eye-opening. And sometimes a bit scary.

But no one dies in the process, so you’ve got that going for you…

Anyway, while doing the 360 survey on Bob, I was privileged to meet and speak with many of the direct reports on his leadership team. Without getting into details that would make Bob (if he’s reading this) squeamish, the results were insightful and indicated he’s clearly respected. Mostly good things, and nothing really out of the ordinary.

Until I spoke with Jim (again, not his real name). Jim offered that Bob was direct, decisive, and had a low tolerance for incompetence. No real shocker, given Bob’s role. Then, he gave the “pièce de résistance” (that’s a copy-paste, I had no idea how to write that).

“Bob fires assholes,” he said.

So, that had me putting my pen down. “Do tell,” I replied.

It seems that even more than incompetence, Bob has a crushingly low tolerance for anyone, particularly in any sort of leadership role, “being an asshole.” The culture of this organization doesn’t support that kind of behavior, and given their size, the ripple effect of a single jerkazoid in the mix causes all sorts of problems. Problems that can easily, and more effectively, be avoided by just firing “the asshole.”

Admit it – you’ve read this with a slight grin and a knowing nod of the head. You know the assholes in your world, the people causing problems, discomfort and stress for others, and you know the ones that should be whacked.

So whack ‘em.

Performance challenges we can deal with. We coach, mentor, advise, bring resources to bear to help someone well-intentioned up their performance game. That’s as it should be, so don’t stop that.

But behavior issues, particularly in leadership, should be dealt with sharply, definitively and immediately. The impact is just too big on the organization. You know that already, so suck it up and do what needs to be done.

Bob fires assholes. Be like Bob.

Team-Based Leader Development: Why together is better…

Team-Based Leader Development

Educating executives, managers, supervisors and other leaders remains a major concern for companies eager to keep their organizations afloat or even thriving in a challenging economic environment. Frankly, the limiting factor for most organizations continues to be leadership.

Leader development is not a new concept.  It continues, however, to be practiced in ways that – at best – do little to develop successful leaders and – at worst – damage functional relationships by allowing learning to exist in silos and independent “vacuums.”

The problem is not content. Adequate topical content is a dime-a-dozen and represents time-tested applications and concepts that have not changed much in a couple of millennia. Any of several firms create and publish reasonably valid content.

The principal challenge around effective development is relevancy. The content mentioned above is generic and must be made relevant for a specific functional or hierarchical group, within a specific organization. Then, when properly facilitated, we can at least hope to successfully develop a group of leaders.

The biggest issue, though, in effectively developing a group, team, gaggle, or flock of leaders is making sure they all learn the same things, the same way, and in the same context. Further, they should be able to test relevant applications and concepts together, for best learning and application.

Enter Team-Based Leader Development.

Now, I’m not speaking of team-building, per se, nor am I talking about campfires, challenge/ropes courses, falling-backward trust exercises, or other hardly-effective methods of development.

Those have value in team-bonding, but not real team development. And no, bonding and development are not the same things… in fact, it’s not actually a team just because you call it a team. See our article on The First rule of the Leadership Team.

I’m simply talking about developing a team or group of leaders at the same time, together. At our firm, we see more and more organizations wanting – needing – content specific for their groups; you just can’t get there when sending people out to some public session or seminar trying to be all things to all people.

You need your leaders developed together, learning applications and concepts relevant to your organization. By using team-based leader development, all leaders of a particular level or function learn these things at the same time, in the same room, using each other as learning tools.

The advantages of this approach should be obvious, and include demonstrated successes in:

  1. Improving communication flow within the team and out to the organization. This can occur naturally, and in a less stressful, facilitated environment. Conversations like this…
  • …benefit the organization, by providing calm discussions among leaders of similar hierarchical or functional levels, about just about anything important occurring in the organization today, and
  • …benefit the specific leaders involved, as they not only are discussing new learnings and applications, but they now have the opportunity to discuss things not normally discussed.

For example, without a safer venue, how many mid or senior-level managers would ask a peer “Hey, John, what’s the best way for me to resolve a conflict in my department?”  Or “Say, Susan, I’m having some issues in driving empowerment to my hourly employees – any suggestions?”

I’m guessing those conversations/questions, in the midst of our brutally hectic workdays, would be damned rare.

  1. Fostering mutual accountability for behaviors and results. One of the biggest advantages in having all these leaders in one location discussing the same things is that accountabilities can become institutionalized. It’s one thing to make a casual mention in the hallway; another thing altogether to commit to a group today, then speak with them a month or so later about your progress.

Also, this close-in work environment creates team ground rules that foster cohesion; if we agree in a group that behind-the-back caucusing is not something we’ll do, then having those back-stabbing conversations later just doesn’t feel right. Further, open communications in a facilitated setting inevitably translate to more open conversations in the open workplace.

  1. Faster assimilation, shared accountabilities, and increased understanding. This is the financial “why?” answered. Homogeneous participants learn faster, and the learning is more relevant. Therefore, an organization’s return on those development dollars is quicker, and the skills are more appropriate for the organization’s needs.

Understanding is accelerated; participants can discuss/explain with each other on various points and concepts, making sure that the meaning is the same for all, and that more realize how they can actually be used for leader success.

Participants in team-based development are able to identify their primary strengths quicker, and better understand how building on those contributes to higher levels of personal satisfaction and team success.

In short, all win. And the organization is better for it, all the time.

For additional insight, see the incredibly old-but-still-relevant Houston Business Journal’s feature article, Many companies now leaning toward team-oriented training.

(If link above doesn’t work, you can download pdf version at https://triangleperformance.com/wp-content/uploads/2023/01/HBJ-4-24-09.pdf.)

Stupid should hurt… Learn from your business mistakes.

stupid mistakes happen

I was recently involved (as a participant) in a strategic planning event; the facilitator, Alan Pue, was discussing many of the ways that planning — and its subsequent implementation — can go wrong.

In part of that commentary, he mentioned as an example a firm’s inability to adapt to a necessary change in the market, and how that inability adversely affected their performance. Alan wasn’t sympathetic to their plight, nor even empathetic. In fact, he made it clear that the problem was their own doing, and the resultant pain was of their own creation. They did it to themselves, have no one else to blame, and these lessons — though valuable — can be painful.

I agree.

When we act so dumb in business that we can’t get out of our own way, the resultant pain is our own doing. Sort of like touching a hot stove, we hopefully learn that we shouldn’t do that again.

Stupid should hurt.

Span of Control

What’s the optimum number of direct reports? How many people should a single manager have working for them? What we are referring to, of course, is “Span of Control,” and though there can be unique situations in some organizations, there are also decent historical guidelines.

Span of control isn’t simply dependent on individuals; it’s a basic limitation of all managers as it describes only their direct reports. Though any manager can control any number of people if there are enough levels in between, not so when it comes to direct reports.

Research (mostly military-based) has shown that a leader can directly control about three to six persons effectively. Additionally, the “relationships” among those supervised are as important as their actual number.

Managing four people who interact constantly might be harder than supervising five or six who work largely independently.

Generally, an executive (someone managing managers) should supervise a maximum of four or five people.

In real practice, you don’t have to be an expert to know if you’re in trouble with span of control. If you have more than half a dozen people reporting to you, it’s probably too many.

Even six could be too many if those six have consistent dealings with each other. The reason of course, is that in addition to managing relationships with each subordinate, managers have to get involved to an extent in their relationships with each other.

In simple terms, going from four to five direct reports, each with four direct reports of their own, potentially doubles your effective workload while increasing your output (productivity) capacity by only 20 percent.

If the people you supervise don’t interact, you can handle more of them.

Remember, too, that I’m discussing managerial span of control — managers managing managers. The numbers can increase significantly when managing individual contributors, particularly if highly skilled.

Just some thoughts…

Yooo-hoooo… Here I am!!

I didn’t disappear, just fell victim to the “wait until the end of the year to do that” disease.

I did, and it hurt. Traveled 6 out of the last 8 weeks out of the year… and remember, I’m one of those that doesn’t even like to travel. Simply brutal.

Further, with the growth of my business, I’ve been in something of a “hiring” mode, and that’s equally difficult to do — personally — while traveling.

Speaking of hiring… now that the new year is upon us, it’s a great time to do some cleaning up. And I mean the really difficult stuff. Have that performance conversation with the under-performing employee; hire that new sales or marketing pro; stop doing those things that don’t create enterprise value, and focus on those things that do.

I’ll be back soon with something to write home to mom about — thanks for tuning in.

Fish or Fowl?

Fish or fowl? Black or white? Day or night? We frequently find ourselves arguing whether human resources — as a function — is a true business partner in the strict financial sense or an employee advocate in the most liberal sense.

We’re wasting our time arguing semantics and methodology. Our resources are better spent discussing and acting on results.

First, let’s get some clear definitions and positioning. Is the human resources executive the do-all, end-all example of goodness and perfect behavior in the organization? Of course not. No single person or function is solely responsible for our organization’s’ moral compass. We are, however, the keeper of that compass, like it or not.

It’s simple logic, not the soft, intangible, transactional focus that many embrace. As human resource executives, we function as primary agents of organizational and behavior change — it’s what we do. As focal points for change, we become the de-facto example for that desired behavior. Sorry, but there is a modicum of “glass house” while leading human resources.

This doesn’t mean we are, necessarily, this “employee advocate” that so many speak about. It simply means that we must be exemplify and model the very behaviors we hope to see in an organization. Yes, to some degree, that’s every executive’s charge. But again, we may not be the moral compass of our organization, yet we are surely the keeper of same.

So what, you say? Here’s “what:” We must be true business partners in every sense. Our goals must always be the organization’s goals — no exceptions. Within legal and ethical boundaries, we should be prepared to do whatever is necessary to support our firm’s vision and direction with personal conviction. This is non-negotiable. In addition, we must always recognize that — like it or not — employees (managers and executives often included) look to us for positive, correct examples of desired behavior.

Let’s make sure we set that positive, correct example.

At C-Level Newsletter

Join our mailing list to receive our newsletter jam-packed with info, leadership tips, and fun musings.

You have successfully subscribed!