← All articles

Filling out your end-of-year review as a new development team leader

7 min read

  • Leadership
  • Career
  • Team Leading
  • Performance Reviews

Your first end-of-year review as a team leader feels different from the ones you wrote as a developer. Before, you could list what you built. Now, much of your best work is invisible: the blocker you removed, the junior developer who got more confident, the release that didn’t go wrong.

This guide keeps it simple: what to gather, how to write each section, and a template you can copy.

Step 1: Gather your evidence first

Don’t start writing from memory. You’ll remember the last two months and forget the first ten. Spend 30 minutes collecting:

  • Your objectives from the start of the year (or from when you became team leader)
  • Releases and projects the team delivered: your backlog, sprint history, release notes
  • Incidents and how they were handled
  • Your 1:1 notes with your team and your manager
  • Feedback you’ve received: emails, Teams or Slack messages, thanks from other departments
  • Changes you introduced: new processes, standards, tools, documentation
  • Training you’ve done, and anything you’ve learned on the job

Tip for next year: keep a running “wins” document and add a line every Friday. It turns this job from an afternoon of digging into ten minutes.

Step 2: Understand the shift from “I” to “we”

As a developer, you were judged on what you delivered. As a team leader, you’re judged on what the team delivers and how you made that possible.

As a developer As a team leader
“I built the new reporting screen.” “The team delivered the new reporting screen two weeks early. I broke the work down, cleared a dependency on the data team, and paired with our junior developer on the hardest part.”
“I fixed 40 bugs.” “I introduced a weekly bug triage, which cut the open bug count from 60 to 25.”
“I reviewed pull requests.” “I set up a code review checklist so reviews are faster and more consistent across the team.”

It’s fine to mention hands-on work you still do, but lead with team outcomes and your part in them.

The areas a team leader’s impact usually falls into:

  • Delivery: did the team ship what mattered, reliably?
  • People: did your team grow, stay engaged and get support?
  • Quality and process: did things get better, safer or faster?
  • Stakeholders: did the business trust the team and know what was coming?
  • Yourself: how did you grow into the role?

Step 3: Write achievements that show impact

For each achievement, use a simple three-part shape:

What the situation was → what you did → what changed as a result

And add a number wherever you honestly can: time saved, incidents reduced, releases shipped, people trained.

Weak:

Worked on improving deployments.

Strong:

Deployments were manual and took most of a morning, so the team avoided releasing. I led the move to an automated pipeline with a test stage. Releases now take 20 minutes, and we went from monthly to weekly releases with no rollbacks since June.

Weak:

Supported the team.

Strong:

Started fortnightly 1:1s with each developer. One developer used them to plan a move into backend work and now owns our main API. Another raised workload concerns early, so we rebalanced before it became a problem.

Pick your three to five best achievements. A long list of small things dilutes the big ones.

Step 4: Be honest about challenges

Every reviewer knows the first year as a leader is hard. A review with no challenges reads as either unaware or not honest. Pick one or two real ones and show what you learned and changed:

Early on, I kept taking the hardest tickets myself, which made me a bottleneck and meant the team wasn’t stretched. Since September I’ve been assigning those to developers and supporting through pairing and reviews instead. It’s slower at first, but two developers can now handle work only I could do before.

Common first-year challenges that are worth naming:

  • letting go of coding and delegating
  • giving difficult feedback, especially to former peers
  • balancing meetings with time for the team
  • saying no, or “not yet”, to stakeholders
  • managing your own workload alongside everyone else’s

Step 5: Set clear goals for next year

Make them specific and measurable, so next year’s review is easy to write. A mix of the five areas works well:

  • Delivery: “Deliver the customer portal phase 2 by Q2, with release dates communicated to stakeholders a month ahead.”
  • People: “Hold monthly career conversations with each team member and agree a development goal for each by March.”
  • Quality: “Raise automated test coverage on our core services and add tests to the pipeline so every release runs them.”
  • Process: “Introduce a quarterly retrospective on how we work, and act on at least one change from each.”
  • Yourself: “Complete a leadership course and get 360 feedback from my team by the end of the year.”

Step 6: Ask for what you need

The review is a chance to ask for support, and new leaders often forget to. Be specific:

  • training, such as a leadership or management course
  • a mentor who’s a more experienced team leader
  • clearer priorities, or more say in them
  • headcount, tools or time to pay down technical debt

A template you can copy

Summary In my first year as development team leader, the team [biggest outcome]. My focus has been [two or three themes, e.g. reliable delivery, growing the team, improving how we work].

Objectives [Objective 1]: Met / Partly met / Not met. [One or two lines of evidence.] [Objective 2]: …

Key achievements

  1. [Situation] → [what I did] → [result, with a number if possible]
  2. …
  3. …

Leading the team [How you supported, developed and looked after the team: 1:1s, coaching, recognition, wellbeing, hiring or onboarding.]

Challenges and what I learned [One or two honest challenges, what you changed, and the result so far.]

Goals for next year

  1. [Specific, measurable goal]
  2. …

Support I’d like [Training, mentoring, resources.]

If you’re also reviewing your team

As a new team leader you may be writing reviews for your developers too. A few basics:

  • No surprises. Nothing in a review should be news. If something’s important, it should already have come up in 1:1s.
  • Use evidence, not impressions. Use specific examples, and the same Situation → Behaviour → Impact shape: “In the March release (situation), you wrote the rollback plan without being asked (behaviour), which meant we recovered in ten minutes when the migration failed (impact).”
  • Balance it. Recognise strengths properly, not just as a warm-up before the criticism.
  • Look forward. Spend as much time on next year’s growth as on last year’s performance.
  • Ask for their view first. Read their self-assessment before writing yours, and ask what support they want from you.

Common mistakes

  • Writing it the night before. Give yourself time to gather evidence and redraft.
  • Only listing tasks. Say what changed because of them.
  • Underselling yourself. “Helped with” often means “led”. Be accurate, not modest.
  • Taking all the credit, or none. Credit the team, and be clear about your part.
  • Vague goals. “Be a better leader” can’t be measured. “Hold monthly career conversations with each developer” can.
  • Ignoring your company’s framework. If your company has values or competencies, link your examples to them, using their wording.

Checklist before you submit

  • Evidence gathered from the whole year, not just recent months
  • Three to five achievements, each with a clear result
  • Team outcomes first, with your part in them
  • One or two honest challenges, with what you learned
  • Specific, measurable goals for next year
  • Support or training requested
  • Linked to your company’s values or competencies where they apply
  • Read through once out loud: would your manager recognise every example?

Sources