Week 30 Day 5: Teaching People to Think, Not What to Think

The goal of developing others is not to produce clones of yourself. It is to develop people who can think through problems using their own judgment, experience, and perspective. A team of independent thinkers will disagree with you -- and that disagreement is a sign of success, not failure. If everyone on the team always agrees with you, they are either suppressing their own thinking or they have learned to predict and conform to yours.

Here is how to develop thinking instead of compliance. First: teach frameworks, not answers. When someone asks how to prioritize their work, do not give them your priority ranking. Teach them the prioritization framework you use: urgency, impact, effort, dependencies. Let them apply the framework and reach their own conclusion. Their conclusion might differ from yours -- and that is fine as long as the framework was applied thoughtfully. Second: reward the reasoning, not the outcome. When someone presents a recommendation, evaluate the quality of their analysis, not whether it matches your preferred answer. 'I disagree with your conclusion, but your reasoning is sound -- tell me more about how you weighted the risk factor.' This sends the message that thinking quality matters more than answer matching. Third: share your reasoning process, not your conclusions. When you make a decision, narrate the thinking that led to it. 'Here is what I considered, here is what I weighted heavily, here is what I discounted, and here is why I landed where I did.' This gives the team a model of how to reason, not what to conclude. Fourth: create safe failure space. Independent thinking requires the freedom to be wrong. If every wrong answer is punished, people stop thinking independently and start conforming. Create explicit safety for being wrong: 'I would rather you give me your honest analysis and be wrong than tell me what you think I want to hear.' I have a test I use to evaluate whether I am developing thinkers. Once a quarter, I ask myself: has anyone on my team disagreed with me recently? If the answer is no, I am developing mirrors, not thinkers, and I need to change my approach.

The distinction between teaching thinking and teaching compliance maps to what Bloom (1956) calls the taxonomy of educational objectives. Teaching answers operates at the lowest levels of the taxonomy: knowledge (remembering facts) and comprehension (understanding concepts). Teaching thinking operates at the highest levels: analysis (breaking down problems), synthesis (combining elements), and evaluation (making judgments). Research by King (1994) on 'guided cooperative questioning' found that students trained in analytical questioning frameworks outperformed answer-trained students by 40% on transfer tasks -- problems that differed from the training context -- demonstrating that thinking skills generalize while answers do not. The 'reward the reasoning' principle implements what Mueller and Dweck (1998) call 'process praise' versus 'person praise.' Their research found that praising the process (effort, strategy, reasoning) increased persistence and performance by 30% compared to praising the person (intelligence, talent), because process praise attributes success to controllable factors (effort, reasoning quality) while person praise attributes success to uncontrollable factors (innate ability). The quarterly disagreement test connects to research by Janis (1972) on 'groupthink,' which demonstrated that the absence of disagreement in a team is a reliable indicator of conformity pressure rather than consensus, and that groupthink produces systematically worse decisions because the team fails to examine alternatives, question assumptions, or consider risks.