Manu's Vault

Performance Management System

3 min readStatus:Seedling

Core Idea

Most performance management failures are systemic design failures, not individual manager failures. A coherent system requires three mutually reinforcing components — a career ladder, consistent designations, and structured review cycles — none is sufficient without the others.

Performance Management System

Engineering performance management fails most often not because managers are poor evaluators, but because the underlying system is incoherent. Larson identifies a three-part architecture that must work in concert.

The Three Components

1. Career Ladder

  • Documents expected scope, impact, and observable behaviours at each level (Engineer I → Senior → Staff → Principal)
  • Good ladders are: criterion-referenced (compare to the level definition, not to peers), behaviorally specific (observable actions and outcomes), and progression-oriented (explicitly describe growth from N to N+1)
  • Bad ladders are: vague, peer-comparative, or lists of technologies with no behavioural grounding

2. Designations

  • The label applied to each person at a point in time, assigned through a consistent documented process
  • Must mean the same thing across teams — cross-team calibration is essential

3. Review Cycles

  • The structured process for assessing performance, updating designations, and adjusting compensation
  • Creates a predictable rhythm; produces written performance feedback, designation confirmation or change, compensation adjustment

Why All Three Must Be Coherent

  • Ladder without consistent designations: Aspirational but unfair — people levelled arbitrarily against a document they can see
  • Designations without a ladder: Arbitrary — no shared standard for what a designation means
  • Review cycles without a ladder or designations: Just salary discussions — no framework for growth conversations
  • All three without calibration: Drift — designations diverge in meaning across teams over time

Common Failure Modes

  • Ladders that describe “what you do” rather than “what you deliver and how”
  • Designation decisions made ad hoc rather than through a structured cycle
  • Review cycles that skip feedback and jump straight to compensation
  • No cross-team calibration, causing “Senior” to mean radically different things across the organisation
  • Career-Stagnation-and-Growth as a downstream consequence: without a clear growth path, engineers plateau in place

Sources

  • Larson, Will (2019). An Elegant Puzzle: Systems of Engineering Management. Stripe Press. ISBN: 978-1-7322651-8-9.

    • Chapter 6.5 — primary framework for the three-part performance management architecture

  • DeNisi, Angelo S. and Robert D. Pritchard (2006). “Performance Appraisal, Performance Management and Improving Individual Performance.” Management and Organization Review, Vol. 2(2), pp. 253–277. DOI: 10.1111/j.1740-8784.2006.00042.x.

    • Argues for shifting focus from measurement accuracy to performance improvement; theoretical basis for criterion-referenced assessment

  • Awan, Sajid Hussain, et al. (2020). “Effectiveness of Performance Management System for Employee Performance Through Engagement.” SAGE Open, Vol. 10(4). DOI: 10.1177/2158244020969383.

    • Empirical study (N=285) showing coherent, fair system design predicts task and contextual performance

  • Holloway (2021). The Holloway Guide to Technical Recruiting and Hiring. Holloway.

  • Orosz, Gergely (2022). “Performance Reviews for Software Developers.” The Pragmatic Engineer. Available: https://blog.pragmaticengineer.com/performance-reviews-for-software-engineers/

    • Practitioner account of criterion-referenced reviews at scale; cross-team calibration in practice

Note

This content was drafted with assistance from AI tools for research, organization, and initial content generation. All final content has been reviewed, fact-checked, and edited by the author to ensure accuracy and alignment with the author’s intentions and perspective.

Graph View

Backlinks