Executive Coach Executive CoachExecutive Coach
Scott Eblin offers his take on lessons in the news and his advice on your pressing leadership questions.

3 Reasons You Should Not Hire a Coach

ARCHIVES
Image via dotshock/Shutterstock.com

As an executive coach, I’ll be the first to acknowledge that the title of this post may not be the world’s best business development strategy. But, after more than 12 years as a coach, I think I’ve learned when it makes sense to hire a coach and when it doesn’t.

I’ll get to the reasons why you should hire a coach next week. This week, though, I want to start with three of my favorite reasons why you shouldn’t hire a coach. Through the school of hard knocks, I’ve learned that these reasons are sure fire predictors of a failed coaching engagement. That’s why when I hear one of them or sniff it out, I turn down the business.

Here they are:

1. It’s a reclamation project: There are times when I’m talking with an HR business partner or a leadership development specialist about a potential client and I’m compelled to ask the question, “Does this person have a future with your company?” The typical answer to that question is either a long pause or an acknowledgement that it’s dicey. I then politely suggest that coaching is not going to help that person. Coaching reclamation projects rarely work because the organization has already made up its mind. That leader is more or less cooked and coaching is the last play before they’re out the door. Why waste time and money with coaching?

2. My boss needs a coach: Last month, an HR director asked me to come in to meet with her and her company president because she thought he could benefit from coaching. I drove out to meet them and asked him to tell me his story. As we talked, I concluded that he was a great guy and probably a pretty strong leader. I also concluded that the person who really needed a coach was his boss, the CEO, not him. I made some suggestions about consultants who specialize in advising the founders of family run businesses and declined the work. I could have talked with him and coached him until the cows came home and it wouldn’t have made much of a difference. The person who really needed a coach was his boss and he wasn’t likely to hire one.

3. It’s the thing to do: Even in today’s cost conscious business environment, there are organizations where the norm is that leaders at a certain level and above all have a coach. Then there are organizations where a certain group of executives all get coaches as part of a leadership development initiative. I’m usually leery of coaching engagements that are there because it’s the thing to do. What I’m looking for is an executive who needs to get different results and understands that he or she will need to do some things differently to get the different results. One of my favorite little jokes is how many coaches does it take to change a light bulb? The answer is just one, but the light bulb has to really want to change. If a leader is interested in coaching just because it’s the thing to do, they’re not my kind of light bulb.

I have other reasons why you shouldn’t hire a coach. Those are just my top three. What are the other reasons you should not hire a coach?

Image via dotshock/Shutterstock.com

 

Executive coach Scott Eblin’s goal is to help you succeed at the next level of leadership. Throughout the week, he’ll offer his take on the leadership lessons in the news and his advice on your most pressing leadership questions. A former government executive, Scott is a graduate of Harvard’s Kennedy School of Government and is the author of The Next Level: What Insiders Know About Executive Success.

FROM OUR SPONSORS
JOIN THE DISCUSSION
Close [ x ] More from GovExec
 
 

Thank you for subscribing to newsletters from GovExec.com.
We think these reports might interest you:

  • Sponsored by G Suite

    Cross-Agency Teamwork, Anytime and Anywhere

    Dan McCrae, director of IT service delivery division, National Oceanic and Atmospheric Administration (NOAA)

    Download
  • Data-Centric Security vs. Database-Level Security

    Database-level encryption had its origins in the 1990s and early 2000s in response to very basic risks which largely revolved around the theft of servers, backup tapes and other physical-layer assets. As noted in Verizon’s 2014, Data Breach Investigations Report (DBIR)1, threats today are far more advanced and dangerous.

    Download
  • Federal IT Applications: Assessing Government's Core Drivers

    In order to better understand the current state of external and internal-facing agency workplace applications, Government Business Council (GBC) and Riverbed undertook an in-depth research study of federal employees. Overall, survey findings indicate that federal IT applications still face a gamut of challenges with regard to quality, reliability, and performance management.

    Download
  • PIV- I And Multifactor Authentication: The Best Defense for Federal Government Contractors

    This white paper explores NIST SP 800-171 and why compliance is critical to federal government contractors, especially those that work with the Department of Defense, as well as how leveraging PIV-I credentialing with multifactor authentication can be used as a defense against cyberattacks

    Download
  • Toward A More Innovative Government

    This research study aims to understand how state and local leaders regard their agency’s innovation efforts and what they are doing to overcome the challenges they face in successfully implementing these efforts.

    Download
  • From Volume to Value: UK’s NHS Digital Provides U.S. Healthcare Agencies A Roadmap For Value-Based Payment Models

    The U.S. healthcare industry is rapidly moving away from traditional fee-for-service models and towards value-based purchasing that reimburses physicians for quality of care in place of frequency of care.

    Download
  • GBC Flash Poll: Is Your Agency Safe?

    Federal leaders weigh in on the state of information security

    Download

When you download a report, your information may be shared with the underwriters of that document.