A clarifying question helps to remove ambiguity, elicits additional detail, guides you as you answer a question that had been put to you, or just satisfies your curiosity. Clarification is a useful tool in job interviews, consulting, sales, investigation, and interrogation, but it must be used with delicacy and sensitivity.
In job interviews, as the candidate, if you're unsure how to respond to a question, you might want to ask a clarifying question. Unfortunately this can make you seem like you have something to hide. Better: answer in a minimally helpful way, and then ask the clarifier. Even a limited answer positions you as genuinely trying to reply, and earns the credit you need to ask the clarifier.
Keep two things in mind. First, interviewers sometimes intend to make you unsure how to respond. Maybe it's a test — will you take the initiative and ask a clarifier? Second, interviewers, recruiters, consultants, therapists, salespeople, investigators, and interrogators like to ask open questions, which sometimes feel vague. And people who ask open questions are not always skilled in doing so, which can add to their vagueness.
In conflict, when you sense tension, a gentle clarifying question — and careful listening to the response — can prevent misinterpretation from turning things toxic. And asking a question can tell your partner that communication generally isn't working right.
Here are some tips for clarifying questions.
- Don't ask too many
- Asking too many clarifiers looks evasive. The person you ask defines too many. Be sensitive to their responses.
- Clarifiers don't have to be questions
- "Say more," or "Tell me more about that" often suffice. And they don't always count as questions — your partner might even be flattered by your interest.
- Ask open questions
- Open questions tend to produce more information. Closed questions tend to produce short, limited responses. For instance, "Tell me how this all began," will produce more information than "How long has this been going on?"
- Asking too many clarifiers
looks evasive. The person you
ask defines too many.
- Avoid "or"
- "Or" restricts the reply to one of the possibilities you mention. If you catch yourself in "mid-or", adding "…or something else" at the end repairs some of the damage.
- Ask one question at a time
- You never know where the answer to the first question will lead. Wait to find out before asking another.
- Don't ask clarifiers in email
- The round trip time can be long, which creates frustration for all. If you need clarification, try telephone or face-to-face, instead of email.
- Go easy on presenters
- In presentations, it's disruptive to ask clarifiers more often than, say, every 15 minutes. If the presentation really needs that much clarification, questions won't help.
In a single day, you can witness the final hours of a brand that took ten years to build. Or you can see it re-emerge stronger than ever. From Tylenol to JetBlue — no brand is exempt. And the outcome depends not only on what you say to the public, but on how well you communicate internally — to each other. 101 Tips for Communication in Emergencies is filled with tips for sponsors of, leaders of, and participants in emergency management teams. It helps readers create an environment in which teams can work together, under pressure from outside stakeholders, in severely challenging circumstances, while still maintaining healthy relationships with each other. That's the key to effective communication in emergencies. It's an ebook, but it's about 15% larger than "Who Moved My Cheese?" Just USD 19.95. Order Now! .
Your comments are welcomeWould you like to see your comments posted here? rbrenDukaxzpdNooJjaYQner@ChachEqQPqhrGbVgZmmEoCanyon.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 Personal, Team, and Organizational Effectiveness:
- Getting Around Hawthorne
- The Hawthorne Effect appears when we measure employee attitudes or behavior — when people know
they're being measured, they modify their behavior. How can we measure attitudes with a minimum of distortion
from the Hawthorne Effect?
- 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.
- Twenty-Three Thoughts
- Sometimes we get so focused on the immediate problem that we lose sight of the larger questions. Here
are twenty-three thoughts to help you focus on what really counts.
- Management Debt: I
- Management debt, like technical debt, arises when we choose paths — usually the lowest-cost paths
— that lead to recurring costs that are typically higher than alternatives. Why do we take on
management debt? How can we pay it down?
- A Review of Performance Reviews: Blindsiding
- Ever learn of a complaint about you for the first time at your performance review? If so, you were blindsided.
Reviews can be painful. Here are some guidelines for making them a little fairer.
Forthcoming issues of Point Lookout
- Coming July 26: 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. Available here and by RSS on July 26.
- And on August 2: Linear Thinking Bias
- When assessing the validity of problem solutions, we regard them as more valid if their discovery stories are logical, than we would if they're less than logical. This can lead to erroneous assessments, because the discovery story is not the solution. Available here and by RSS on August 2.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenRfqPyPkQNojfECrXner@ChacckSxBFvqlYbSCMpWoCanyon.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 a date for this
- 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 a 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.
- 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.