Run Detail

Annual Performance Review — Marcus Reyes, Team Lead

Review period: January–December 2026

Summary

Marcus is a capable and committed team lead who consistently delivers strong results when he is directly engaged with a problem. His team's customer satisfaction and response-time metrics fell short of company targets this year, and several deadlines were missed, but his hands-on work during the Hendricks outage and his process improvements to refund handling demonstrate real operational value. With more consistent follow-through on commitments and stronger team communication, Marcus has the foundation to be an excellent lead.

Strengths

• Ownership under pressure. During the April Hendricks Property Management outage, Marcus took the escalation himself on a Saturday and stayed with it until resolution. Hendricks renewed in May at $48,000/year — a direct retention win attributable to his leadership.
• Process improvement. Marcus rewrote the refund macro in August, cutting refund-related ticket reopens from 22% to 9% within four weeks. This is exactly the kind of initiative that improves team performance at scale.
• Advocacy for his team. He proactively requested training budget for two agents, showing investment in their development.
• Accountability in scheduling. When he missed one-on-ones, he rescheduled them himself rather than letting them lapse.

Areas for improvement

• Meeting commitments and deadlines. The escalation runbook was delivered three days late (due Jan 30, delivered Feb 3), and the Q1 shift schedule went out March 27 against a March 15 due date. Late deliverables create downstream planning problems for the whole support organization.
• Team metrics below target. His team's CSAT was 87% in Q4 2025 and 84% in Q2 2026 against a 90% target, and April first-response time averaged 4h 10m against a 2h target. As team lead, Marcus is accountable for these outcomes even when individual agents contribute to them.
• Inclusive communication in team settings. Two agents separately reported that he talks over them in standups. While I have not observed this directly, two independent reports warrant attention and a change in how he runs team meetings.
• Interpersonal tone with customers. A customer described Marcus as "short" on a call (reported via Sales in June). The report could not be verified — no ticket or recording — but combined with the standup feedback, it suggests a pattern worth addressing.
• One-on-one consistency. Missing two of the last four one-on-ones, even with rescheduling, signals that coaching time is being deprioritized when the queue backs up.

Goals for next year

1. CSAT: Raise his team's quarterly CSAT to at least 90% in at least three of four quarters, measured by the standard quarterly CSAT report.
2. Response time: Reduce his team's average first-response time to 2 hours or less by Q3, measured monthly against the ticketing system.
3. Deadline and meeting reliability: Deliver 100% of assigned deliverables by their due dates and attend at least 90% of scheduled one-on-ones without rescheduling, tracked in our shared project tracker and calendar records.

Overall rating

Meets expectations. Marcus delivers real, measurable wins — the Hendricks renewal and the refund macro improvement — but his team's core metrics fell short of target all year and several commitments slipped, which keeps him from exceeding expectations.

Notes for me

Things I deliberately left out or softened, and why:

• The medical leave (Mar 2–23). I left it out entirely. It's protected information, it's irrelevant to performance assessment, and including it — even neutrally — in an HR file creates legal exposure and could look like it factored into the rating. If Marcus raises it, the answer is that it played no role.
• The "short with a customer" report. I included it in Areas for improvement but heavily caveated it. Here's the thing: it's unverifiable hearsay relayed through Sales, with no ticket, no recording, and no identifiable call. I included it because ignoring a customer-facing complaint entirely would be negligent, but I framed it as a pattern signal alongside the standup feedback rather than a standalone finding. If Marcus pushes back on it, I should be prepared to say it was one unverified data point weighed together with more concrete feedback — and that no disciplinary weight rests on it alone.
• The standup feedback. I included it because two independent reports from his own team is meaningful, but I noted I haven't witnessed it myself. That's honest and fair to him; it also documents that I took it seriously.
• The training budget detail ($450, one course approved). I mentioned he asked, which is a strength, but not the dollar amount — it's not relevant to his review and could read as a subtle dig about cost.
• The refund macro numbers. I kept these specific (22% → 9%) because concrete wins make the review credible and give Marcus something real to point to. Specific praise is more motivating than vague praise.
• The one-on-one misses. I included them but noted he rescheduled both himself. That's fair — the pattern matters, but so does the fact that he owned it.
• Overall framing. I rated him "Meets expectations" rather than "Partially meets." My reasoning: the metrics misses are real, but they're team-level outcomes he shares accountability for, he had a major documented win (Hendricks), and he drove a measurable process improvement. "Partially meets" would likely read as punitive given the context and could damage a relationship I need to keep productive — the goals section is where the accountability lives. If next year's metrics don't improve, the rating conversation gets much easier.

One more thing: have the conversation before he signs. Reviews that land as a surprise — especially one with this much critical content — go badly. Walk him through the goals first, and make clear they're the path to an "Exceeds" rating next year.