I’m just sayin’…

First, that phrase for this post — “I’m just sayin’,” drives me nuts. I hate it. Now that I feel better for sharing…

A diversity consulting firm called The Novations Group, apparently surveyed a couple thousand managers, and concluded that senior managers were poor communicators. For this, they seem to want acclaim…

Survey respondents blamed senior management for (in order of survey popularity):

1. Relying too much on e-mail.

2. Assuming a single message is enough.

3. Having no feedback loop in place.

4. Messages lacking clarity.

To this, I say “hmmmm…”

Nonetheless, there is some truth here.

We all rely too much on email. Email is great for simple information/data sharing. It breaks down when we try to have conversations, include emotion, or the worst: we try to manage by email.

Walk down the hall or pick up the damned phone. Email is the worst medium on the planet for any communication requiring acknowledged understanding, purposeful dialog, or meaning other than the simple written word. There is no defined ‘subtlety’ in emails. And managers shouldn’t use it as a proxy.

Another pox on communication occurred while we were gutting mid-management from organizations. In flattening org charts, we forgot that most on-the-ground communications with employees was done with middle managers. Today, they are either extinct or a bit harried from the evolution of their jobs.

Further, much of what we as senior leaders do has at least a modicum of confidentiality. Next thing you know, we’re acting like everything we say and do is some state secret.

It ain’t.

The problem, of course, is in the absence of communication, our employees fill in all the details, blanks, and relevant information themselves. From spotty knowledge, connecting rumor dots, or simply making it up as they go. None bodes well for us while trying to lead an organization in this age.

Next week, I’ll post some tips and techniques for communications that, though maybe not necessarily “easy,” they probably won’t leave visible scars.

Until then,

Leadership Laws: #3

In this and 2 remaining blog entries, I’m expanding on the “5 Irrefutable Laws of Leadership” I outlined in a recent article.

This third law is a reminder that development is essential for employee growth, and for your own well-being. In other words, it’s both selfish and generous; making someone else smarter while you do less work. This is a good thing, eh?

Law #3. If you always answer employee’s every question, you’ll forever be answering employees’ every question.

Questions are teaching moments — don’t rob employees of the opportunity.

Sounds trite, and I don’t mean it to (ok, maybe I mean it to be a little trite). If an employee is asking because they’re stupid, get rid of the employee. If they are a decent employee asking because they do not know, then teach them.

Next time, they’ll know how to do it — or at least the thought process behind it — and you won’t have to. How’s that for planned efficiency??

Now, you have time to go do something important. And to answer in advance: No, answering every employee’s every question is not something important you should be doing. If you’re doing that, you may as well just do it yourself…

Now that sounds fun, eh?

Let’s Benchmark!

I have a better idea… Let’s not.

Personally, I think “benchmarking,” much like its sister phrase, “best practices,” means “waste of time.” Time better spent analyzing and improving your internal processes.

Benchmarking is supposed to mean looking inside other organizations, and comparing their results, methodology and metrics of a practice or process with your own. Supposedly, this has some meaning to us, and we can use that to adjust and improve our own processes and practices.

Therein lies the problem — our processes and practices, not theirs. We cannot simply reach into another organization — similar in scope or not — and extricate several of their unique processes to overlay on our organization. Taken so out of context, we may actually do much more harm than good.

One size doesn’t fit all, what works for you may not for me, templates are useless… pick a phrase, they all apply. Studying another’s process to determine if there are pieces of it that you can use, within your own, well-defined structure and practice, may indeed have some value. Benchmarking entire processes, practices, and methodologies does not.

Sure, compare all you like. But take the results of that comparison and ask why there is a variance. There are so many variables within organziations — people, structure, geographic, cultural, you name it… a firm can have “better” metrics than you, but not necessarily execute that particular process nearly as well.

Don’t benchmark… analyze and improve.

But, that’s just me…

Exceptions vs. Precedents

Human Resources needs to get past this, “Do it for one, must do it for all” mentality. It’s just not true, and a lousy way to help a business succeed.

I regularly tell people this about precedents: “Yes, I’ll likely do the same thing, given the exact same circumstances, in the future.”

For example, if I allow an extra week of protected FMLA for a stellar employee in production with 6 years with the company, I may very well agree to do that same thing for the next “stellar employee in production with 6 years with the company.” Change a single parameter and the precedent doesn’t exist.

