The first week as a team lead: what to actually do
You have just become the team lead. Do not rewrite anything yet. Here is a week-by-week guide to the first month, built around a real weekly rhythm.
First week as a team lead. The most common failure mode is doing too much. You have new authority, probably a new title, and a strong urge to prove you belong in the chair. The second most common failure mode is doing too little. You tell yourself you are "listening" for two months and then everyone wonders what you actually changed.
Both are avoidable. Here is a simple plan for the first four weeks.
Week 1: don't break anything
Goal: do not change a single process. Run the team the way you found it, end to end.
- Monday: meet your team, one by one. Ten-minute 1:1s. Two questions: what is working for you, and what is one thing we should change. Write down the answers.
- Tuesday–Thursday: shadow. Sit in the rituals that already exist. Watch how decisions get made. Do not propose anything.
- Friday: write a one-page summary of what you saw. Keep it to yourself.
The temptation to change things will be strong. Resist it. You have no context yet.
Week 2: run their rhythm, cleanly
Goal: run the existing cadence, but with rigor.
Most teams have a standup of some shape, even if it is informal. Whatever it is, run it this week as designed. If there is a Monday plan, write it. If there is a Friday review, close it out. Do nothing extra.
Your job this week is to prove, to them, that you can hold the current shape. Trust is cheap to lose here.
Week 3: introduce the lightest structure you can
Goal: if there is no weekly rhythm, add the lightest one.
If the team already runs Mon/Wed/Fri or equivalent, keep it. If not, try three touchpoints:
- Monday plan: one sentence focus, the goals that serve it, owners.
- Wednesday status: on track, moved, or stuck — three lines per person.
- Friday review: what shipped, what didn't, what rolls over.
Do not call it a new process. Call it "the plan for this week," "a quick mid-week check," and "Friday wrap-up." Frame matters.
Week 4: start listening for patterns
Goal: spot the two or three real problems.
By week four you will have seen each teammate plan, check in, and close out. You will have 1:1 notes. Real patterns will show up: an overloaded person, a decision that keeps getting deferred, a cross-team dependency that always breaks.
This is when your opinion becomes useful. Pick two things. Not ten. Change them deliberately.
What not to do in the first month
- Do not rewrite the OKRs. Not yet.
- Do not schedule a team offsite. Your team does not know you well enough yet.
- Do not replace the tool stack. Tools do not fix leadership problems.
- Do not pick a theme for the quarter on day one. You have no signal.
The single most valuable thing you can do in month one is be the person the team can count on to close out Friday every week. Nothing else signals "we are in good hands" as clearly as a team lead who does not drop the rhythm.
After the first month
Once the weekly rhythm is stable, you can start making real changes. Pick one area a month. Hiring, roadmap, 1:1s, scope, meetings — one at a time, with the team, visibly.
The urge to move fast is real. Move fast on the weekly rhythm. Move slow on everything else.