Skip to main content

Losing the Locker Room

For those of us who play, have played, or are fans of sports, there is a phrase that is used when a coach or player has lost the trust and/or respect of her/his teammates: Losing the Locker Room.

In the 2010 NFL season, Brad Childress lost his locker room. Some say that he lost it long before that, but it came to a head midway through November when he was fired from his job as the head coach of the Minnesota Vikings.

Poor decision making and the inability to effectively communicate cost him the respect of his team, the team owners, and the fans. "Without a foundation of trust and loyalty, Childress watched as his players reached near-mutinous levels at the first sign of adversity this season", wrote Kevin Seifert on ESPN.com.

It also resulted in an abysmal collapse of the team that, during the previous season, was a coin-toss away from advancing to the Superbowl. It resulted in failure.

Unfortunately, this phenomena is not limited to realm of sports. It exists in every profession. Once it occurs, it is often irreversible.

As Product Managers, a great deal of our job is achieving buy-in from colleagues across the organization, most of whom are managed by someone else. We have to be excellent communicators, solicitors of ideas, and be able to concisely articulate the goal, its purpose, and the tactics we intend to use to accomplish the goal. We need to lead with inspiration and earn the confidence of others.

Unfortunately, not everyone shares this view. Some people do not solicit ideas but instead impose their own ideas and fail to listen. Some people who do hold either managerial authority or political leverage within an organization wield it like a weapon, implying (or directly stating) that repercussions shall befall those who don't fall in line.

While these industrial-revolution era management tactics may still be effective in some enterprises, especially those in which the tasks are menial and/or straightforward, they fail miserably in contemporary professions that require analytical, critical, or creative thought. (For an excellent book on this topic, I recommend that you read Drive, by Daniel Pink.)

In a high-technology workplace, the vast majority of roles fall into the latter categorization. Product managers--and all managers, including executive leadership--must understand this and recognize that success will not be borne from mere persistence, insistence, or simply because you say it's important and that's that.

If you take this approach, the likelihood is that you will fail to get maximal results from your colleagues, lose their respect, and ultimately lose the locker room. It might not be immediate. You might squeeze out a few successes in the short-term. Even Childress won a couple of games before he was sacked.

But if you want sustained success, and you want to get the most from your teams, then it's crucial to communicate effectively, engender trust, always be ready to listen or help, solicit and give advice constructively, and always remember that you are working with peers, not mindless minions. To be an effective leader, you must have dedicated collaborators. To borrow a quote from the West Wing series: A leader without followers, is just a guy taking a walk.

Comments

Popular posts from this blog

Hiring: Scheduling Interviews

Interviewing candidates is never easy. There's a lot at stake . Many notable managers and companies will bloviate about their hiring processes; often in self aggrandizement but occasionally to share tidbits of wisdom. A successful hiring process requires that a lot of pieces be firmly in place. Corporate messaging. Job descriptions. Salary ranges. Benefits packages. Application process. Referral programs. The list goes on... One very important yet often overlooked item is scheduling, and that is the focus of this post. While interviewing a candidate recently, I was doing my routine pre-interview preparation and reviewed with whom and when the candidate had already spoken. To my confused dismay, I learned that the candidate had spoken to 5 people already on three separate days . I was to be the 6th interviewer (on day #4), and there was still one more interviewer scheduled for later that week. That's 5 distinct interview periods!!! After conducting the interview, I

OSX & Mac Office Team: Please Be Kind

Recently I opened a Word document from Outlook. I worked in it for a while, tracking changes, etc. Then I did a "Save As...". The prevous three Word documents I had saved automatically went to my Desktop. However, because this one originated in Outlook, I didn't notice that the destination folder was set to "Outlook Temp". Needless to say, I went looking for it. Lo and behold, Word didn't have any recollection of this being a recently-opened document. So I couldn't open it from Word. Very lame Word. Very lame . Suspecting something was amiss, I opened another document from Outlook and did a "Save As..." and then noticed that the save folder was set to "Outlook Temp". No problem, I thought. I'll just go to that folder and fetch my file. Actually, this turned out to be a problem. I searched in vain for "Outlook Temp" via Spotlight to no avail. I searched for the file name in Spotlight. Nothing. I then went back t

Improving Win Rates

Still here at the Gartner Local Briefing. In a session with Richard Fouts about customer win rates. Sharing Win/Loss Data Sales teams tend to advertise their wins, yet contain their losses. Why is this so? Q:  How many global IT companies conduct win/loss on an enterprise scale? Less than 5%? About 10%? About 20%? A: Less than 5% Why? CEOs and Sales people say "I know why we win/lose".  Some politics are touchy; people don't want you to expose what they did well/not (especially in competitive environments).  "I clicked the won/loss checkbox in Salesforce.com" One company evaluated their win/loss data. They looked at 140 wins, and 55 losses. Looking at this data, they noticed a correlation between the wins and the fact that they beat their competition to market with compelling announcements in over a third of the scenarios. An IT services firm attempted to sell a more sophisticated solution. Upon evaluation of the win/loss data, they fo