People Ops Guide

Review season guide
for founders and senior leaders

Everything you need to think through before the end-of-year review cycle: why it matters, the mistakes to avoid, a month-by-month plan, and what a good growth matrix looks like.

01

The review cycle is as much for you as for your team

Too often a review cycle is treated as an HR formality, something to run once or twice a year, check off, and forget. The best leaders treat it as a chance to step back and ask a strategic question: does the team have what it takes to reach company aspirations, and how can we support their development?

Done well, it creates a culture where growth is planned, fair, and predictable, instead of being reserved for the loudest voices in the room.

A well-orchestrated and thought-out review cycle can give you visibility on three things: the skills you have in the org and the ones you're missing, the people who hold the company together, and how performance compares to expectations.

Skill map across the team

A map of existing capabilities compared to expected coverage for your industry, size and type of projects

Skill coverageCovered · 6Gap · 3
Visual design8UX research6Strategy5Brand storytelling4Prototyping4Workshop facilitation3Accessibility-Illustrations-Data analytics-
Informal networks

The hidden org chart demonstrating who carries critical knowledge, who might be a bottleneck and what people work well together

Most selected people
Mira Okonkwo
12
Daniel Reis
10
Inés Vargas
9
Renée Adler
8
Tomás Bohra
8
Tony Madden
7
Gabriel Liu
7
Rafael Marín
6
37%
Reciprocity rate
Mira⇄Renée
Daniel⇄Tomás
Inés⇄Tony
Gabriel⇄Rafael
Holistic organisation health view

A radar across the dimensions of your growth model as well as the distribution curve across levels and skills

Rating distribution
BelowApproachingOn-trackAdvancedOutstanding
Name
Level
Dept
Final
Promo
Jordan Lee
L4
Design
On-track
-
Riley Park
L5
Design
Advanced
-
Taylor Kim
L3
Engineering
Advanced
▲Promo
Alex Chen
L3
Marketing
On-track
-

02

If you're going to run reviews, make them worth it

The companies we work with run reviews because they genuinely care about their people. Here are the practices that make the difference between a cycle that drains everyone's energy and one people look forward to.

#
What we see
What to do instead
01
Assume people will use AI
Even when you explicitly discourage it, people will use AI to prepare their self-reflections and growth memos. The risk is that without guidance, the output will be generic, and leave both sides confused: the person reading the self-reflection, and the person reading the feedback memo.
Give people guidance on using AI meaningfully: to help articulate things they would otherwise struggle to put into words, to summarise feedback conversations, to prepare for difficult discussions. Set up a prompt, share an example of good output, and set the expectation clearly: AI should be used to prepare for human conversations, not to replace them.
02
Keep feedback and reviews separate
Feedback and the review cycle get collapsed into the same meeting. What should have been day-to-day feedback is delivered a year later, and what should have been a strategic, forward-looking conversation becomes a heavy backward-looking assessment. People feel judged on things they were never told about.
Keep them separate by design. Feedback is continuous: tied to real work, given quickly, specific to a moment. The review cycle is strategic: it looks at patterns over time. When people receive regular feedback throughout the year, the review conversation becomes lighter, more forward-looking, and easier for everyone in the room.
03
Run the cycle for the whole company at once, not person by person
Reviews happen on individual start dates, or whenever there is time. Calibration becomes almost impossible. One person's “strong performer” is another's “meets expectations”, and no one ever compares notes.
Pick two fixed moments a year and have everyone move through the cycle together. That makes ratings consistent, promotion decisions defensible, and the process something people trust. It also creates a shared moment when the organisation pauses to reflect.
04
Build and communicate shared criteria
Promotions happen when someone asks loudly enough, when it feels like the right time, or, worse, when someone threatens to leave. There is no shared understanding of what "senior" means, and people who don't get promoted have no idea why.
A simple growth matrix, even if it's only three levels, gives everyone a shared reference point. It does not need to be perfect, but it does need to exist. When the criteria are explicit, growth conversations become easier to run, to hear, and to act on.
05
Use structure to protect the culture you have built
When you have built something informal and human, adding process can feel like a threat, so it gets delayed. Meanwhile, the best people start wondering what their next chapter here looks like, and they eventually stop waiting once they're offered a better title elsewhere.
Build cultural expectations into the career matrix so that everyone can advocate for them: how people treat each other, how they communicate with clients, which information gets shared and which stays internal. The matrix is the best place to make culture explicit, especially if you want to protect it as you scale.
06
Design for fairness
Every review process has bias in it. When you run calibration alone, or without a shared framework, the people who get recognised are often those who are most visible, most vocal, or most similar to whoever is making the decisions, not necessarily the best people.
Name the biases before the cycle starts: recency, affinity bias, halo effect. Run calibration with more than one person in the room: different perspectives will help surface different things. Use a written memo to force reasoning into words.

