Leadership development happens most reliably in the spaces between formal meetings and planned initiatives. Over years of watching people grow into leadership roles, I’ve noticed that the ones who develop genuine capability do so by navigating actual problems, making decisions with incomplete information, and learning from how those decisions land. This isn’t romantic or particularly dramatic. It’s what occurs when someone is responsible for something that matters and has to figure it out.
The common assumption is that leadership develops through programs, workshops, or mentorship structures. These can help, but they’re rarely where the real learning occurs. What I’ve observed is that people develop leadership capacity by encountering friction in their work – moments when their current approach doesn’t work, when they have to influence without authority, when they need to make a call that affects others. The quality of their thinking afterward determines whether they learn or simply move on.
The role of small decisions
Most leadership development happens through decisions that feel minor at the time. Someone decides how to respond when a colleague makes a mistake. Another person chooses whether to speak up in a meeting when they see a problem forming. A third decides how to allocate time between a crisis and a longer-term issue. None of these moments appear in a leadership curriculum, yet they accumulate into patterns of thinking and behavior that define how someone leads.
What distinguishes people who develop leadership from those who don’t is often their willingness to sit with the discomfort of these moments rather than rush past them. When a decision doesn’t produce the intended result, some people immediately rationalize it and move forward. Others pause and ask what they missed, what assumption proved wrong, or what they might do differently. This reflection – this deliberate thinking about what happened and why – is where actual learning lives.
I’ve watched this play out repeatedly in project work. Two people might face the same setback. One treats it as an external problem that happened to them. The other examines their own role in how things unfolded. Over time, the second person develops a more nuanced understanding of how their decisions ripple outward. They become more attentive to early signals. They anticipate consequences more clearly. This isn’t because they’re smarter; it’s because they’ve built a practice of learning from their work.
How constraints shape judgment
Real constraints – limited budget, tight deadlines, competing priorities – force the kind of thinking that leadership requires. When someone has unlimited resources and time, judgment doesn’t develop much. The interesting learning happens when you have to choose what matters most, when you can’t do everything, when you have to make a case for your priorities to people who see things differently.
I’ve noticed that people who develop strong judgment tend to have worked in environments where they felt the weight of tradeoffs. They’ve had to defend a decision to someone skeptical. They’ve had to live with the consequences of choosing one path over another. This creates a kind of calibration that no simulation can replicate. You learn what you actually value by having to choose under pressure.
The people who struggle most in leadership roles often come from backgrounds where they had a lot of autonomy but not much constraint. They could do what they thought was right without having to convince anyone or negotiate across competing needs. When they move into roles where their decisions affect others and resources are limited, they sometimes lack the experience of having to build consensus or make hard tradeoffs. They have to develop this capacity on the job, which can be slower and more painful than if they’d encountered it earlier in a smaller context.
Learning from how others respond
One of the underestimated sources of leadership development is paying attention to how people respond to your actions and decisions. If you make a call and people seem confused or resistant, that’s information. If you ask for help and people are slow to respond, that’s information. If you set a direction and people don’t follow, that’s information. Most people experience these moments as frustration or failure. Some experience them as data about how their approach is landing.
I’ve worked with people who are remarkably attentive to this kind of feedback. They notice when someone’s body language shifts during a conversation. They pick up on tone changes in emails. They remember how people responded to similar situations in the past. This attentiveness isn’t innate – it’s developed through practice and deliberate reflection. They’ve built a habit of asking themselves, “What did I notice about how that landed?” and “What does that tell me about how to approach this differently next time?”
The opposite pattern is also common: people who move through their work without much awareness of how others are responding to them. They make a decision, communicate it, and assume understanding. When things don’t go as expected, they blame external factors or other people’s resistance rather than examining their own communication or approach. Over time, this creates a ceiling on their effectiveness. They don’t develop the sensitivity to influence that leadership requires.
The accumulation of small experiences
Leadership develops through accumulation. One conversation where you listen more than you speak doesn’t make you a good listener. One project where you think carefully about tradeoffs doesn’t make you strategic. But over time, as these moments stack up, patterns form. You develop intuitions about what works. You learn to recognize situations you’ve seen before. You build judgment.
This is why people who’ve worked in several different contexts often develop leadership capacity faster than those who’ve stayed in one place. Different environments create different problems, different constraints, different kinds of people to work with. Each context teaches something different about how to navigate complexity, how to influence, how to make decisions when you don’t have perfect information.
The people I’ve seen develop most as leaders are those who’ve been genuinely curious about their own impact. They’ve asked for feedback, not defensively but genuinely wanting to understand how they come across. They’ve reflected on projects that didn’t go well and tried to extract learning rather than blame. They’ve sought out stretch assignments not for the resume line but because they wanted to test themselves against harder problems. This orientation – toward learning rather than toward proving themselves – seems to be what separates those who develop and those who plateau.
What I’ve come to understand is that leadership development isn’t something that happens to you through programs or mentors. It’s something you do through how you engage with your actual work. It’s built through the small decisions you make every day, the way you respond when things don’t go as planned, and your willingness to examine your own role in outcomes rather than always looking outward for explanations. The people who develop leadership capacity are those who treat their work as a continuous learning environment rather than a series of tasks to complete.
