Article

Are you a Leader, or just a Manager with more Meetings?

Management is a role; leadership is a choice. Why the most important contribution to your team might have nothing to do with your title.

LeadershipManagementProfessional Growth

In the world of software development, we often use the terms "Technical Lead" and "Manager" as if they are interchangeable. They are not. Management is about things: budgets, timelines, resource allocation, and reporting structures. Leadership is about people: growth, vision, motivation, and trust.

The Influence Gap

The most dangerous assumption a person can make is that their title gives them the right to lead. Authority can be granted by an HR department, but leadership must be earned from the engineers on the ground.

  • A manager uses positional power to compel action ("Because I'm your boss").
  • A leader uses referent power to inspire action ("Because we believe in the quality of the architecture").

If you stripped away your title and your ability to approve vacation time, would your team still follow your technical direction? If the answer is "no," you are currently managing, not leading.

The Myth of the "Hero Technical Lead"

Many managers believe their job is to be the smartest person in the room—to provide all the answers and make all the final architectural calls. This is a trap that leads to massive technical silos.

A true leader's primary goal is to make themselves unnecessary. They focus on building a team composed of individuals who have the skills, context, and confidence to make decisions without asking for permission. They invest in mentorship of junior engineers rather than doing the deep work themselves.

Shipping vs. Sustainability

Management relies on a contract: "I give you a salary, you give me your time." Leadership relies on a covenant: "I give you my trust, you give me your commitment to excellence."

When things go wrong—when a production outage happens or a deadline is missed—the manager looks for a "process failure" or someone to blame in the Post-Mortem. The leader looks for a way to support the person who made the mistake and ensures the team learns from the outcome without introducing additional friction.

Credits & References

  • Fred Brooks: The Mythical Man-Month - The definitive work on why management and technical leadership must stay in constant, healthy tension.
  • Simon Sinek: Start with Why - A core text on how leadership is about vision and purpose, not just instructions and tactics.
  • Peter Drucker: Often cited on the difference between "doing things right" (management) and "doing the right things" (leadership).

This article is part of the Decoupled Leadership Series.

About the writer

Marcus Thorne

Head of Engineering

Recommended by our partners

Discussion

Keep the conversation going

Log in to join the discussion.

No comments yet. The first thoughtful reply can set the tone for the whole thread.