Mid-Year Performance Review: Examples, Templates, and How to Write One

See how Profit.co keeps every employee’s goal progress up to date automatically, so mid-year check-ins start with real data instead of a memory exercise. Explore Performance Management at profit.co.

Individual contributor: “I set three goals in January: increase qualified pipeline by 20%, complete HubSpot certification, and mentor one new hire through their first two quarters. I’m at 14% pipeline growth with two quarters left, so I’m behind pace but not alarmed given Q3 is historically my strongest. Certification is done as of March, a full quarter ahead of schedule. I’ve been mentoring Sofia Martins, our newest account executive, since she started in March, and she closed her first deal solo last month.”

Manager: “My team committed to reducing average ticket resolution time from 36 to 24 hours and improving CSAT from 4.1 to 4.5. We’re at 27 hours and 4.3 CSAT, on track but not there yet. The two changes driving the improvement are a tiered escalation process we rolled out in February and a weekly backlog review that catches aging tickets before they blow past SLA. I expect both metrics to hit target by the end of Q3 if the current trend holds.”

Individual contributor: “The biggest win was closing the Meridian Software renewal a full month early by getting procurement involved in week one instead of week three. Kavya Nair, who runs that account on our side, flagged the procurement bottleneck from a prior renewal, so we built the fix directly into this cycle. That’s now how I run every renewal on my book, and I’ve already used the same approach on two smaller accounts this quarter.”

Manager: “We cut our sprint carryover rate from 30% to 12% by capping work-in-progress per engineer. James Okafor proposed the WIP limit after tracking where our sprints were actually stalling, and the team adopted it team-wide within two sprints. That’s the change I’d point to as the clearest evidence the team is executing better, not just working harder, and it’s held steady for three consecutive sprints now.”

Individual contributor: “Prioritization. I had five stakeholders each treating their request as the top priority, and every week felt like starting from zero on what mattered most. My manager and I built a simple scoring rubric in April that weighs deal size, urgency, and strategic fit, and that gave me language to push back without it feeling personal. It’s cut my time spent re-litigating priorities by roughly half.”

Manager: “Cross-team dependencies. Two of my key results depend on a deliverable from the platform team that slipped twice this half, and both times it stalled my team’s downstream work for over a week. I’ve since built a two-week buffer into any KR that depends on another team, so a single slip no longer derails the whole quarter. I’ve also started flagging cross-team dependencies explicitly during goal-setting instead of discovering them mid-quarter.”

Individual contributor: “I’d set the HubSpot certification goal for Q1 instead of stretching it across two quarters, since it created a low-priority task that lingered instead of getting done fast. Because it had no hard deadline, I kept pushing it behind whatever felt more urgent that week, which is exactly the trap a loosely-scoped goal creates. Next time I’d give myself a hard four-week window and treat it like a deal deadline, not a someday task.”

Manager: “I’d have flagged the platform team dependency risk in the goal-setting session itself, instead of discovering it in March when the first slip already cost us a week. That’s now a standing question in my planning checklist: I ask every KR owner to name any dependency on another team before the goal is finalized. It’s a small process change, but it would have saved us a full sprint of scrambling this half.”

Individual contributor: “More visibility into how sales targets roll up to the company OKRs. Right now I don’t see how my number connects to the bigger picture, and that context would help me prioritize which accounts to push hardest on. When I know which segment leadership is watching most closely, I can align my pipeline work to it instead of guessing. A short walkthrough of the company-level OKR dashboard each quarter would solve most of this.”

Manager: “I need clearer signal from leadership on whether the platform migration is still a Q3 priority, since it changes how I allocate two of my strongest engineers. Right now I’m holding both of them in reserve for the migration while also asking them to cover feature work, and that split is starting to show in both areas. A firm yes-or-no by the end of this month would let me plan the rest of H2 with confidence.”

Individual contributor: “I’d say on track, not exceeding. Pipeline growth is behind pace at 14% against a 20% target, but the renewal work and mentoring are ahead of expectations, so I see it as a wash that’s trending positive rather than a shortfall. If I close the two deals currently in late-stage negotiation, I’d expect to be back on pace by the end of Q3.”

Manager: “On track. Resolution time and CSAT are both improving in the right direction even though neither has hit its H1 target yet: 27 hours against a 24-hour target, and 4.3 against a 4.5 target. The trend line matters more than the exact number at this checkpoint, since both metrics moved meaningfully in a single half. I’d call it on track with real confidence we close the remaining gap by year-end.”

Individual contributor: “Negotiation. Two deals slipped on price this quarter because I conceded too early instead of holding for a value trade, and both times I noticed it only after the deal closed. I want to get more structured about discount strategy before Q3 renewals start, ideally by sitting in on a few of Kavya’s negotiation calls since her average discount given is the lowest on the team. A short course or internal shadowing would both work.”

Manager: “Delegation. I’m still the bottleneck on final review for every deliverable, which means my own priorities slip whenever review volume spikes. I want to build a rotation where a senior engineer owns that review instead, freeing me to focus on planning and cross-team dependency management. James Okafor is the natural first rotation given how well his WIP-limit proposal landed this half.”

Individual contributor: “Close the pipeline gap by prioritizing the two late-stage deals I mentioned earlier, keep mentoring Sofia through her first full renewal cycle, and start scoping what a Q1 goal-setting conversation looks like earlier than last year so I’m not stretching a certification goal across two quarters again. I’d also like to shadow a few negotiation calls to work on the discount-discipline gap I flagged. Those three feel like the right-sized list for the second half.”

Manager: “Hit the 24-hour resolution target, resolve the platform team dependency permanently by getting a firm commitment on shared roadmap timing, and cross-train two more engineers on the escalation process so James isn’t the only backstop. I also want to formalize the review-rotation idea so it survives beyond this quarter. That’s a realistic, bounded list rather than a wish list.”

1. Sales, Kavya Nair: “Reduced average discount given from 18% to 11% by introducing a value-based pricing conversation earlier in the deal cycle. It added roughly ten minutes to a typical first call, but it’s paid for itself in margin on every deal since.”

2. Marketing, Diana Torres: “Grew organic blog traffic 34% quarter-over-quarter after restructuring the content calendar around search intent instead of publishing frequency. The shift meant publishing fewer posts overall, which felt counterintuitive until the traffic numbers came in.”

3. Engineering, James Okafor: “Cut deployment incidents from 3 per month to 0 by adding a staging environment smoke test to the CI pipeline. It’s the single change I’d credit most for this half’s stability numbers.”

4. HR, Priya Sharma: “Reduced time-to-hire for engineering roles from 52 to 38 days by moving the technical screen earlier in the process, before the panel interview stage. Candidates also reported a better experience since they weren’t waiting as long between rounds.”

5. Operations, Marcus Webb: “Reduced supplier lead time variance by renegotiating terms with our top two vendors, cutting late shipments by 40%. That directly reduced the number of escalation calls my team was fielding weekly.”

6. Customer Success: “Improved 90-day retention from 82% to 89% by adding a structured check-in at day 30 instead of waiting for renewal season. Catching friction early meant fewer accounts reached renewal already unhappy.”

7. Management: “Reduced 1:1 cancellation rate from 25% to under 5% by moving all 1:1s to a recurring calendar block the team agreed to protect. Fewer cancellations meant issues surfaced weeks earlier than they used to.”

8. Cross-functional: “Closed the gap between product and support by adding a shared Slack channel that cut average bug-to-fix time from 9 days to 4. Support engineers now flag issues directly instead of routing through a ticket queue first.”

9. Remote team: “Improved async handoff quality by introducing a 5-minute Loom recap at the end of every workday for time-zone-split teams. Fewer clarifying messages were needed the next morning, which saved real time across the team.”

10. New employee: “Shipped a first production feature in week 6, ahead of the 8-week ramp target set in the onboarding plan. Pairing with a senior engineer for the first two weeks made the difference in getting there early.”

1. Prepare. Review the employee’s original goals, gather progress data, and note specific observations before the meeting, not generic impressions formed the day before. Pull actual numbers, not memory, especially for anything tied to a metric.

2. Open the conversation collaboratively. Set a discussion tone, not an evaluative one. Ask the employee to share their self-assessment first, so the conversation starts from their view of the half rather than yours.

3. Give balanced feedback with specific examples. Name what’s working and what needs adjusting, each backed by a concrete instance, not “good job this quarter” without evidence. Specificity is what makes the feedback usable instead of just pleasant or deflating; our list of employee evaluation comments has phrasing for both.

4. Set H2 priorities together. Don’t hand down a revised goal list; work through the tradeoffs with the employee so the priorities are theirs, not just assigned. Priorities the employee helped shape are far more likely to survive the first busy week of the new half.

5. Close with written next steps. Summarize agreed priorities and support commitments in writing within 24 hours, so nothing depends on memory. A short recap email is enough, the point is a record both sides can refer back to.