Founder's Desk
Most engineers who get promoted into their first management role are handed a title, not a definition. Nobody sits them down and explains what, specifically, separates "leading" from "managing", so they tend to default to whichever behaviors they last saw modeled well, or badly, by their own manager.
The distinction is worth being precise about, because the two roles depend on genuinely different mechanisms, and mixing them up is one of the more common ways new engineering managers stumble.
The test that actually distinguishes them
Leadership and management get used interchangeably, but they're distinguishable by a fairly simple test: a leader is accountable for reaching a goal, not for performing a task, and that goal can't be reached alone. It requires a team, and every person on that team is, in a meaningful sense, free to say no or walk away. The only real lever a leader has is persuading people the goal is worth pursuing.
That constraint shapes everything else. If your team members have differing motivations that sometimes clash with each other, you don't get to simply overrule the disagreement, you have to work through it. If the team has skills you personally don't possess, and it almost always will, you still have to evaluate their work fairly, which means learning enough to ask good questions even where you can't personally do the job.
A manager, by contrast, operates inside a formal structure. People report to you because the org chart says so, not because they've chosen to follow your vision. You have levers a leader doesn't automatically have: you can set someone's tasks, evaluate their performance, and in most companies, affect their pay. None of that requires the same ongoing persuasion a leader depends on.
This isn't a knock on management. Plenty of essential work, resourcing, coordination, performance evaluation, genuinely requires the authority a management title confers. But it's a different job, with a different set of skills, than rallying a team around a goal they're free to walk away from.
Why the distinction actually matters
The healthiest engineering organizations we've seen treat these as complementary rather than competing skill sets, and actively develop both in the same person over time. Someone can hold a management title and still lead, in the sense of building genuine buy-in rather than only issuing direction, and the best managers usually do exactly that.
A simple gut-check
The confusion between the two roles causes real damage. Someone promoted into a management title, but never taught to lead, tends to fall back on the authority of the role whenever persuasion would be harder: assigning work by decree instead of building buy-in, and wondering why the team's engagement quietly declines.
The reverse failure also happens. A strong technical leader with no formal authority can rally a team around a good idea, but if the organization never gives them the structural tools management requires, resourcing, evaluation, escalation, the team's momentum has nowhere to go once the idea needs real organizational weight behind it.
Developing both, deliberately
A simple gut-check: think about the last time you got a team to do something hard. Did it work because they were persuaded of the goal, or because the org chart said so? Most people, if they're honest, find they've relied on the org chart more than they'd like to admit.
