Josie stopped short, because she had just learned something that might break the impasse. She turned to Greg. "Wait a minute," she said. "Are you saying that you never use this system to review dormant accounts?"
Greg looked surprised. "Right," he began. "But I told you that two weeks ago in my office. What's the problem?"
"I don't remember it that way," Josie explained. "But it means that we can eliminate about 20% of the work."
Josie and Greg might never figure out how they got confused, but one partial cause might be related to Josie's approach to interviewing, and Greg's approach to being interviewed.
Sometimes we interview others to elicit critical information — to resolve an ambiguity, to solve a problem, to create a design or to develop requirements. Most sources are willing, even eager to help. Yet we often come away from the effort with incomplete or wrong information. What can we do to make this kind of interview more effective?
of the willing
effective strategyEffective interviews of the willing start with effective strategy. Here are some general principles that help.
- Prepare yourself
- Know what you want to uncover, and have a plan that will get there. Unless you're an expert, improvisational interviewing is unlikely to produce the results you seek.
- Eliminate presuppositions
- Presuppositions constrain responses. Contrast "How often do you use the system for viewing dormant accounts?" with "Do you use the system for viewing dormant accounts?" The former question presupposes the use. With the presupposition, responders who don't actually view dormant accounts might feel a "should" in the question.
- Use context-free questions
- A context-free question neither suggests its answer, nor biases the responder. For instance, "What's the customer's frame of mind?" is free of context. "Is the customer under time pressure?" is not.
- Ration your questions
- Even a willing source becomes less willing as the questions keep coming. Quotas vary from person to person, and some questions "expire" — they drop out of the quota — after varying amounts of time and intervening interactions.
- Beware repetition
- Asking about the same thing repeatedly, even when the questions aren't successive, can cause some sources to feel that they're under suspicion. They might become wary and guarded.
- Plan for post-interview analysis
- Review your results after each interview. Don't assume that you understood everything you heard the first time, or that you asked unambiguous questions.
- Exploit synergy and follow up
- Compare results from multiple sources, looking for discrepancies, re-enforcements and synergies. Look for what was not said by each responder. This process often generates a need to follow up for clarification.
The article you've been reading is an archived issue of Point Lookout, my weekly newsletter. I've been publishing it since January, 2001, free to all subscribers, over the Web, and via RSS. You can help keep it free by donating either as an individual or as an organization. You'll receive in return my sincere thanks — and the comfort of knowing that you've helped to propagate insights and perspectives that can help make our workplaces a little more human-friendly. More
Your comments are welcomeWould you like to see your comments posted here? rbrenWuFfZyLnuMCugnSrner@ChacUlBKiLRempChLFVWoCanyon.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 Effective Communication at Work:
- Discussus Interruptus
- You're chairing a meeting, and to your dismay, things get out of hand. People interrupt each other so
often that nobody can complete a thought, and some people dominate the meeting. What can you do?
- There Is No Rumor Mill
- Rumors about organizational intentions or expectations can depress productivity. Even when they're factually
false, rumors can be so powerful that they sometimes produce the results they predict. How can we manage
- Asking Clarifying Questions
- In a job interview, the interviewer asks you a question. You're unsure how to answer. You can blunder
ahead, or you can ask a clarifying question. What is a clarifying question, and when is it helpful to ask one?
- That Was a Yes-or-No Question: I
- In tense situations, one person might question another. As the respondent replies, the questioner interjects,
"That was a yes-or-no question." The intent is to trap the respondent. How does this work,
and how can the respondent escape the trap?
- Listening to Ramblers
- Ramblers are people who can't get to the point. They ramble, they get lost in detail, and listeners
can't follow their logic, if there is any. How can you deal with ramblers while maintaining civility
Forthcoming issues of Point Lookout
- Coming November 29: Manipulators Beware
- When manipulators try to manipulate others, they're attempting to unscrupulously influence their targets to decide or act in some way the manipulators prefer. But some targets manage to outwit their manipulators. Available here and by RSS on November 29.
- And on December 6: Reframing Revision Resentment: I
- From time to time, we're required to revise something previously produced — some copy, remarks, an announcement, code, the Mona Lisa, whatever… When we do, some of us experience frustration, and view the assignment as an onerous chore. Here are some alternative perspectives that might ease the burden. Available here and by RSS on December 6.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrengLXSKsBHmdJIyjljner@ChacZoXfCOynMBYZDQDfoCanyon.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
- Ten Project Management Fallacies: The Power of Avoiding Hazards
- Most of what we know about managing projects is useful and effective, but some of what we know "just ain't so." Identifying the fallacies of project management reduces risk and enhances your ability to complete projects successfully. Even more important, avoiding these traps can demonstrate the value and power of the project management profession in general, and your personal capabilities in particular. In this program we describe ten of these beliefs. There are almost certainly many more, but these ten are a good start. We'll explore the situations where these fallacies are most likely to expose projects to risk, and suggest techniques for avoiding them. Read more about this program. Here's a date for this program:
- 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.