The Leadership Habit Most Leaders Skip

There's a line from Stephen Covey that has stayed with me across years of working with leaders: “seek first to understand, then to be understood”. It sounds so straightforward. It is, in practice, one of the hardest things for a leader to actually do. Not because of any technical difficulty, but because most leadership training pulls in exactly the opposite direction.

Leaders are coached to communicate vision, to be decisive, to project confidence, to drive alignment. All of that is about transmission. Very little of it is about reception. The result is a style of leadership that is often articulate, often well-intentioned, and chronically underinformed about what is actually happening in the team beneath it. This tension is frequently explored in conversations around transformational leadership approach, where influence begins with deeper understanding rather than louder direction.

This matters more than it might appear. When a leader doesn't genuinely understand the people they're leading, not just their job functions, but their pressures, their motivations, where they feel stretched and where they feel underused, they're making decisions on incomplete information. They assume a team member is disengaged when they're actually overwhelmed. They push harder on a goal when the real obstacle is something structural that nobody has surfaced. They mistake compliance for commitment and are blindsided when good people leave.

None of this is malicious. It's the natural consequence of defaulting to broadcasting when the situation calls for listening. And it accumulates. Small misreadings compound into cultural norms: teams learn that concerns don't travel upward well, that leaders prefer confirmation to challenge, that the safest course is to nod and manage problems quietly rather than raise them. By the time the leader notices something is wrong, the gap between what they believe is happening and what is actually happening can be substantial. Over time, this disconnect can contribute to patterns similar to those described in the overwhelmed practice, where leaders are reacting to symptoms rather than addressing root causes.

The fix isn't complicated, but it does require a genuine shift in where a leader directs their attention. One-to-one conversations where the agenda belongs to the team member, not the leader. Questions that invite honesty rather than close it down: 'What's getting in your way?' rather than 'Everything going okay?' A genuine tolerance for answers that are inconvenient or uncomfortable, which is the only way to build the kind of trust where people tell you things worth knowing.

Regular structured feedback matters here too, but not the kind that gets retrofitted into an appraisal cycle once a year. The most useful feedback loops are continuous and low-stakes: brief, frequent check-ins where a team member can flag something early, before it becomes a crisis. Leaders who build this into the rhythm of how they work find that problems surface faster, course corrections are smaller, and the team spends less energy managing around things that should have been addressed directly. Creating this environment is closely connected to strengthening team motivation and engagement, where open dialogue becomes part of the culture rather than an exception.

Emotional intelligence gets discussed a lot in leadership contexts, sometimes to the point where it starts to sound like a soft skill rather than a practical one. But the capacity to read what's actually going on with a person, to pick up on what isn't being said as much as what is, has direct operational consequences. A leader who can sense that a key team member is burning out before it becomes a resignation has a far wider range of options than one who discovers it on the day the notice lands. Awareness creates room to act. The absence of it doesn't. Sustaining this awareness is also critical in preventing long-term strain, as highlighted in discussions on preventing team burnout.

The deeper point is that understanding your team isn't a leadership technique to deploy alongside others. It's the foundation that determines how well everything else works. A leader with genuine insight into their team sets better goals, because the goals are grounded in what the team can actually achieve and what would stretch them usefully. They delegate more effectively, because they know who thrives with autonomy and who needs more support. They build stronger cultures, because people don't perform well in environments where they feel unknown.

Leadership that begins with understanding doesn't dilute authority, it makes authority worth something. People follow leaders they believe understand them far more willingly than leaders who simply outrank them. The difference shows up in discretionary effort: the work people do because they want to, not because they're required to. That's where most of the competitive advantage in a team lives, and it's almost entirely a function of how people feel about the leadership above them.

So the practical question is less about philosophy and more about habit. How much of your time as a leader is genuinely spent listening, not waiting for your turn, not formulating your response, but actually trying to understand what someone is telling you and why it matters to them? If the honest answer is not enough, that's the place to start.

‍