30-60-90 Day Plan for Team Leads: Template, Example and First Week

10 min read ยท 2026-10-25

A 30 60 90 day plan for team lead roles splits your first three months into three jobs: learn how the team works (days 1-30), take over its routines and delivery (days 31-60), then improve results and grow people (days 61-90). Each stage ends with a result your manager can check, such as a completed round of 1:1s or a published team working agreement.

Team leads often have a harder start than other new managers. You may still do hands-on work, you may lead people who were your peers last week, and your authority over hiring or reviews may be unclear. The plan below handles those problems directly. It includes a first-week checklist, the people to meet, a filled-in example for a support team lead, the metrics to report and how to present the plan to your manager or in an interview.

The roadmap at a glance

Goal: By day 90, the team runs on clear routines you own, one real bottleneck is fixed, every person has a development goal and your manager has approved the next-quarter plan. Duration: 90 days (13 weeks)

  1. Listen and learn (Weeks 1-2)

    Build trust with each person and learn how work really flows before you change anything.

    • Agree with your manager in writing on what you own: priorities, input on hiring, time off approvals, escalations and performance reviews.
    • Run a first 1:1 with every team member using the same four questions: what works, what gets in your way, what you want to learn, how you like feedback.
    • Sit in on every team ritual (standup, planning, retro, queue review) as an observer, without changing the format.
    • Read the last two months of tickets, incidents, escalations or deal notes to see where work gets stuck.

    Milestone: A first 1:1 done with every direct report and a one-page scope agreement confirmed by your manager.

  2. Map the work (Weeks 3-4)

    Turn what you heard into a clear picture of the team's work, strengths and problems.

    • Draw the team's workflow from request to done, with every handoff and who waits on whom.
    • Build a simple skills matrix: one row per person, one column per key skill, rated as learning, solid or can teach.
    • Meet the leads of the two or three teams you depend on most and ask what they need from your team.
    • List the top five problems you heard, ranked by how often they came up and how much they slow delivery.

    Milestone: Day 30: a one-page summary with the workflow map, skills matrix and top five problems, reviewed with your manager and the team.

  3. Take over the routines (Weeks 5-6)

    Run the team's rituals yourself and make expectations explicit.

    • Move to a fixed weekly or biweekly 1:1 rhythm with a shared running notes document for each person.
    • Write a team working agreement together: response times, how work gets assigned, when to escalate, how work gets reviewed.
    • Take over sprint planning or weekly planning, and publish the plan where your manager and partner teams can see it.
    • Hand back individual work that blocks you from leading, or agree with your manager on a capped share of your week for it.

    Milestone: A team working agreement published and every recurring ritual run by you for at least two cycles.

  4. Fix one bottleneck (Weeks 7-9)

    Deliver one visible improvement the team asked for and start measuring results.

    • Pick one problem from the top five that the team can fix in three weeks, such as a slow review step or unclear intake.
    • Name one owner on the team for the fix and protect their time in planning.
    • Record a baseline for two or three team metrics before the change, so you can show the effect.
    • Give each person a first round of specific feedback: one thing to keep doing and one thing to change.

    Milestone: Day 60: one bottleneck fixed with a before-and-after metric, and a simple team metrics view shared with your manager.

  5. Grow people and plan ahead (Weeks 10-13)

    Set growth goals for each person and agree on the team's plan for the next quarter.

    • Write a short development goal with each team member, tied to a gap or strength in the skills matrix.
    • Delegate one area you used to handle, such as release coordination or escalation triage, to someone ready to grow.
    • Draft the next-quarter plan: goals, metrics, staffing needs and risks.
    • Review the plan with your manager and agree on how your own performance will be judged.

    Milestone: Day 90: a development goal for every person, one area delegated, and a next-quarter plan approved by your manager.

Team lead vs manager: what changes in your plan

A team lead usually sits between the team and a people manager. In many companies you guide the daily work, run the rituals and coach people, while hiring, pay and formal reviews stay with your manager. In others, team lead is the first management title and you own all of it. Your plan has to start by finding out which version you have, which is why the first step is a written scope agreement.

The other big difference is that most team leads keep doing hands-on work. You might still write code, handle hard tickets or carry a few accounts. That keeps you close to the work, but it can eat your whole week. A common starting point is to agree on a cap for your individual work and protect fixed blocks for 1:1s, planning and unblocking others. Settle the questions below in week one and write the answers down.

  • Who approves time off, overtime and schedule changes?
  • Do you write, contribute to or only give input on performance reviews?
  • Do you interview and decide on hires, or give a recommendation?
  • Which decisions can you make alone, and how much of your week goes to hands-on work?

Your first week as a team lead: checklist and people to meet

Week one is about relationships and facts, not changes. People want to know if you will listen, be fair and shield them from chaos. You show that by asking good questions and following up on small requests fast.

Book these meetings in your first five days. Keep each one short and come with questions, not a pitch. Write notes in the same format every time so you can compare answers later.

  • Your manager: expectations for day 30, 60 and 90, team goals, open people issues and how they want updates.
  • Each direct report: a 30-minute 1:1 with the same four questions for everyone.
  • The previous lead, if reachable: open commitments, known risks and what they wish they had fixed.
  • Peer team leads: how your team's work affects theirs and where handoffs break.
  • Your main internal customer: the product manager, sales manager or operations lead who relies on your team's output.
  • Your HR business partner: leave policies, how performance issues are handled and how new hires are onboarded.

