What Might Happen if You Asked a Powerful Question?

Posted by Deborah Hartmann on May 12, 2008 01:00 AM

Community

Agile

Topics

Leadership ,

Teamwork

Tags

Management ,

Coaching and Mentoring

Would you rather be asked: "Why did you fail?" or "What would help you succeed next time?". Too often leaders, pressed for time, throw the easiest question at a team. But a moment's reflection, followed by a wise open-ended question can generate new possibilities when a team is stuck. The art of the deceptively simple "Powerful question," a centuries-old educational technique, is still taught to coaches-in-training, for example, by the Coaches Training Institute (CTI).

A vital question, a creative question, rivets our attention.
All the creative power of our minds is focused on the question.
Knowledge emerges in response to these compelling questions.
They open us to new worlds.

-- Verna Allee, in The Knowledge Evolution

The trick lies in NOT asking the weak question, particularly the "yes/no" question, in which the asker's assumptions lead the discourse. Another pitfall is the blaming "why" question, which can prompt a "justifying" answer, rather than reflection and truth-telling, which would be more constructive. (Note that Lean's "Five Whys" exercise is a constructive use of the same Why question, though it can be challenging on teams with trust issues). Then there are the questions that are not questions at all: in one case, asking "How do you feel" led in a surprising direction, when it would have been just as easy to say "You must be frustrated!" (not a real question at all, but still demanding a yes/no answer).

Looking for further examples? Independent coach Lyssa Adkins has applied Powerful Questions to some Agile Team situations, including this one:

Trigger:
    A team member rehashes, yet again, something that happened months ago.
Weak Question:
    Why are we talking about this again? (implicit: "cut that out!")
Powerful Question:
    What do you make of that?

While, at first, it can feel strange to ask such open-ended questions, this one introduces the possibility of  a new kind of conversation, if there is some underlying issue that no one has been talking about. Now that it can be talked about openly, the team's range of possible approaches is expanded, and surprising new directions can result.

In a non-judgmental environment Powerful Questions can contribute to learning and problem solving in a way that a veiled "oh, shut up already" never would! Note that eliminating unnecessary "Why" questions can be a great first step toward establishing a blame-free environment, where Powerful Questions thrive.

For more on creating Powerful Questions that open up new possibilities, theworldcafe.com offers this article on what makes questions powerful [pdf], which looks at such questions as:

• "How can we best manage our work group?"
• "How can we best manage our company?"
• "How can we best manage our supply chain?"

The article includes this quote, which seems useful a useful reminder to for Agile software teams:

“A paradigm shift occurs when
a question is asked inside the current paradigm
that can only be answered from outside it."

-- Marilee Goldberg, from The Art of the Question.

1. Back to top

   It is just conceptual things

   May 13, 2008 3:18 AM by z q

   I think what's questions is good enough, it depends on the current situation. whether "how" questions or "what" questions, we can not simply determine which one is good.

   Reply

2. Back to top

   Whether or not you want to block the entire team...

   May 13, 2008 6:44 AM by Dries Bellen

   Trigger: A team member rehashes, yet again, something that happened months ago.
   Weak Question: Why are we talking about this again? (implicit: "cut that out!")
   Powerful Question: What do you make of that?

   If you talk offline to someone who keeps rehashing the same situation, you can take some time for open questions. But e.g. within a SCRUM stand-up meeting, it tends to make a meeting - that should be short and focussed - way too long. That way you're keeping the rest of the team as a hostage for something that might just as well be a personal issue... I wouldn't even ask the weak question in group, but rather offline.

   Reply

3. Back to top

   Re: Whether or not you want to block the entire team...

   May 13, 2008 9:44 AM by Mishkin Berteig

   It's true that the question might not be appropriate in the daily Scrum... I would suggest that any person circumstances that affect work are indeed the concern of the team. How those personal factors are raised and discussed is always dependent on the team's level of mutual trust and commitment. For example, if I'm always coming to work with mild illnesses such as with sniffles and a mild cough, then my personal health habits are affecting the rest of the team. The team has every right to request a change in my engagement: perhaps they ask if I can not come in when I'm sick, or perhaps they ask what they can do to help me have a healthier lifestyle... Having the discussion with the team is _not_ holding it hostage. That attitude actually is quite dangerous to the proper development of the team.

   Reply

• Older >