Week 30 Day 3: The Power of Asking Instead of Telling

When a team member brings you a problem and you immediately provide the solution, you have solved one problem and created a dependency. When you ask 'what have you tried so far?' and 'what options are you considering?' you force them to develop their own reasoning. The next time they face a similar problem, they have the thinking skills to solve it without you.

Here is the questioning framework I use when someone brings me a problem. Instead of responding with a solution, I move through four questions. Question one: 'What is the problem as you see it?' This forces them to articulate the problem clearly. Half the time, the act of articulating reveals the solution -- they were stuck because they had not defined the problem precisely. Question two: 'What options have you considered?' This surfaces their thinking. Often they have already considered the right approach but lack confidence to commit. Your validation of their thinking is more valuable than your alternative. Question three: 'What are the tradeoffs of each option?' This develops their analytical muscle. Even if their analysis is incomplete, the exercise of evaluating tradeoffs builds a skill they will use independently. Question four: 'What is your recommendation?' This asks them to commit to a position. Most people who bring problems to their manager have a recommendation but are afraid to state it. Asking for the recommendation normalizes having opinions and builds decision-making confidence. Notice what this framework does not include: my opinion. In most cases, the four questions are sufficient to help the person reach a good decision without my input. When they reach it themselves, they own it. When I tell them the answer, I own it and they are just executing. There are two exceptions to this framework. First: when the building is on fire. If there is an active incident, a time-critical decision, or an irreversible action about to be taken, skip the questions and provide the answer. Coaching during emergencies is irresponsible. Second: when the person has asked you the same type of question three times and you realize that questioning alone is not building the skill. In that case, pair with them: work through the problem together, narrating your reasoning process so they can observe and internalize your approach.

The questioning framework implements what Whitmore (2009) calls the 'GROW model' of coaching -- Goal, Reality, Options, Will -- which is the most widely used coaching framework in organizational settings. Research by Grant (2003) on the effectiveness of coaching found that a questioning-based coaching approach increased goal attainment by 32% compared to directive instruction, and that the effect persisted six months after the coaching interaction, while directive instruction effects faded within weeks. The mechanism is what psychologists call 'generative learning' (Wittrock, 1989) -- the finding that knowledge generated through active reasoning (answering questions) is retained and transferred more effectively than knowledge received passively (being told answers). Wittrock's research found that generative learning produced 30-50% better transfer to novel problems compared to receptive learning, which explains why question-based coaching develops problem-solving capability while answer-giving does not. The 'half the time, articulating reveals the solution' observation maps to what programmers call 'rubber duck debugging' and what psychologists call the 'self-explanation effect' (Chi, Bassok, Lewis, Reimann, and Glaser, 1989), which demonstrates that the act of explaining a problem activates problem-solving schemas that remain dormant during internal rumination. The two exceptions -- emergencies and repeated questions -- implement what Vroom and Yetton (1973) call the 'contingency model of leadership,' which demonstrates that the optimal leadership style varies by situation, and that participative (questioning) leadership is optimal in most situations but autocratic (directive) leadership is optimal when time pressure is high or when the subordinate lacks the foundational knowledge to participate meaningfully.