Showing posts with label candor. Show all posts
Showing posts with label candor. Show all posts

Friday, January 04, 2008

Listening to dissent stops automatic thinking

Recently, I was working with a colleague on an order we were about to place with a supplier. We had had some issues with this supplier's performance, but they had been resolved. Anyway, that had been weeks earlier and I was looking ahead to what we needed next. One morning I got an email from my colleague answering some questions I had about the order.

But at the end of this email, he wrote something that really stopped me in my tracks. He wrote: should we continue using this supplier?

Despite the troubles, I hadn't even considered replacing them. As I spent the next few hours thinking about my colleague's question, it occurred to me that this is one of the values of dissent: it helps stop automatic thinking.

I was ready to go ahead and place the order and the response from my colleague made me stop and think. We talked, my colleague and I, and decided the order should go ahead, but in addition, we put together a list of the concerns we had, and asked the supplier to respond to them before the next order shipped. Looking back, I was glad my colleague raised his voice. And I was glad I listened.

spoken through SpinVox

Tuesday, October 02, 2007

The dissent-free organization: a worst practice

There's an excellent item by Garry Emmons in Harvard Business School's Working Knowledge site this week on candor--or more accurately, a lack of it, and what damage it can do to organizations. Here's a quote:


Consider the costs to organizations, large and small, when dissent does not or cannot surface: Abjuring rigorous debate about its merits, a youthful president John F. Kennedy essentially rubber-stamped a 1961 plan to invade Cuba at the Bay of Pigs, resulting in one of the biggest U.S. foreign policy fiascoes in decades. During a 1996 commercial expedition to the summit of Mt. Everest, several climbers, including two of the world's most experienced professionals, died in part because junior team members didn't speak up when their expert leaders ignored their own core operating principles surrounding safety. In 2003, NASA engineers were reluctant to challenge long-held beliefs that foam strikes incurred during the launch of the space shuttle Columbia posed no risk to its fuselage.


I can't count how many times in my career I have swallowed what I should have said--and I was always considered a loudmouth. How many mistakes could have been avoided? Lack of dissent is terribly frequent within senior management teams, where respect for (or fear of) the CEO, or an unwillingness to step into colleagues' sandboxes, results in meetings full of good feelings and no debates. (We know that X-Teams don't do this.)

Why do people shut down when they should pipe up? It's entirely rational. Writes Emmons:

[HBS Professor Amy] Edmondson says this reluctance to speak up stems variously from fears that superiors will not like the idea or that it may appear to criticize the status quo, which most people find reassuringly familiar or dangerous to challenge. Edmondson sums up the mental calculation this way: "The potential costs to me for speaking out seem reasonably certain and somewhat immediate; the potential benefit to me for speaking out seems rather uncertain and definitely long-range."

I've also been responsible for quashing dissent. Whether due to wishing to move faster, or to protect my turf, I didn't create a very good environment for those who disagreed with my ideas. It's appalling, in retrospect. It should be somewhat comforting that I've got a lot of company in this. But it's not.

So, to improve your business, get your team debating, disagreeing, even arguing. Here's former Medtronic CEO Bill George quoted in the Working Knowledge article:

During the decision-making process, George explains, this means asking probing questions and insisting that managers present each situation in objective terms, rather than with a positive spin.

"You must acknowledge and thank those who disagree by telling them that they made the discussion, and hence the ultimate decision, much better," George says. "You need to reward and promote the mavericks or else the organization will lose its creative edge. You try to create tension inside because the outside challenge is so great."

Monday, June 11, 2007

X-Teams create a safe environment for candid communication

I've been reading this book, "x-teams: how to build teams that lead, innovate and succeed," by Professors Deborah Ancona of MIT's Sloan School and Henrik Bresman of INSEAD, and, as I read on, its messages begin to seep in and I begin to realize that this is an excellent book that will earn a long-term place on my office bookshelf.

One message concerns candor in teams (see an earlier post on candid communication here). Great teams build a deep level of communication that is unfettered by fear of reprisal, concern about appearing stupid, or worry that one's point or question is too obvious to state. And such candor requires a safe environment for communication.

You may be saying, "Yeah, so what? How rare is that?"

In my experience, exceedingly rare. Most teams are very polite to each other. This reflects their organizations, in many of which politeness is raised to an art form. And those who speak up are viewed as poor team players. Wrap-up of a typical team meeting: "Does anyone have any objections to this approach?" Followed by silence.

"Silence equals assent" is perhaps the most incorrect statement in management. For when the meeting ends, small clusters of people gather and discuss what just happened, how dumb some ideas are, how they'll never work. It's a recipe for failure, repeated again and again.

One team profiled in the book, by contrast, held occasional meetings at the pub. Breaking down barriers that arise at the office, moving to an environment in which candid discourse is routine, allowed the team to get issues out on the table and create a true consensus for their next actions.

The three areas to encourage to build an environment for candid communication, according to Ancona and Bresman:

  • Psychological safety - acknowledging mistakes is routine, "quiet fixing," where an employee patches a problem without informing anyone, unthinkable.
  • Team reflection - the team periodically takes a break, looks back at what they've done, learns, and makes adjustments going forward.
  • Knowing what others know - the team shares enough so that they each create a database of others' knowledge, the better to know who to ask when something new comes up.