Annual Review Template by Kevin Lee

Standard Operating Procedure: Execution and Governance of the Kevin Lee Annual Review Template

---

1. Executive Summary & Purpose

1.1 Purpose

This Standard Operating Procedure (SOP) defines the institutional protocol for executing, calibrating, and archiving performance evaluations utilizing the Kevin Lee Annual Review Template. The objective is to standardize performance appraisal metrics, eliminate subjective bias, ensure longitudinal data integrity across engineering and product organizations at Template Registry, and align individual output with systemic corporate OKRs.

1.2 Objective

To establish a repeatable, mathematically sound framework for assessing technical execution, leadership, systemic impact, and operational hygiene over a rolling 12-month evaluation window.

---

2. Scope & Prerequisites

2.1 Scope

This SOP applies to all engineering tiers (L3 through L7), Senior Systems Architects, Engineering Managers, and the Office of the CTO within Template Registry.

2.2 Prerequisites & Required Tooling

• Software Environment: Access to Template Registry’s internal HRIS (Workday Enterprise v24.2), secure Notion workspace (Template Registry Architecture Tier), and encrypted local execution environments (Git/Markdown parser).
• Reference Artifacts:
  • Master Kevin Lee Annual Review Template (.md or .gdoc schema v2.1).
  • 12-Month Git Commit Logs, Jira/Linear Velocity Reports, and Post-Mortem Contributions.
  • Q1–Q4 OKR Attainment Sheets.
• Safety/Compliance: Strict adherence to GDPR and internal confidentiality protocols; PII redaction mandatory prior to archival.

---

3. Roles & Responsibilities (RACI Matrix)

---

4. Step-by-Step Procedure

Phase 1: Data Gathering & Artifact Compilation

• 1.1 Export the last 52 weeks of Jira/Linear issue resolution metrics, highlighting cycle times, bug-to-feature ratios, and system reliability contributions.
• 1.2 Aggregate all System Architecture Documents (SADs), RFCs authored, and Pull Requests merged by the evaluatee.
• 1.3 Secure asynchronous 360-degree feedback from at least three cross-functional peers using the Kevin Lee Feedback Intake Form.

Phase 2: Template Initialization & Baseline Scoring

• 2.1 Clone the master Kevin Lee Annual Review Template into the designated secure evaluation directory: s3://tr-hr-evaluations-secure/[CALENDAR_YEAR]/[EMPLOYEE_ID]/.
• 2.2 Populate Section 1 (Core Competency Metrics) utilizing the 5-point calibration scale:
  • 1 - Unsatisfactory: Fails to meet systemic baselines; requires constant oversight.
  • 2 - Developing: Meets basic deliverables; inconsistent architectural adherence.
  • 3 - Proficient: Consistently delivers high-quality engineering outputs; reliable execution.
  • 4 - Advanced: Exceeds expectations; drives cross-team efficiency and mentors peers.
  • 5 - Exceptional: Industry-level impact; transforms organizational capabilities.
• 2.3 Calculate the weighted technical impact score based on the Kevin Lee formula: $\text{Score} = (0.4 \times \text{Execution}) + (0.3 \times \text{Systemic Impact}) + (0.3 \times \text{Leadership/Culture})$.

Phase 3: Drafting Qualitative Assessments & Growth Trajectory

• 2.4 Complete Section 2 (Systemic Impact & Technical Leverage) with concrete citations of codebases architected, technical debt reduced, or latency metrics optimized.
• 2.5 Document developmental bottlenecks and behavioral friction points in Section 3, ensuring all critiques are objective, behavior-focused, and paired with remediation strategies.
• 2.6 Formulate Section 4 (Next-Year Trajectory & OKR Alignment), establishing three measurable technical objectives for the upcoming cycle.

Phase 4: Calibration, Review, and Archival

• 2.7 Conduct calibration sessions with Engineering Leadership to normalize scores across cohorts and prevent grade inflation or deflation.
• 2.8 Execute the Synchronous Review Meeting (duration: 60 minutes) between Reviewer and Evaluatee; secure digital sign-offs within the template footer.
• 2.9 Encrypt and upload the finalized document to Workday HRIS, locking the record against further edits.

---

5. Quality Assurance & Pro-Tips

5.1 Pro-Tips for Systemic Accuracy

• Anchor to Artifacts: Avoid recency bias. Weight Q1 and Q2 performance equally with Q3 and Q4 by referencing the data gathered in Phase 1.
• Behavior Over Persona: Evaluate the systemic output of the engineer, not their communication style in isolation. Focus on how their technical decisions impact system throughput and team velocity.

5.2 Common Pitfalls to Avoid

• The "Center-Clustering" Trap: Giving all engineers a "3" to avoid conflict. If an engineer is exceptional or failing, use the appropriate bounds of the 1–5 scale with documented justification.
• Vague Qualitative Statements: Phrases like "needs to communicate better" are non-actionable. Instead, specify: "Must publish RFCs 5 business days prior to architectural changes to improve team alignment."

5.3 Metric Thresholds

• Any score of 1 or 5 across any metric must be accompanied by a minimum of 150 words of empirical justification and at least two verifiable audit artifacts.

---

6. Frequently Asked Questions (FAQ)

Q1: What happens if the evaluatee disputes their weighted score during the synchronous review meeting?
A1: The evaluatee must submit a formal rebuttal containing counter-artifacts within 5 business days. The Reviewer and the Chief Architect (Julian Vance) will review the counter-artifacts within 72 hours, and the resulting determination is final.

Q2: Can the Kevin Lee Annual Review Template be modified for non-technical roles within Template Registry?
A2: No. The Kevin Lee template schema is strictly calibrated for engineering and systems architecture competencies. Non-technical evaluations must utilize the administrative or product management variants (SOP-TR-HR-400 series).

Q3: How are historical review templates handled during corporate restructuring or management changes?
A3: All historical evaluations remain locked in the secure Workday HRIS repository. Incoming managers are required to read the preceding two cycles of Kevin Lee evaluations before drafting the subsequent annual review.