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? rbrenLzQdGHAHLHPEKVkxner@ChacfqqTmZCFvfjuAAbjoCanyon.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:
- Knowing Where You're Going
- Groups that can't even agree on what to do can often find themselves debating about how
to do it. Here are some simple things to remember to help you focus on defining the goal.
- Ten Tactics for Tough Times: I
- When you find yourself in a tough spot politically, what can you do? Most of us obsess about the situation
for a while, and then if we still have time to act, we do what seems best. Here's Part I of a set of
approaches that can organize your thinking and shorten the obsessing.
- Problem-Solving Ambassadors
- In dispersed teams, we often hold meetings to which we send delegations to work out issues of mutual
interest. These working sessions are a mix of problem solving and negotiation. People who are masters
of both are problem-solving ambassadors, and they're especially valuable to dispersed or global teams.
- New Ideas: Generation
- When groups work together to solve problems, they employ three processes repeatedly: they generate ideas,
they judge those ideas, and they experiment with those ideas. We first examine idea generation.
- Strategic Waiting
- Time can be a tool. Letting time pass can be a strategy for resolving problems or getting out of tight
places. Waiting is an often-overlooked strategic option.
Forthcoming issues of Point Lookout
- Coming May 23: Narcissistic Behavior at Work: IX
- An arrogant demeanor is widely viewed as a hallmark of the narcissist. But truly narcissistic arrogance is off the charts. It's something beyond the merely annoying arrogance of a sometimes-obnoxious individual. What is narcissistic arrogance and how can we cope with it? Available here and by RSS on May 23.
- And on May 30: Chronic Peer Interrupters: I
- When making contributions to meeting discussions, we're sometimes interrupted. Often, the interruption is beneficial and saves time. But some people constantly interrupt their peers or near peers, disrespectfully, in a pattern that compromises meeting outcomes. How can we deal with chronic peer interrupters? Available here and by RSS on May 30.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenceBcArehDgQTjOanner@ChacAskyTdUMXbNAZOiroCanyon.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, 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
- Technical Debt Management: Making the Business Case
- This program
outlines the steps necessary for deploying a program for rational management of technical debt. For
many organizations, adopting a program for rationally managing technical debt entails organizational
change. And unlike some organizational changes, this one touches almost everyone in the organization,
because technical debt isn't merely a technical problem. Technical debt manifests itself in technological
assets, to be sure, but its causes are rarely isolated to the behavior and decisions of engineers. We
can't resolve the problem of chronically excessive levels of technical debt by changing the behavior
of engineers alone. Technical debt is the symptom, not the problem. In this program we outline the essential
elements of an effective business case for adopting a rational technical debt management program. But
this business case, unlike many business cases, cannot be captured in a document. We must make the case
not only at the leadership level of the organization, but also at the level of the individual contributor.
Everyone must understand. Everyone must contribute. We explore five issues that make technical debt
so difficult to manage, and develop five guidelines for designing technical debt management strategies
for the modern enterprise. Read more about
this program. Here's a date for this program:
- Wyndham Springfield City Centre, 700 East Adams Street, Springfield,
Illinois 62701: June 12,
Monthly Meeting, Central
Illinois Chapter of the Project Management Institute. Register now.
- Wyndham Springfield City Centre, 700 East Adams Street, Springfield, Illinois 62701: June 12, Monthly Meeting, Central Illinois Chapter of the Project Management Institute. Register now.
- The Race to the South Pole: The Power of Agile Development
- 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. Lessons abound. Among the more important
lessons are those that demonstrate the power of the agile approach to project management and product
development. Read more about this program. Here's
a date for this program:
- Fifth Third Bank, 5717 Madison Road, Cincinnati, OH 45227:
Monthly Meeting, Cincinnati
chapter of the International Institute of Business Analysis. Register now.
- Fifth Third Bank, 5717 Madison Road, Cincinnati, OH 45227: July 17, Monthly Meeting, Cincinnati chapter of the International Institute of Business Analysis. 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.