Leaders and managers are often expected to be the same person — and in most organisations they literally are. The roles are genuinely different, though. The conflation costs organisations more than is obvious, and it costs individual operators a particular kind of clarity about what they're actually being asked to do in any given situation.
The clearest academic framing of this distinction came from John Kotter, then at Harvard Business School, writing in the Harvard Business Review in 1990. Management, Kotter argued, is about coping with complexity: planning, budgeting, organising, staffing, controlling. Leadership is about coping with change: establishing direction, aligning people, motivating and inspiring. Both are necessary. Most organisations, Kotter observed, are chronically overmanaged and underled. The observation has aged well — it describes the 2020s at least as accurately as the 1990s.
Three distinctions hold up across contexts, industries, and decades. They're not a ranking of which role matters more — management isn't lesser work than leadership. They're a diagnostic: if you know which mode your situation actually requires, you can apply it deliberately rather than by accident.
1. Managers optimise execution; leaders choose the direction
Management asks: given a goal, how do we execute it efficiently? Staffing, process, milestones, iteration — the machinery of delivery. Leadership asks a prior question: is this the right goal? When the goal is given, clear, and stable, management is most of what's needed. When the goal is ambiguous, contested, or subtly wrong, leadership is what's required first.
The costs of conflating these are significant in a particular way. The most common organisational failure isn't bad management — it's good management of a bad goal. The project team that delivers on time and on budget but builds something the market doesn't want. The sales organisation that hits its quota on a product that's losing relevance. The content team that produces efficiently against a brief that's misframed for its audience. In each case the execution is competent; the error happened upstream, at the direction-setting step that should have been leadership work.
The leadership work of setting direction is often undervalued precisely because it's harder to quantify. A manager who runs a clean process leaves behind a visible trail of closed tasks and delivered output. A leader who asks "should we be doing this at all?" often generates friction before they generate clarity. The short-term cost of that friction is real; the long-term cost of not asking the question is usually much larger. Teams in stable, well-managed execution of the wrong goal are a slow-motion failure that can look like good performance for years before the gap becomes visible.
The practical test: in any planning meeting, ask who's deciding what to pursue versus who's deciding how to pursue it. In functional teams both questions get answered, usually by different people in different moments. The problem arises when everyone is focused on the how and no one owns the what — or when the person ostensibly owning the what is just ratifying the team's existing momentum.
2. Managers track outputs; leaders develop people
A manager's primary scorecard is work completed: milestones hit, tasks closed, quality maintained, deadlines met. These are necessary measures and a manager who doesn't track outputs isn't doing the job. A leader's primary scorecard is people grown: who is more capable this year than last, who has taken on more responsibility than their title implies, who could run the next team level up if needed.
The distinction produces different time horizons. A team that's well-managed but poorly led will often perform adequately in the short run — outputs are delivered, the metrics look passable. Over three to five years, the people on that team haven't developed much. They do the same work at roughly the same level. The manager who doesn't develop their people is a competent short-term operator. A decade in, the team has flatlined and the organisation has stagnated at whatever level of capability existed when the manager arrived.
The leader who develops people produces a compounding effect. Each year the team can do slightly more, slightly better, with slightly less direct supervision. Over a decade, that team has become capable of work that would have been beyond reach at year one — not because the leader got smarter, but because the team did. That compounding effect outlasts the leader: it shows up as organisational strength that survives their departure, and as the next generation of capable operators the organisation draws from.
There's a practical self-interest argument here too. Leaders who genuinely develop their people almost universally report that it frees them to operate at a higher level. When your team handles more autonomously, the nature of your own work shifts from supervising execution to navigating the bigger problems the organisation needs solved. The leader who doesn't develop their team is, in a practical sense, choosing to remain a floor below where their role requires them to operate.
Practical signal: look at the last six people to leave your team. Did they leave more capable than they arrived — more skilled, more confident, with a broader professional network? If the answer is uncertain, the development function is probably missing from how the team is run.
3. Managers use authority; leaders build trust
Managers can issue instructions. People comply because of role power — the reporting relationship, the performance review cycle, the org chart. Formal authority is a genuine resource and it's necessary for many kinds of coordination. The limitation is that compliance bought through authority is conditional on the authority persisting. When the authority diminishes — through role change, organisational restructuring, or the person moving on — the compliance often diminishes with it.
Leaders don't depend on authority to get people moving. People follow because they want to — because they trust the leader's judgment, because following has been worth it in the past, because the direction being pointed to seems genuinely correct. The same person can hold a manager's title and not be a leader: people comply when required and disengage when not. The same person can operate as a leader without any formal title: influence comes from demonstrated competence, honest communication, and a track record of good calls.
The trust that makes someone a leader rather than merely a manager is built through small acts of congruence over time. The person who says they'll do something and then does it. Who takes responsibility for their decisions when they go wrong, without deflecting to circumstances or subordinates. Who tells the team what they actually think rather than what they calculate the team wants to hear. None of these gestures is dramatic. Cumulatively they produce a kind of credibility that formal authority alone cannot replicate and that survives the removal of the title.
The gap between authority-compliance and trust-followership shows up most starkly in difficult conditions. In calm periods, the manager whose team complies and the leader whose team genuinely follows may look similar — the outputs are comparable. In a crisis, a period of sustained pressure, or a moment where the team needs to act beyond their job description, the difference becomes the deciding factor. Teams built on trust stretch; teams built on authority often don't.
Practical test: if your formal title and authority were removed tomorrow, would people still seek your input and follow your direction? If yes, you're operating as a leader in the relevant sense. If no — if the followership depends entirely on the role structure — the trust side of the work needs deliberate attention.
When each mode is needed
Most organisations need both functions simultaneously, in the same person. The skill is recognising which mode the situation requires and switching deliberately.
A crisis calls primarily for leadership: the goal may need to change, the team needs to move on trust rather than process, the direction has to be set under genuine uncertainty. A steady delivery quarter calls primarily for management: direction is set, the work is planned, the job is to optimise execution and track outputs. A hiring decision sits in both simultaneously — management asks "what do we need this role to produce now", leadership asks "who has the potential to grow beyond what we need right now".
The leaders who plateau tend to favour one mode regardless of what the situation needs. The "big picture" person who is always asking what we should do and never engaging with whether it's getting done. The operational perfectionist who gets the process exactly right but never questions whether the process should exist. Both are common; both are costly; both are correctable once the person recognises which mode they're defaulting to.
Both are learnable — the research is clear on this
The "born leader" assumption — that some people naturally have what it takes and others don't — tends to make leadership feel like a personality lottery rather than a developable skill. The research consistently contradicts this. Twin studies published in The Leadership Quarterly (De Neve, Mikhaylov, Dawes, Christakis & Fowler, 2013) and Journal of Applied Psychology (Arvey, Zhang, Avolio & Krueger, 2007) find that heritability accounts for roughly 24–32% of the variance in whether someone occupies a leadership role over their career. The remaining 68–76% is environmental — shaped by experience, education, deliberate practice, opportunity, and the specific situations that either develop leadership capacity or suppress it.
The behaviours that constitute effective leadership — setting direction clearly, developing people intentionally, building trust through congruent action — are all teachable, with learnable mechanics. The leader who treats their own leadership as a craft requiring deliberate practice improves faster than the one who treats it as a fixed trait. For the specific skills worth focusing on, six specific behaviours for building your leadership capacity is the practical framework, and how leadership capacity develops over a career covers the underlying science.
The synthesis
The three distinctions — direction vs execution, development vs outputs, trust vs authority — are most useful not as a ranking of which matters more, but as a diagnostic for which one is missing in any given moment or relationship.
The leader who is strong at trust-building but weak at managing execution leaves their team with good morale and uneven delivery. The manager who is strong at tracking outputs but never questions the direction leaves their team efficient and possibly working on the wrong thing. The one who develops people but never makes hard calls about direction produces talented individuals without coherent collective purpose. For the fuller picture of what effective leadership actually looks like across all three dimensions, the six qualities that predict whether a team will follow someone through a hard stretch provides the most practical framework.
The most effective senior operators are the ones who have developed fluency in both modes — who can set the right goal, build the process to reach it, develop the people doing the work, and maintain trust across all three simultaneously. That combination is the job. The management/leadership distinction is real, but it describes points on a spectrum that the same person has to cover. Knowing which mode the moment requires — and being honest about which mode you're currently in — is most of what it means to do the role well.
Comments (0)