But even that isn’t the right answer, since decisions need to be made based on current business needs. I’m not trying to create a social system at work whereby all receive identical treatment. They won’t. I’ll do those things necessary, including making nondiscriminatory employment-related decisions, as the business needs dictate.

There’s all this talk about HR’s “seat at the table.” Want to get “kicked off the table” in a hurry? Adopt the inflexible, “Do for one, do for all” mindset. It has no place in business, in my opinion.

Cheers,

Leadership Laws: #2

In this and 3 subsequent blog entries, I’m expanding on the “5 Irrefutable Laws of Leadership” I outlined in a recent article.

The second law focuses on open communications; too often, usually in the misplaced interest of correctness or conflict-avoidance, we tap-dance around topics, subjects, and even direction. We assume — often incorrectly — that someone “knows what we mean,” though we didn’t come out and say it.

Law #2. If you want something specific done, say so specifically, using clear, plain language. Employees, generally, have some difficulty doing their basic jobs; adding “mind-reading” to their description is just plain unfair.

No hints, implications, or innuendos. Say what you want, and use English! Directness counts.

I was recently doing some coaching with a client executive who was lamenting the poor “listening skills” of his Operations VP. Seems he had told the VP that one of his director-level staffers was not fully competent, and that the VP should “do something about that person.”

3 days later, that VP fired that director. My client executive was shocked — he told me, “I told him to do something with her, you know, like coach, train, or develop. Maybe even warn her of her performance.” He said, “I didn’t tell him to fire her…”

The VP, of course, simply said, “The boss said ‘do something with her, so I did.”

“Problem fixed.”

Not really… I don’t need to tell those of you reading this the difficulty in replacing an experienced mid-level manager in a specific industry. Especially without even making an effort to change her performance or behavior in some way.

Of course, the senior executive felt his comments were sufficient… obviously, they were not. English would have prevented this misunderstanding… simply telling the VP that he should “improve her performance or behavior” would have been sufficient; perhaps even simply asking the VP what he’s done to work with the director would have jogged a reasonable conversation.

Instead, a miscommunication — caused solely by incomplete/indirect language — has created yet another “situation” at the company.

As if we didn’t already have enough to do, we go out creating challenges to deal with.

So, like the doctor when the patient says, “Doc, it hurts when I do ‘this,’ and the Doc says simply, “Stop doing that.”

Stop doing that.

Rippin’ Good Feedback!

— It’s not just the words…

WARNING: Colorful metaphors, including PG-13 language follows. Don’t read if easily offended since, generally, I try so very hard to never offend…!

So, I’ve got this client… (as my friends know, most of my really good stories start this way). Anyway…

I’m working with their leadership teams (multiple levels), and during a recent mid-manager session, one of the participants commented that it was great to have a “common language” for all the managers.

This, of course, is music to my consulting ears, so I ask him to elaborate.

He said well, we can discuss things now like “empowering employees,” “resolving conflict,” and “active listening,” and the term means something to us, as opposed to (in the past) not really being able to verbalize these concepts.

Now, I’m really jazzed, so I ask for specific examples. In retrospect, this could have been an error in judgment on my part… live and learn.

So, this participant then says, “Well, everyone now understands what we’re talking about — what we’re doing — even when getting “chewed out.” He says, “It’s not an “ass-ripping” anymore, it’s “feedback.”

“It’s not an ass-ripping any more, it’s feedback.” You gotta admit, that’s funny. I could hardly catch my breath I was laughing so hard.

After normal conversation resumed, however, it became clear that what he had said, though funny, was actually quite accurate. And it isn’t just a play on words.

Taken out of context, with no management or leadership process in place for continued communications and real feedback, an “ass-ripping” is just that. Used in the productive context of regular and frequent communications and clearly defined expectations, within a defined performance management process, it really is, now, “feedback.”

I learned a valuable lesson that day (well, TWO lessons if you count “don’t ask stupid questions like that” as a lesson): Words matter, because that’s how we frame situations within our environment. It’s not a simple play on words if the new frame of reference is different than the old.

This “common language” thing can really make sense.

How about in your organization?? Are you still “ass-ripping” or are you “providing feedback?”

Think about that.

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!