Asking the right questions to facilitate teamwork

One of the most important skills for teamwork is the ability to ask questions effectively. Great questions can set the stage for teams to have constructive dialogue that can support creative thinking, structured planning, and problem solving.

Conversely, poorly asked questions can be destructive to teamwork. Bad questions can distract from the topics at hand and undermine the culture of cooperation that teams need to be most productive.

Skillful questioners tend to ask only a few, well selected questions and avoid asking many questions that others might ask. To avoid less fruitful questions, learn to wait; often you will find the answer or someone else will ask it.

Questions to avoid (also discussed here)

  • Gratuitous challenges – questions designed to embarrass the answerer; cause unnecessary tension.
  • Unnecessary questions – those that you could answer yourself with a little thought; derail meetings and waste time.
  • Off-topic questions – self-explanatory; frustrating to everyone else.
  • Confrontational questions – designed to inflame passions rather than gaining knowledge; lead to destructive conflict.
  • Questions for which you already know answer – usually asked to demonstrate knowledge; these make the questioner look like a show-off and create resentment.

Skillful questioners frame their questions so as to open up the dialogue to new possibilities. Questions should show courtesy and respect for others and only be asked when you sincerely want the answers.

Questions to ask

  • Clarifying questions – those that help ensure a full understanding of topics; essential for all team members to be working with common knowledge for planning problem solving.
  • Exploratory questions – emphasize possibilities that have not yet been discussed; enhance teams ability to find creative solutions.
  • Why questions – these examine the underlying rationale for actions, processes, or circumstances; useful for problem solving, planning and several other purposes, as explained here and here.

Asking questions is such a common activity that it is easy to simply take questioning skills for granted. However, with a little focus on asking the right questions (and avoiding the wrong questions) our teams can realize the benefits of skillful questioning.

TechnoratiTechnorati: , , , , , ,


4 Responses to Asking the right questions to facilitate teamwork

  1. […] One of the last posts was about Asking the right question to facilitate teamwork: again very good stuff and there is something at the end I don’t agree. Why questions – these examine the underlying rationale for actions, processes, or circumstances; useful for problem solving, planning and several other purposes […] […]

  2. Kent Schnaith says:

    Hi, I found this mp3 at and thought you might like it.
    It’s Episode 8: investigate INVESTIGATE … The Best Ideas Are Recursive.
    How to learn anything from others without driving them nuts. A protocol called Investigate is described.
    Here is a link to the podcast

  3. First, be sure to read my response to PierG’s comments about this post at this link.
    Second, thanks for the link Kent. I heard a couple of good lessons. “When you are angry, INVESTIGATE.” Which means find out all the facts and under-the-surface issues involved in a situation. Really good advice.
    The other nugget is the “CHECK OUT” option. When you know you are not reacting well, check out, then come back to it when your frame of mind is more likely to produce good results.

  4. […] post: Asking the right questions to facilitate teamwork Technorati: Dale H. Emery, […]

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: