Week 49 Day 4: Your Humility Story -- The Team Member Who Taught You Something

Think about a specific moment when a team member changed your mind about something important. Not a small adjustment -- a genuine shift in how you thought about a problem, a practice, or a leadership approach. The more junior the person, the more powerful the story, because it demonstrates that you learn from people regardless of their position.

Here is the structure for the humility story. First -- the assumption you held. What did you believe before this person changed your mind? The assumption should be something reasonable, not something obviously wrong. 'I believed that the best way to develop junior engineers was to assign them challenging projects with minimal guidance -- throw them in the deep end and they will learn to swim.' The reasonable assumption makes the story relatable because the audience probably holds similar assumptions. Second -- the moment of challenge. How did the team member challenge your assumption? 'A junior engineer I managed, about two years into her career, asked for a one-on-one outside our regular schedule. She said: I know you believe in learning by doing, and I appreciate the challenging assignments. But I am spending about 30% of my time stuck on problems that a 10-minute conversation with you would resolve. I am not learning from being stuck -- I am just being stuck. I would learn more if I had 15 minutes of your time each day for the first week of a new project to get oriented, and then I could run independently.' The specific language matters. Paraphrasing dilutes the story -- if you can remember the actual words (or close to them), use them. Third -- your reaction. Be honest about your initial internal reaction, even if it was defensive. 'My first instinct was to push back. I had learned by struggling, and I believed struggle was necessary for growth. But I sat with her feedback for a day, and I realized she was not asking me to make things easier. She was asking me to make the struggle productive instead of wasteful.' The honest reaction is what makes the story authentic. If you immediately agreed and changed, the story sounds rehearsed. If you initially resisted and then came around, the story sounds human. Fourth -- the change. What did you do differently? 'I tried her model: 15 minutes each morning for the first week of a new project. Orientation, context, key decisions, and known pitfalls. After that week, she ran independently. Her ramp-up time on new projects dropped from three weeks to one. I used the same model with every new engineer after that.' Fifth -- what you learned about leadership. 'She taught me that there is a difference between productive struggle and wasteful struggle. Productive struggle is when you are working at the edge of your ability on a problem you have the context to solve. Wasteful struggle is when you are stuck because you lack context that someone else already has. My job as a leader is to remove the wasteful struggle so the team can focus on the productive struggle.' When to use this story: when onboarding a new team member who seems hesitant to challenge you, when you want to model intellectual humility, when you are encouraging the team to push back on your ideas.

The humility story implements what organizational learning researchers call 'leader learning orientation' (Bunderson and Sutcliffe, 2003) -- the demonstration by a leader that they prioritize learning over appearing competent. Their research found that leaders who displayed learning orientation (including publicly acknowledging what they learned from subordinates) produced teams with 40% higher experimentation rates and 25% higher innovation output than leaders who displayed performance orientation (appearing competent and knowledgeable). The productive versus wasteful struggle distinction maps to what Vygotsky (1978) calls the 'zone of proximal development' (ZPD) -- the range of tasks that a learner can perform with guidance but not yet independently. Tasks within the ZPD produce learning because the learner is working at the edge of their current capability with appropriate support. Tasks outside the ZPD (either too easy or too difficult without available support) produce either boredom or frustration, neither of which produces learning. The junior engineer in the story was identifying that her leader's approach was placing her outside the ZPD -- in the frustration zone -- rather than within it. The '15 minutes of daily orientation' model implements what cognitive apprenticeship researchers (Collins, Brown, and Newman, 1989) call 'scaffolding' -- the temporary support structure that an expert provides to a learner, which is gradually removed as the learner develops competence. Their research found that scaffolded learning produced 50-80% faster skill development than unscaffolded learning for complex cognitive tasks, because scaffolding directs the learner's attention to the most relevant features of the task and reduces cognitive overload during the initial learning phase.