Asana's guide to leadership and management distinguishes two clusters of work. Leaders set vision, inspire change, take calculated risks, and influence people; managers organize resources, maintain stability, provide feedback, and turn direction into execution. The article repeatedly says organizations need both and that one person can perform both. That qualification prevents the comparison from becoming a simple ranking.
The table still carries a familiar hierarchy. Vision, transformation, inspiration, and the future sound expansive; operations, structure, mitigation, and the present sound administrative. The result is a distinction that celebrates leadership while making the actual exercise of organizational power harder to see.
Managers do not merely read a map drawn by leaders. They decide who receives an opportunity, whose deadline moves, how performance is documented, whether leave is workable, which conflict is escalated, and whose employment ends. Those decisions shape strategy and culture as concretely as a speech about purpose. Describing management as execution understates both its moral responsibility and its capacity to change direction.
Leadership without formal authority is also romanticized. A colleague can earn trust, mentor others, and influence a team without a title. But influence cannot approve a budget, correct an unsafe workload, disclose pay bands, or guarantee protection from retaliation. Encouraging everyone to "lean in" as a leader can ask employees to supply emotional energy and coordination beyond their role while the organization retains authority elsewhere. Responsibility expands; power does not.
The leader-manager split can then create convenient deniability. Senior leaders own the inspiring vision while managers become the face of unpopular constraints. Managers may be told to motivate people toward a target they did not set, with staffing they cannot change. When the target fails, the organization can diagnose weak execution; when it succeeds at human cost, leaders can claim strategic clarity. A useful framework should show how authority and accountability travel together.
The claim that leaders drive change while managers maintain stability is similarly too neat. Front-line managers often detect the need for change because they see recurring failures. Senior leaders can be the strongest defenders of an existing strategy, especially when status or compensation depends on it. Stability is not a lesser instinct either. In safety-critical, financial, care, or public-service work, preserving reliable operations can be the most important form of leadership.
Organizations would learn more by mapping decisions than labeling people. For each consequential choice, who proposes, advises, decides, funds, implements, can stop, and must explain the result? Which information does each role receive? Can a manager reject an unsafe target? Can an informal leader challenge the vision without becoming responsible for fixing it? Does the person praised for transformation remain accountable for the operational debt it creates?
The article's practical advice on feedback, delegation, communication, and development remains useful. Those are not exclusively management or leadership skills; they are ways people coordinate under unequal authority. Treating them as shared practices would be clearer than sorting them into aspirational identities.
The addendum is that the central distinction is not vision versus execution. It is influence versus authority, and responsibility must be matched to both. A title does not create leadership, but it does confer powers that inspiration cannot replace. Organizations become healthier when the people who set direction remain answerable for its operational consequences and the people managing those consequences have genuine authority to revise the direction—not merely a nicer label for carrying it out.