Most developers become team leads the same way: they’re good at their job, someone notices, and one day they’re handed a new title and a vague sense that more is expected of them. Nobody sits them down and explains what the job has actually become. The assumption is that being a great engineer will naturally turn into being a great lead.
It doesn’t. The two roles share a workplace and a vocabulary, but they run on different skills, and the transition is harder than it looks from outside. This article is about the things that tend to surprise new leads, and about how to handle them without losing yourself or your team along the way.
Your output is no longer your own work
The first shift is the hardest to accept. As an engineer, you measured your day by what you built. Lines written, bugs fixed, features shipped. There was a clear feeling of progress at the end of a good day.
As a lead, your output is what your team produces. A day in which you wrote no code at all, but unblocked three people, clarified a confusing requirement and talked a stressed colleague through a hard week, may be one of the most productive days you ever have. It just won’t feel that way, because nothing visible came out of it.
Many new leads quietly resist this. They keep taking the most interesting tickets for themselves, because coding is where they feel competent. They tell themselves it’s efficient, since they’re the fastest person on the team. But every hard task you keep is a task someone else doesn’t get to grow on, and every hour you spend heads-down is an hour your team can’t reach you. A lead who is also the busiest developer is usually a bottleneck in disguise.
This doesn’t mean you must stop coding. Many good leads stay hands-on. But you have to stop treating your own code as the main event. A useful test is to ask, at the end of the week, whether your team is better off because of how you spent your time. If the honest answer is yes, you did the job, whatever your commit history says.
Feeling less competent is normal
For months, sometimes years, you were among the people who knew the answers. Then you take on a role where nobody has trained you, the feedback is vague and the results show up slowly. It’s common to feel like a beginner again.
This feeling is a sign that you’re learning something new, not that you’re failing. Management is a separate craft, with its own techniques and its own mistakes, and it takes practice. You wouldn’t expect to be excellent at a new programming language in your first month. Give yourself the same patience here.
What helps most is finding a few people to learn from. A more experienced lead, either in your company or elsewhere, who’ll talk through real situations is worth more than a shelf of books. Read the books too, but treat them as a way to name problems you’ve already met, not as manuals.
Your words now carry more weight than you realise
One of the quieter changes is that people listen to you differently. An offhand remark from a teammate is a thought. The same remark from the lead can be heard as an instruction, a verdict or a warning.
Say you glance at someone’s work and murmur that it looks a bit messy. To you it’s a passing comment. To them it may be a worry they carry all weekend. Say you mention in a meeting that a project might be cancelled. You meant it as a possibility, and half the team starts updating their résumés.
The practical response is not to become guarded or stiff. It’s to be a little more deliberate. Notice how your comments land. When you’re thinking aloud, say so, so people know you’re not announcing a decision. When you give feedback, be specific and be clear about how serious it is. And when you’ve said something carelessly, correct it quickly, because a small clarification early prevents a lot of anxiety later.
Feedback is the core of the job, and most people avoid it
If you could master only one skill as a lead, make it giving honest feedback with kindness. It’s the thing that most separates good leads from mediocre ones, and it’s the thing most people dodge.
The reasons for avoiding it are understandable. Nobody enjoys telling a colleague that their work isn’t good enough, especially when you were their peer last month. So you soften it until the message disappears, or you wait for a better moment that never comes, or you hope the problem fixes itself. It rarely does. It grows, and eventually you have a much harder conversation about a much bigger problem.
Good feedback has a few qualities. It’s timely, meaning close to the event rather than saved for a review six months later. It’s specific, describing what actually happened instead of vague impressions. It’s about behaviour and its effects, not about the person’s character. And it comes from a place of wanting the person to succeed, which they can usually tell.
It also has to include the good news. Many leads only speak up when something goes wrong, which teaches people that attention from the lead means trouble. Telling someone clearly what they did well, and why it mattered, is not flattery. It’s information they need in order to repeat it. People who never hear what’s working are left guessing about their own value.
If a conversation feels difficult, it usually means it’s worth having. Prepare by deciding what you want the person to understand and what you hope will change. Then say it plainly, listen to their side, and agree on what happens next. You’ll rarely regret a hard conversation held early, and you’ll often regret one avoided.
Protect your team from noise, but don’t hide reality
A big part of the job is standing between your team and the chaos of the wider organisation. Priorities shift, executives change their minds, other teams make demands, and somebody always wants something urgently. If you pass all of that straight to your developers, they’ll spend their days reacting instead of building.
A good lead filters. You absorb the noise, work out what actually matters, and give the team a clear, stable picture of what to do. That stability is a gift. People do their best work when they can concentrate.
But there’s a trap on the other side. Some leads protect their team so thoroughly that they hide real problems from them: a budget cut, a strategic change, a risk to the project. Teams are not fragile. Most adults prefer to hear difficult news honestly and early than to be surprised later, and they can usually tell when something is being kept from them. Trust drains away quickly when people discover they were managed instead of informed.
The balance is to shield the team from the pointless churn while being straightforward about the things that truly affect them. When in doubt, share more than you think you should, and explain the reasoning along with the news.
Delegate in a way that builds people
Every new lead hears that they should delegate. Fewer hear how to do it well, and doing it badly is worse than not doing it at all.
Bad delegation looks like dumping a task on someone with no context and then criticising the result. Or handing over the work but secretly hovering, redoing parts of it when you think no one’s looking. Or delegating only the boring tasks and keeping everything interesting for yourself. People notice all of these, and they conclude, correctly, that you don’t trust them.
Good delegation starts with being clear about the outcome you need and why it matters, then letting the person choose how to get there, within sensible limits. It includes giving enough context for good decisions, agreeing when you’ll check in, and being available for questions without taking the work back. When the result differs from what you’d have done, you ask whether it actually works before deciding it’s wrong. Often it’s simply different, and sometimes it’s better.
It also means matching tasks to growth. Look for work that stretches someone slightly beyond where they are, with enough support that they can succeed. That’s how people develop, and a team whose members keep growing is far stronger than one that depends on you for everything.
Be prepared for mistakes. Someone will get something wrong, because that’s part of learning. How you respond decides whether they ever take a risk again. If your reaction is blame, they’ll play safe from then on. If it’s curiosity about what happened and what to change, they’ll learn and so will you.
Meetings are a tool, not a lifestyle
A common surprise is how many meetings the job brings. Some of them are valuable. Many are not, and a lead who doesn’t take control of the calendar will end up with no time to think.
Start by questioning every recurring meeting, including the ones you run. Does it still have a purpose? Does it need everyone who attends? Could it be a short written update instead? Cancelling a pointless meeting is a gift to everyone in it.
For the meetings you keep, a little structure goes a long way. Know why you’re meeting and what you want to leave with. Share any reading beforehand. Start and end on time. Finish by saying who will do what, so the meeting produces action and not just conversation.
Guard your own thinking time as well. A lead whose day is fragmented into half-hour pieces can’t do the deeper work of planning, reviewing and reflecting, and the quality of everything suffers. Block out time on your calendar and treat it as seriously as any other commitment.
One-to-ones are the most valuable hour you have
If you do only one routine well, make it regular one-to-one conversations with each person on your team. Even half an hour a week or every other week changes the relationship.
The key is that the meeting belongs to them, not to you. It isn’t a status update, since you can get that elsewhere. It’s a chance for the person to raise whatever is on their mind: a frustration, an idea, a worry about their career, something that isn’t working. Your role is mostly to listen and ask good questions.
Over time, these conversations are where you learn about problems while they’re still small. Someone’s quietly losing motivation. Two people are struggling to work together. A process is wasting hours every week. A person is thinking about leaving. You won’t hear about any of this in a standup. You’ll hear about it in a trusted private conversation, if you’ve built the trust and kept showing up.
Keep the meetings even when things are busy. Cancelling them sends a message about what you consider important, and the busiest periods are exactly when people most need to talk.
Careers are your job too
Part of leading people is caring about where they’re going, not just what they’re delivering this quarter. Ask your team members what they want from their careers. Some want to go deeper technically, some want to lead, some want to try something new, and some are happy where they are. You can’t help anyone if you don’t know what they’re aiming for.
Once you know, look for ways to move them in that direction: projects that build the skills they want, introductions to people who can teach them, chances to present their work, and honest advice about what they need to improve. Argue for them when promotion decisions are made. Remember that your reputation as a lead is partly built from the people who grew under you.
This also means being honest when someone wants something that isn’t available. It’s better to say that a role doesn’t exist yet, or that you don’t think they’re ready and here’s why, than to let them wait on a vague promise.
Look after yourself too
New leads often burn out, and the reasons are predictable. They take on too much, because they’re still doing their old job as well as the new one. They absorb their team’s stress. They feel responsible for every problem. And they don’t have anyone to talk to, because they’re now in a position where they can’t always be fully open with their old peers.
Some habits help. Set boundaries on your availability, and keep them. Find a mentor or a peer group of other leads where you can speak freely. Take your holidays, and let the team run without you, which is also a good test of whether you’ve built something sustainable. Notice the early signs of exhaustion, such as irritability or dread on Sunday evenings, and act on them before they become serious.
It also helps to remember that you aren’t supposed to have every answer. A lead who admits uncertainty, asks for help and says “I don’t know, let’s find out” gives the team permission to do the same. That openness builds trust far more than a performance of confidence.
Keep your technical edge, in a different form
Many leads worry about losing their technical skills, and the worry is fair. You can’t make good decisions about a system you no longer understand. But your relationship with technology changes. You’re no longer the person writing the most code. You’re the person who sees how the pieces fit together, spots risks early and helps the team make sound choices.
Stay close enough to the work to keep your judgment sharp. Read code reviews, join design discussions, occasionally pick up a small, contained task, and keep learning about the tools your team uses. But resist the urge to prove your technical credentials by overruling people on details. Your credibility now comes less from being the best coder and more from asking the right questions and making good calls.
Measure what matters
It’s easy to judge a team by the wrong things: hours worked, tickets closed, lines written. These are easy to count and often misleading. A team that closes many tickets may be shipping low-value work. A team that works long hours may be burning out.
Better questions are whether the team is delivering things that matter, whether the quality is holding up, whether people are learning and staying, and whether the team is still healthy under pressure. These are harder to measure and more honest. Talk to your people, look at the outcomes of their work, and watch for patterns over months rather than days.
Being a good lead is mostly small, repeated habits
If this all sounds like a lot, it helps to remember that very little of leadership is dramatic. It’s mostly small habits repeated over a long time: giving a clear piece of feedback, keeping a one-to-one even when it’s inconvenient, explaining the reason behind a decision, saying thank you specifically, admitting a mistake, protecting an hour of focus for the team.
None of these is hard on its own. The difficulty is doing them consistently, especially when you’re busy or tired. The leads people remember fondly are rarely the most brilliant strategists. They’re the ones who were reliable, honest and genuinely interested in the people they worked with.
If you’ve just stepped into the role, be patient with yourself. You’ll make mistakes, and your team will forgive most of them if they believe you’re trying to do right by them. Pay attention to what you learn, ask for feedback often, and keep your focus on the people. The rest tends to follow.
What do you wish someone had told you when you first led a team? Share it in the comments, because the best advice usually comes from people who’ve been through it.
Top comments (0)