Promoted from within vs hired from outside

If you were promoted from inside the team, the hard part is the shift from peer to lead. Some people will be happy for you, someone may have wanted the job, and everyone will watch how you handle old friendships. Say it out loud in your first team meeting: the relationship is changing, you will apply the same rules to everyone, and you want feedback on how you are doing. Then hold a private 1:1 with anyone who applied for the role and ask how you can support their growth.

Former peers also expect you to keep doing your old job. Be clear about which tasks you are handing back and to whom. If you fix every hard problem yourself, you take learning chances away from the team and become the bottleneck.

If you were hired from outside, your challenge is context and credibility. Spend more time in the first two phases, ask why things work the way they do before judging them, and pick a quick win the team itself asked for.

Example: a support team lead's first 90 days

Here is the plan filled in for an agent promoted to lead a team of eight people handling tier 1 and tier 2 tickets in a help desk tool. The new lead still takes escalations for a couple of hours a day.

Each line has an owner and a result you can check, which makes the plan easy to review at each checkpoint.

  • Days 1-30, learn (owner: team lead): 1:1s with all eight agents, observed the morning queue review, read recent escalations, met the tier 3 lead and the billing product manager. Milestone: listening summary showing unclear escalation rules and outdated macros as the top two problems.
  • Days 31-60, own the routines (owner: team lead, with one senior agent): weekly 1:1s in place, working agreement on queue rotation and escalation rules written with the team, macro clean-up owned by the senior agent. Milestone: escalation rules published, old macros retired, first-response time baseline recorded.
  • Days 61-90, improve and grow (owner: team lead): development goal for each agent, one agent trained to run the weekly queue review, next-quarter plan drafted with a staffing request for the seasonal peak. Milestone: plan approved by the support manager, with first-response time and reopen rate reported against the baseline.

Metrics a new team lead should track

Pick a few measures that show delivery, quality and team health, and record a baseline before you change anything. Use what the team already tracks in Jira, Azure DevOps, a help desk or a CRM rather than adding a new system in your first month.

Report trends, not single weeks. Never use these numbers to rank people in front of the team, or they will start working for the number instead of the result.

  • Throughput: items finished per week or per sprint, counted from your board or ticket system.
  • Cycle time: average days from started to done. A rising number often points to blocked handoffs.
  • Quality: bugs found after release, reopened tickets or customer complaints per week, depending on the team's work.
  • Commitments met: planned items delivered in the week or sprint they were planned for, against the total planned.
  • Team health: one anonymous pulse question each month, such as how clear priorities are on a 1 to 5 scale.

How to present your plan to your manager or in an interview

For your manager, keep it to one page or one slide with three columns: days 30, 60 and 90. In each column put the goal, three or four actions and one milestone. Add a bottom row for the metrics you will report and the support you need from them. Leave out task-level detail. Your manager wants to see that you will listen before you change things, that you know which results matter and that you will raise risks early.

In an interview, the plan shows you understand the job before you have it. Say what you would learn in the first 30 days and who you would meet. Give one example of a quick win you might look for, framed as an idea you would test with the team. End with how you would measure success at day 90. Interviewers often ask what you would do in your first week, so have a two-sentence answer ready. Update the plan openly at day 30 and day 60: a plan that changes after you learn more shows you were listening.

Common mistakes to avoid

  • Changing processes in your first two weeks makes the team feel judged, so observe and ask why for the whole first month before you redesign anything.
  • Keeping your full workload as an individual contributor leaves no time to lead, so agree on a cap with your manager and hand work back on purpose.
  • Holding 1:1s only when there is a problem makes them feel like warnings, so set a regular rhythm by week five and keep it even in busy weeks.
  • Treating former peers differently, either stricter or friendlier, damages trust, so apply the same rules to everyone and say so openly.
  • Solving every hard problem yourself turns you into the bottleneck, so coach the person who owns it and step in only when a deadline or customer is at risk.
  • Reporting only activity, like meetings held, hides whether the team improved, so share a before-and-after metric at day 60 and day 90.

Frequently asked questions

What should a team lead do in the first 30 days?

Listen and learn. Hold a 1:1 with every team member, sit in on all team rituals without changing them, and agree on your scope with your manager. End the month with a short summary of the workflow, the team's strengths and the top problems you heard.

How is a team lead 30-60-90 day plan different from a manager's plan?

A team lead plan spends more time on daily delivery and hands-on work, and less on budgets, hiring and org design. It must also settle which decisions you can make alone, since that varies between companies.

What are good quick wins for a new team lead?

Pick something the team already complains about and can fix in a few weeks: unclear intake, a slow review step, an outdated runbook or a meeting nobody needs. The quick win should come from the team's own list, not from habits at your old team or job.

How do I lead people who used to be my peers?

Name the change openly in your first team meeting, then hold a private 1:1 with each person. Apply the same rules to everyone, including friends. Hand back your old tasks clearly and ask for feedback on how you are doing at day 30.

Should I bring a 30-60-90 day plan to a team lead interview?

Yes, if you keep it to one page. Show what you would learn, who you would meet and how you would measure success. Frame any changes as ideas to test with the team, since you do not know the full context yet.

Generate this roadmap with AI