You've been made a team lead: what to do in your first week
Congrats, you've been made a team lead. The congratulations fade, Monday arrives — you're in the new role with no manual for it. So where do you even start?
Straight up: almost every new lead falls into one of two traps. Either they hide in familiar tasks and keep shipping code (it's comfortable, it's safe). Or they start changing everything from day one — to prove they were the right pick. Both bite you later.
The first week isn't about results at all. It's about which kind of manager the team will remember you as. And that picture sticks for months.
Your first call isn't technical
On day one you have neither authority nor context. What you do have is the team's attention — everyone's watching what kind of person you are. So the big call of the week isn't about architecture, it's about how you show up.
Don't announce reforms. Don't promise "nothing changes" (reads as weak) or "we'll fix everything" (that's scary). Just be honest: this week I'm listening and learning, decisions come later. That's fine — nobody expects you to know it all on day one.
Do a 1-on-1 with everyone in the first couple of days
The classic rookie mistake is to push the one-on-ones "until I've settled in." But it's exactly in those first day or two that the stuff which later hides is still visible: who actually carries the team, who feels passed over, who's already halfway out the door.
This matters most with that strong engineer who wanted your seat, or who effectively ran the team before you. Skip a real chat in the first days and they'll close off — and quietly chip away at you.
- talk to everyone in the first week, short is fine;
- ask, don't lecture: what works, what's annoying, what they expect from you;
- shut up and listen more than you talk.
Your first public reaction = the team's norm
Someone will test the boundaries. Classic move: a new hire drops "stand-ups are a waste of time" into the group chat. It's not about stand-ups. It's a test of how you react in front of everyone.
Your first answer becomes a norm everyone remembers. Snap back, you get fear. Stay silent, you get chaos. Calmly name the line and offer to talk it through, you get respect.
Don't fix what you don't get yet
You're a strong engineer, you spot the mess instantly: a broken process here, painful releases there. And your hands itch to fix it on day one. Don't. Until you understand why things ended up this way, any "optimization" risks breaking a non-obvious balance — and turning people against you.
Give yourself a few days to just watch. Write down questions, not conclusions.
What NOT to do in week one
- Stay a strong engineer. Close tasks yourself and the team won't grow — you become the bottleneck.
- Change everything at once. With no context it reads as "the new person flexing."
- Dodge the awkward people. The one you'd rather not talk to is usually your key conversation of the week.
- Over-promise upward. Your manager asks "so, how's it going?" — don't promise quick wins, you don't know the scale yet.
Bottom line — don't sweat that you don't know everything. Nobody does in week one. You've already got the base, or they wouldn't have picked you; the rest you'll build. Just start with the people.
The only catch: the first stand-up, the first 1-on-1 and the first reaction happen exactly once — no second take.