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? rbrenRCSZReUaGYJMGCALner@ChacEFULUaUquKMrzolNoCanyon.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:
- Critical Thinking and Midnight Pizza
- When we notice patterns or coincidences, we draw conclusions about things we can't or didn't directly
observe. Sometimes the conclusions are right, and sometimes not. When they're not, organizations, careers,
and people can suffer. To be right more often, we must master critical thinking.
- When We Need a Little Help
- Sometimes we get in over our heads — too much work, work we don't understand, or even complex
politics. We can ask for help, but we often forget that we can. Even when we remember, we sometimes
hold back. Why is asking for help, or remembering that we can ask, so difficult? How can we make it easier?
- Emergency Problem Solving
- In emergencies, group problem solving is unusually challenging, especially if lives, careers, or companies
depend on finding a solution immediately. Here are some tips for members of teams that are solving problems
- Forward Backtracking
- The nastiest part about solving complex problems isn't their complexity. It's the feeling of being overwhelmed
when we realize we haven't a clue about how to get from where we are to where we need to be. Here's
one way to get a clue.
- Design Errors and Groupthink
- Design errors cause losses, lost opportunities, accidents, and injuries. Not all design errors are one-offs,
because their causes can be fundamental. Here's a first installment of an exploration of some fundamental
causes of design errors.
Forthcoming issues of Point Lookout
- Coming May 31: Unresponsive Suppliers: III
- When suppliers have a customer orientation, we can usually depend on them. But government suppliers are a special case. Available here and by RSS on May 31.
- And on June 7: The Knowledge One-Upmanship Game
- The Knowledge One-Upmanship Game is a pattern of group behavior in the form of a contest to determine which player knows the most arcane fact. It can seem like innocent fun, but it can disrupt a team's ability to collaborate. Available here and by RSS on June 7.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenbHoxiQIdDCncuBOzner@ChacZNUXJcfHLnEjREEHoCanyon.com or (617) 491-6289, 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, USD 11.95)
- Get 2003-4 in Why Dogs Wag (PDF, USD 11.95)
- Get 2005-6 in Loopy Things We Do (PDF, USD 11.95)
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, USD 11.95)
- Get 2009-10 in The Questions Not Asked (PDF, USD 11.95)
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, USD 28.99)
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
- Creating High Performance Virtual Teams
- Many people experience virtual teams as awkward, slow, and sometimes
frustrating. Even when most team members hail from the same nation or culture, and even when they all
speak the same language, geographic dispersion or the presence of employees from multiple enterprises
is often enough to exclude all possibility of high performance. The problem is that we lead, manage,
and support virtual teams in ways that are too much like the way we lead, manage, and support co-located
teams. In this program, Rick Brenner shows you how to change your approach to leading, managing, and
supporting virtual teams to achieve high performance using Simons' Four Spans model of high performance.
Read more about this program. Here's an upcoming date
for this program:
- Baci Grill, 134 Berlin
Road, Berlin, CT 06416: September 19,
Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- Baci Grill, 134 Berlin Road, Berlin, CT 06416: September 19, Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- The Race to the South Pole: Ten Lessons for Project Managers
- 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. Lessons abound. Read
more about this program. Here's an upcoming date for this program:
- CTCPA, 716 Brook Street,
Rocky Hill, CT 06067: September 20,
Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.
- CTCPA, 716 Brook Street, Rocky Hill, CT 06067: September 20, Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.