Turn what you learn running reviews into posts people read100 free credits, about ten posts. No card needed.
Try Lantern for free
03

Now is exactly the right time to start preparing for your end-of-year cycle

Here are the practical things that will get you moving, before the calendar fills up and September arrives faster than expected.

Block the dates

Open your calendar and protect the key moments: when the cycle kicks off, when self-reflections go out, when feedback collection closes, when growth conversations happen, and when the all-hands wraps it up. Everything else follows from these dates. If they are not in the calendar, the cycle will not happen.

Check whether you have a career framework

A simple three-level model is enough to run a meaningful cycle. It does not need to be perfect. If you do not have one yet, starting now gives you two months before the cycle opens, enough time to iterate and test.

Decide who will run the growth conversations

This could be you, your team leads, or your managers, whoever has the skillset to do it well. They need to understand the process, be able to dedicate the time, and feel prepared to have an honest conversation.

April
May
June
Set up the cycle
Decide your process (self-reflection, peer feedback, manager input)
Confirm your career framework, build a simple one if missing
Identify who will run the growth conversations
July
Build the templates
Prepare self-reflection memo + feedback form
Run brief conversation on the process with key leaders
August
Announce the cycle
Communicate to the team with 4 weeks’ notice minimum
Share self-reflection prompts and timeline
September
Reflect & collect
Kick-off self-reflection preparation
Open feedback collection
Collect exposure lists
October
Submit & calibrate
Collect self-reflections and feedback summaries
Run a calibration discussion, including key leaders
Prepare final growth memos
November
Hold conversations
Run growth conversations (30-45 min)
Announce promotions and celebrate publicly
Share key insights and success stories on all-hands
December
Comp & close-out
Share a written note with every person: this and next year total comp and bonus amounts

04

Get started with a career matrix

A growth matrix is the document everyone refers back to: what is expected, what looks like progress, how someone earns the next level. These are the five things that make one actually useful.

Describes behaviours, not traits or expectations

A useful matrix describes what someone does, not what they are. 'Communicates clearly with clients' is actionable. 'Good communicator' is not. When the criteria are behavioural, conversations become specific and growth becomes visible.

Tied to how your company actually operates

A matrix copied from a big tech firm does not work for a 40-person brand company. The dimensions and the language should reflect your services, your clients, and how value gets created in your context.

Built with the future in mind

The matrix should reflect what your team does day to day while also accommodating the strategy you are implementing. If there are specific skills, industries, or types of knowledge you want to build, the matrix should reflect them: think about AI in creative workflows, for example.

Dimension
…
Mid DesignerL2
Senior DesignerL3
Lead DesignerL4
…
…
…
…
…
…
…
Craft
…
  • Applies interaction and visual design skills independently on assigned work.
  • Uses AI tools to speed up early-stage exploration.
  • Leads research, prototyping, and design phases.
  • Knows design systems deeply.
  • Applies AI and data tools to test assumptions faster.
  • Sets design direction across multiple tracks.
  • Guides the team on where AI improves workflows and where human judgement matters more.
…
Client impact
…
  • Sees how own work connects to the client goal.
  • Delivers work that holds up to brand standards without heavy rework.
  • Identifies the right problems to solve, including those beyond what is explicitly assigned.
  • Makes sure output is tied to what the client actually needs.
  • Knows the client's business well enough to see what they will need before they ask.
  • Aims to be someone the client invites into conversations beyond the current project.
…
Leadership
…
  • Shares useful things learned with peers.
  • Helps new hires get productive by guiding them through tools and how the team works.
  • Runs regular check-ins with juniors.
  • Gives feedback that is specific and actionable: people leave the conversation knowing exactly what to work on.
  • Sets clear growth expectations for each team member.
  • Creates stretch opportunities.
  • Team members visibly grow in skill and confidence over time.
…
…
…
…
…
…
…

Lantern for people leaders

Turn what you learn running reviews into posts people read

Every review cycle leaves you notes on what worked and what you would change. Lantern turns them into a week of posts in your voice, so the lessons reach your team, your peers and the people you will hire next.

Try Lantern for free

100 free credits, about ten posts. No card needed.

Use this guide with your AI

Hand the whole guide to ChatGPT, Claude or Perplexity, and have it turned into a plan for your team, your cycle and your dates.

No download, no email. It reads the guide itself and asks you the rest.

Prefer the file? Markdown copy

We're 60 people and reviews start in November. What should we be doing now?

Working back from November, the guide puts expectations and the growth matrix first, well before anyone writes a self-review. Agree what each level means, tell people the dates, and decide now who calibrates and how pay is separated from feedback.