Description

This curriculum spans the design and operational challenges of performance appraisal in technical management, comparable in scope to a multi-workshop program for implementing a company-wide engineering performance system, addressing everything from metric selection and calibration to legal compliance and organizational scaling.

Module 1: Defining Technical Performance Metrics

Selecting between output-based metrics (e.g., commits, deployments) and outcome-based metrics (e.g., system stability, incident resolution time) for engineering roles.
Aligning individual KPIs with team-level SLOs without creating misaligned incentives.
Deciding whether to track developer velocity and how to normalize for task complexity and team context.
Integrating qualitative peer feedback into quantitative performance dashboards without diluting objectivity.
Handling discrepancies between automated telemetry (e.g., CI/CD throughput) and managerial perception of contribution.
Designing role-specific metrics for specialized positions such as DevOps, data engineers, or security specialists.
Addressing the risk of metric gaming by adjusting scoring thresholds and review frequency.
Determining the frequency and scope of metric recalibration based on project lifecycle and organizational changes.

Module 2: Calibration Across Technical Teams

Establishing a cross-team calibration panel with technical leads to reduce rater bias in performance scoring.
Resolving conflicts when team norms differ (e.g., one team documents extensively, another relies on tacit knowledge).
Standardizing performance bands while preserving technical autonomy in evaluation criteria.
Managing calibration sessions when senior engineers report to managers with less technical depth.
Documenting calibration decisions to ensure auditability and consistency across cycles.
Adjusting for team size and reporting structure when comparing individual performance across departments.
Handling cases where high performers in low-velocity teams appear underperforming relative to high-velocity teams.
Integrating 360 feedback from cross-functional partners (e.g., product, QA) without overburdening reviewers.

Module 3: Integrating Code and System Contributions

Weighting code contributions versus architectural guidance or mentoring in performance evaluations.
Attributing impact for contributions to shared systems where ownership is distributed.
Using code review participation as a performance signal without incentivizing nitpicking or gatekeeping.
Assessing contributions to technical debt reduction when outcomes are long-term and indirect.
Validating self-reported contributions against version control and incident management data.
Recognizing non-code contributions such as improving CI/CD pipelines, documentation, or on-call effectiveness.
Deciding whether automated code metrics (e.g., lines changed, test coverage) should influence promotion decisions.
Handling discrepancies between code volume and actual business impact in evaluation narratives.

Module 4: Managing Peer and 360 Feedback

Selecting reviewers who have sufficient context on the employee’s recent work without creating political friction.
Structuring feedback prompts to elicit specific, behavior-based responses rather than vague endorsements.
Addressing retaliation concerns when junior engineers provide feedback on senior technical staff.
Aggregating conflicting peer feedback without defaulting to managerial override.
Deciding whether to disclose peer reviewer identities and the impact on feedback honesty.
Using 360 data to identify collaboration gaps without pathologizing introverted or independent work styles.
Training technical leads to interpret qualitative feedback consistently across reports.
Archiving feedback data securely to comply with data privacy regulations and internal policies.

Module 5: Performance Reviews in Agile and Matrix Organizations

Assigning accountability for performance reviews when engineers report to functional managers but work in product teams.
Aligning sprint-based delivery expectations with annual or biannual review cycles.
Handling performance issues in agile teams where work is collaborative and individual contribution is diffused.
Integrating retrospective insights into formal performance documentation without breaching team confidentiality.
Managing dual reporting lines when technical managers and project leads provide conflicting performance assessments.
Adjusting review timelines to accommodate project deadlines and avoid review fatigue.
Ensuring that agile role rotation (e.g., rotating scrum master) does not distort performance signals.
Documenting performance decisions in a way that supports both career development and resource allocation.

Module 6: Addressing Underperformance in Technical Roles

Distinguishing between skill gaps, motivation issues, and environmental constraints in underperformance cases.
Designing performance improvement plans that include measurable technical outcomes, not just behavioral goals.
Providing technical coaching without undermining the employee’s credibility with peers.
Deciding when to reassign an engineer to a different project versus initiate formal disciplinary action.
Documenting technical shortcomings using code samples, incident reports, or peer feedback.
Managing senior engineers who resist feedback due to tenure or technical reputation.
Handling cases where underperformance stems from outdated technical skills in rapidly evolving domains.
Ensuring legal defensibility when terminating employment based on technical performance.

Module 7: Linking Performance to Career Progression

Mapping performance outcomes to promotion criteria in technical ladders (e.g., Staff, Principal Engineer).
Assessing leadership beyond management, such as technical vision, cross-team influence, and mentorship impact.
Handling cases where high performers do not seek promotion but must meet evolving role expectations.
Using performance data to identify candidates for stretch assignments or leadership development programs.
Aligning compensation adjustments with documented performance trends, not just annual review scores.
Addressing disparities in promotion velocity across teams with different review rigor.
Documenting promotion decisions with evidence from multiple review cycles to reduce bias claims.
Managing expectations when performance exceeds promotion bandwidth due to organizational constraints.

Module 8: Legal and Ethical Compliance in Technical Evaluations

Ensuring performance documentation does not include proxies for protected characteristics (e.g., "lacks assertiveness" in gendered contexts).
Storing performance records in compliance with GDPR, CCPA, and other data privacy regulations.
Training managers to avoid discriminatory language in written evaluations (e.g., age-related assumptions about learning speed).
Conducting regular audits of performance data for demographic disparities in ratings and promotions.
Handling employee requests to access or correct performance records under data subject rights.
Defining retention periods for performance documents and securely disposing of obsolete records.
Implementing access controls so only authorized personnel can view or modify performance data.
Creating escalation paths for employees who believe their evaluations are biased or factually incorrect.

Module 9: Scaling Performance Systems in Growing Tech Organizations

Transitioning from ad hoc reviews to standardized processes as engineering teams exceed 100 members.
Selecting performance management software that integrates with existing tools (e.g., Jira, GitHub, Slack).
Training new engineering managers on performance evaluation protocols during rapid hiring phases.
Preserving cultural values (e.g., autonomy, innovation) while introducing formal performance structures.
Managing consistency in evaluations across geographically distributed teams with different labor norms.
Automating data collection from version control, ticketing, and monitoring systems without increasing surveillance perception.
Adjusting review frequency and depth based on organizational layer (e.g., ICs vs. Directors).
Establishing feedback loops to refine the performance system based on manager and employee input.