Whether it's an application user interface, a piece of equipment, a redesigned process, a marketing strategy, or whatever, when the unexpected occurs, we ask experts to explain how to proceed, or to fix the problem. When they can fix it, that's great, but when they can't, our first thoughts are usually that the expert we called is perhaps not expert enough. That's the easy case, so let's set it aside.
The more difficult case is that the experts we called are skilled enough, and might even be the best there is, but they're expert in the wrong field. How can this happen? What are the consequences? How can we prevent it?
Three important mechanisms can lead to calling the wrong expert.
- Limited authority to choose
- We can't always choose the expert we need. Budget restrictions, signature authority, and expert availability sometimes dictate the choice.
- Control mechanisms and expert availability can both generate risk. Account for this risk in risk plans.
- Incorrect diagnosis
- Sometimes we diagnose the problem incorrectly, either by honest mistake, or by overestimating our own diagnostic expertise.
- Unless you have diagnostic expertise, let experts perform the diagnosis.
- Undue influence by experts
- Sometimes an expert employee, consultant, or contractor recommends an expert, not on the basis of suitability, but as a favor to the expert being recommended, or because of constraints imposed by the recommender's employer.
- Validate recommendations for their objectivity.
Calling in the wrong expert can have serious consequences:
- Wasting time and resources
- Experts (and all people) are vulnerable to what psychologists call a mental set. If the problem solution lies within the expert's domain of expertise, nobody can address it better. But if the problem solution lies elsewhere, we waste time and resources eliminating all possible solutions within the expert's domain.
- Damaging assets
- Before the wrong experts deduce that the problem solution lies outside their domains of expertise, damage to assets is possible. The experts might even be the agents of the damage.
- The one benefit Sometimes we diagnose the problem
incorrectly, either by honest mistake,
or by overestimating our own
diagnostic expertiseof choosing the wrong expert is the potential to learn the importance of choosing the right expert. That learning can lead us to re-examine the expert-choosing process.
To prevent recurrences, consider two measures. First, avoid diagnosing problems. For example, if the computer can't communicate with the network, don't assume that the computer is defective, or that the network connection is defective. Simply report that the computer can't communicate with the network. Second, consider calling on an expert to tell you what kind of expert you need. In healthcare, this role has been called diagnostician, but the role is emerging in many fields. Before calling an expert, find a "diagnostician" for the relevant problem domain.
Are your projects always (or almost always) late and over budget? Are your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around. Read 52 Tips for Leaders of Project-Oriented Organizations, filled with tips and techniques for organizational leaders. Order Now!
Your comments are welcomeWould you like to see your comments posted here? rbrenmhXARWRMUvVyOdHlner@ChacxgDmtwOKrxnripPCoCanyon.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.
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.
More articles on Problem Solving and Creativity:
- Teamwork Myths: Conflict
- For many teams, conflict is uncomfortable or threatening. It's so unpleasant so often that many believe
that all conflict is bad — that it must be avoided, stifled, or at least managed. This is a myth.
Conflict, in its constructive forms, is essential to high performance.
- Backtracking in Incremental Problem Solving
- Incremental problem solving is fashionable these days. Whether called evolutionary, incremental, or
iterative, the approach entails unique risks. Managing those risks sometimes requires counterintuitive action.
- New Ideas: Judging
- When groups work together to solve problems, they eventually evaluate the ideas they generate. They
sometimes reject perfectly good ideas, while accepting some really boneheaded ones. How can we judge
new ideas more effectively?
- Virtual Brainstorming: I
- When we need to brainstorm, meeting virtually carries a risk that our results might be problematic.
Here's Part I of some steps to take to reduce the risk.
- Guidelines for Curmudgeon Teams
- The curmudgeon team is a subgroup of a larger team. Their job is to strengthen the team's conclusions
and results by raising thorny issues that cause the team to reconsider the path it's about to take.
In this way they help the team avoid dead ends and disasters.
Forthcoming issues of Point Lookout
- Coming September 25: Planning Disappointments
- When we plan projects, we make estimates of total costs and expected delivery dates. Often these estimates are so wrong — in the wrong direction — that we might as well be planning disappointments. Why is this? Available here and by RSS on September 25.
- And on October 2: Start Anywhere
- Group problem-solving sessions sometimes focus on where to begin, even when what we know about the problem is insufficient for making such decisions. In some cases, preliminary exploration of almost any aspect of the problem can be more helpful than debating what to explore. Available here and by RSS on October 2.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenmhXARWRMUvVyOdHlner@ChacxgDmtwOKrxnripPCoCanyon.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 words in your inbox in one hour. License any article from this Web site. More info
- The Race to the South Pole: Lessons in Leadership
On 14 December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough. But to organizational leaders, business analysts, project sponsors, and project managers, the story is fascinating. We'll use the history of this event to explore lessons in leadership and its application to organizational efforts. A fascinating and refreshing look at leadership from the vantage point of history. Read more about this program.
Here's a date for this program:
- Baldwin-Wallace University, 275 Eastland Road, Berea, Ohio
44017: November 7,
Kerzner Lecture Series/International Project Management Day, sponsored by Baldwin Wallace University and the Northeast Ohio Chapter of the Project Management Institute.
- Baldwin-Wallace University, 275 Eastland Road, Berea, Ohio 44017: November 7, Kerzner Lecture Series/International Project Management Day, sponsored by Baldwin Wallace University and the Northeast Ohio Chapter of the Project Management Institute. Register now.
- The Power Affect: How We Express Our Personal Power
Many people who possess real organizational power have a characteristic demeanor. It's the way they project their presence. I call this the power affect. Some people — call them power pretenders — adopt the power affect well before they attain significant organizational power. Unfortunately for their colleagues, and for their organizations, power pretenders can attain organizational power out of proportion to their merit or abilities. Understanding the power affect is therefore important for anyone who aims to attain power, or anyone who works with power pretenders. Read more about this program.