Team review sessions are regular structured reviews where people we look at how people are doing, create feedback for them for the period and decide whether there should be any promotions.

Everybody in the Engineering Team will have regular one-to-ones with their line manager where they should be identifying their successes and where they can improve. This should be coupled with regularly scheduled reviews of the Growth & Progression Framework.

Why we have this process

Transparency & Uniformity

Individual progression should be a transparent and uniform process for everybody and the reasons for a promotion (or lack of) should be justifiable based on a matrix that everybody is compared against.

To maintain our standards

We want to maintain the high working standards that we have at SH:24 and so we need a robust method of making sure that those don’t slip as more people join us or progress.

How the process works

  1. Identify somebody from outside of the company to be part of the process. This is so that we have somebody neutral who can make sure what we’re saying is justified.

    Before the sessions

  2. Create a private Trello board with each position we have (Junior, Mid, Senior etc) and a card for each member of the Engineering Team.

  3. Add team review sessions to all relevant people’s calendars (EM, VP, the external collaborator) well ahead of time to give them time to prepare. We likely want this to be split into two or three sessions so we’re giving everybody the time they deserve and not getting tired. Make sure to link the Trello board so they can update it and read through it ahead of time.

  4. The line manager for the person being discussed should fill the person’s card in with information on that person’s achievements, how they’ve improved and any feedback they’ve received over the last 6 months.

    1. Gather feedback from the Tech Lead and Product Owner on the person’s team.
    2. Go through the last 6 months with the person and pick out key achievements. Searching on Shortcut and reviewing previous 1:1s can help with this.
    3. Add comments from the previous session so we can review where they were.

During the progression sessions

  1. Go through each person on the board and read through all the evidence and feedback on their card. Go through their level in the Growth & Progression framework and see how they’re doing against it and potentially the level above. We also want to consider the Peter Principle and (interestingly named) Law of Crappy People.
  2. Take all the evidence we’ve gathered into account and move them to the appropriate column i.e. (junior, mid, senior etc). Also mark them as low, mid, or high within those bands i.e. somebody could go from a mid-mid to a high-mid indicating that we think they’re at the top of what we’d expect from a mid-level engineer and potentially heading towards a senior position.
  3. Make thorough notes throughout and concentrate on why decisions have been made so we can relay this to people in their next 1:1s.
  4. Once we’ve gone through everybody and decided if somebody should change role we can then review all the changes and the new structure of the teams.

After the session

Create a spreadsheet with all of the changes so that it’s clear what was decided and any progress on the changes can be easily tracked.

The VP of Engineering will communicate the proposed changes to the Directors and agree what changes we can make. Once this is confirmed this can be passed along to the relevant managers. Make sure this is communicated in writing so there isn’t any confusion.