
Roald Amundsen, Helmer Hanssen, Sverre Hassel, and Oscar Wisting at the South Pole, December 16, 1911. The photographer was Olav Bjaaland.
When Amundsen and his party of eight all told departed their base camp for the pole on September 8, 1911, they departed too early. Forced to return in a hasty retreat on account of severe cold, they sustained some injuries from frostbite, and lost a few dogs. But the greatest damage came from the conflict that ensued, and the outright rebellion of Hjalmar Johansen, who openly questioned Amundsen's fitness as a leader. Back at base camp, Amundsen was able to treat the injuries, order equipment changes, and reconfigure the pole party to a smaller group, excluding Johansen. Also excluded was Kristrian Prestrud, who by then had realized that he was not up to the challenges of the polar journey. Amundsen also asked Jø,rgen Stubberud to go with Johansen and Prestrud on an Eastern expedition during the summer while the polar assault was underway. Finally, he carefully polled the party about the decision to depart. When the polar party departed on October 19, after several days of weather delays, they were a smaller party, better equipped and supplied, and starting almost six weeks deeper into Spring. These changes came about as a result of Amundsen's application of three of the practices advocated here: exclusion, inclusion, and retrospectives.
The photo is taken from Amundsen's book about the expedition, The South Pole.
When organizations decide to do something different from what they've been doing, the changes they undertake might involve changing more than what they do. Sometimes they must also restructure the way they make decisions. For example, the relative importance of software engineers and actuaries in insurance companies has changed significantly in the past 50 years. Although software engineering is more important today in such organizations than it once was, one can debate whether the political power of the people engaged in software engineering today parallels the importance of their profession in executing the mission of the organization.
Elective change in organizations sometimes exposes conflicts of interest between the interests of the organization and the interests of the people who must make the decision to change. In some cases, this conflict of interest is resolved not in the favor of the organization, but in favor of the personal interests of the decision makers. When that happens, the organization remains stuck on paths that lead to stagnation, contraction, and — possibly — bankruptcy.
What can we do about this? Here are four suggestions for enhancing decision quality.
- Recusal
- A pattern of participation in decisions that affect the personal interests of the decision makers is a performance issue. In politics and jurisprudence, excusing oneself from such participation is called recusal. The practice is rare even there, but with the exception of certain professional standards, it's almost totally absent from organizational life. Would not organizations that succeed in incorporating recusal into their decision processes gain significant advantages in decision quality?
- Inclusion
- The dual of recusal is inclusion. In most organizations, the same group of decision makers makes all the big decisions. From time to time, they do seek advice from specialists, but the specialists' role is advisory only — they rarely have decision authority. Are there not classes of decisions that would be improved by including some people who are customarily excluded from decision making?
- Decision process risk management
- Even among A pattern of participation in
decisions that affect the
personal interests of the
decision makers is
a performance issueorganizations that recognize the importance of risk management, risk management practice tends to emphasize what the organizations does, rather than how the organization makes decisions. Certainly all organizations make bad decisions once in a while. Can we not use risk management principles to protect ourselves from these mistakes? - Retrospectives
- Most important, perhaps, is a practice often called "lessons learned," or retrospectives. Retrospectives help us avoid repeating our own mistakes — or the mistakes of others. Although widely used in the lower reaches of the org chart, they are much less common at high levels. Why do you suppose that is? Could it be that requiring self-examination of others is easier than asking it of oneself?
Which of these practices do you recognize in the decision-making process of your own organization? Which are absent from it? First issue in this series
Top
Next Issue
Is your organization embroiled in Change? Are you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt? Read 101 Tips for Managing Change to learn how to survive, how to plan and how to execute change efforts to inspire real, passionate support. Order Now!
Your comments are welcome
Would you like to see your comments posted here? rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.comSend me your comments by email, or by Web form.About Point Lookout
Thank you for reading this article. I hope you enjoyed it and
found it useful, and that you'll consider recommending it to a friend.
This article in its entirety was written by a human being. No machine intelligence was involved in any way.
Point Lookout is a free weekly email newsletter. Browse the archive of past issues. Subscribe for free.
Support Point Lookout by joining the Friends of Point Lookout, as an individual or as an organization.
Do you face a complex interpersonal situation? Send it in, anonymously if you like, and I'll give you my two cents.
Related articles
More articles on Workplace Bullying:
Recalcitrant Collaborators
- Much of the work we do happens outside the context of a team. We collaborate with people in other departments,
other divisions, and other companies. When these collaborators are reluctant, resistive, or recalcitrant,
what can we do?
What You See Isn't Always What You Get
- We all engage in interpreting the behavior of others, usually without thinking much about it. Whenever
you notice yourself having a strong reaction to someone's behavior, consider the possibility that your
interpretation has outrun what you actually know.
Covert Inter-Team Noncooperation
- Occasionally teams find that they must cooperate with another team despite strong misgivings. Because
noncooperation isn't an option, they find covert ways to avoid cooperating. Here's a little catalog
of techniques of Covert Inter-Team Noncooperation.
Flexible Queue Management
- In meetings of 5-30 participants, managing the queue of contributors can be challenging. A strict first-in-first-out
order can cause confusion and waste time if important contributions are delayed. Some meetings need
more flexible queue management.
We Can 'Moneyball' Bullying
- Capturing data about incidents of bullying is helpful in creating awareness of the problem. But it's
like trying to drive a car by looking only in the rearview mirror. Forward-looking data that predicts
bullying incidents is also necessary.
See also Workplace Bullying and Workplace Bullying for more related articles.
Forthcoming issues of Point Lookout
Coming February 26: Devious Political Tactics: Bad Decisions
- When workplace politics influences the exchanges that lead to important organizational decisions, we sometimes make decisions for reasons other than the best interests of the organization. Recognizing these tactics can limit the risk of bad decisions. Available here and by RSS on February 26.
And on March 5: On Begging the Question
- Some of our most expensive wrong decisions have come about because we've tricked ourselves as we debated our options. The tricks sometimes arise from rhetorical fallacies that tangle our thinking. One of the trickiest is called Begging the Question. Available here and by RSS on March 5.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.com or (650) 787-6475, or toll-free in the continental US at (866) 378-5470.
Get the ebook!
Past issues of Point Lookout are available in six ebooks:
- Get 2001-2 in Geese Don't Land on Twigs (PDF, )
- Get 2003-4 in Why Dogs Wag (PDF, )
- Get 2005-6 in Loopy Things We Do (PDF, )
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
- Get 2009-10 in The Questions Not Asked (PDF, )
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )
Are you a writer, editor or publisher on deadline? Are you looking for an article that will get people talking and get compliments flying your way? You can have 500-1000 words in your inbox in one hour. License any article from this Web site. More info
Follow Rick





Recommend this issue to a friend
Send an email message to a friend
rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed
