liveBook · Manning

Annual review

As explained in Think Like a CTO

An annual review is a periodic formal assessment of an employee's performance and development, typically conducted once each year.

An annual review is a planned check-in on an employee’s performance, progress, and development. It should clarify where the person excels, where improvement is needed, and what opportunities they want to pursue. Regular manager check-ins remain important: the annual meeting should not be the first time either person hears about a concern. Some organizations review more often, but extra cycles add overhead, especially when reviews coincide with compensation decisions. section 7.0 section 15.1

Make the review specific and manageable:

  • Define the expectations for each role and level in a ratable skill matrix. section 7.6
  • Set a date and give the employee at least a week’s notice. Share the matrix and ask for a self-assessment supported by examples. section 7.1.3
  • Complete your own assessment, using the previous year’s matrix when available. Rate the level at which the employee operates consistently; do not let one success or failure determine the result. section 7.1.3
  • Compare the two assessments in the meeting. Discuss differences, explain your reasoning, and agree on a clear path for improvement. section 7.1.3 section 7.6

When promotion is close

Suppose someone demonstrates a higher-level skill in one project but does not yet operate at that level consistently. Recognize the example without treating it as decisive. Identify what they still need to demonstrate and, if appropriate, set a date in six months to reassess rather than making them wait another full year. section 7.1.3

A review need not push everyone toward more responsibility; steady performance at a level that suits the employee can be a valid outcome. The same discipline applies to executives: if a formal review skips the CTO, they can ask the CEO for feedback on communication, business awareness, and technology direction, then request goals for the coming year. section 7.1.3 section 15.1

How Think Like a CTO covers it

How deep it goes
Provides a preparation and meeting procedure built around a skill matrix, consistent performance, and differences between employee and manager assessments.
Examples
Uses a near-promotion reassessment, differing self-ratings, and a CTO seeking CEO feedback as practical situations.
What it assumes
Assumes defined roles and levels and regular manager check-ins; supplies a matrix-based way to assess performance.
What you can do after
Practice/perform an evidence-led review that leaves the employee with a clear path to improvement.
How it connects
Connects annual reviews to regular check-ins, skill matrices, promotion decisions, and compensation timing.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a CTO. The section links point to the parts of the book it draws on.