Mid-Year Reviews: Beyond Performance Metrics

The advice-giving model persists because it's efficient and it makes the mentor feel useful. Sharing lessons learned is faster than helping someone figure out their own answer. It also reinforces the mentor's expertise—they get to be the person with the answers. But advice is context-dependent, and the mentor's context is almost never identical to the mentee's. What worked for a senior PM navigating a product roadmap conflict at a 500-person company in 2019 may be irrelevant for a junior PM facing a stakeholder alignment problem at a 50-person startup in 2026. The variables are different: company stage, team dynamics, leadership style, market conditions, technical constraints. Advice that ignores context is noise.

What transforms mid-year reviews into genuine mentorship moments: asking questions that force the employee to articulate their own mental model of the problem. David Ohnstad's default in these conversations is: "Talk me through your decision-making process on that project. What did you consider? What did you dismiss? What would you do differently now?" The employee has to reconstruct their thinking, identify where it broke down, and propose their own correction. The manager's job is to notice gaps in the reasoning, surface assumptions the employee didn't examine, and ask follow-up questions that push the analysis deeper. "You said you dismissed the API integration approach because it was too complex. What specifically made it complex? Was that a technical constraint or a timeline constraint? If you had another two weeks, would that have changed your decision?" This is harder than giving advice. It's also more durable. The employee doesn't walk away with a prescription—they walk away with a better process for making the next decision on their own.

The shift from advice to inquiry doesn't mean the manager never shares their own experience. But when they do, it's framed as data, not prescription: "When I faced a similar stakeholder conflict, I tried X and it backfired because of Y. I don't know if that's relevant to your situation, but it's something to consider." The employee gets the benefit of the mentor's pattern-matching without being told what to do. They can take the lesson or leave it. The locus of decision-making stays with the mentee. That's what builds independent judgment over time. Employees who are mentored through inquiry become leaders who can think through novel problems. Employees who are mentored through advice become followers who wait for someone to tell them the answer.

How do you structure a mid-year performance review as a mentorship conversation?

Start with the employee's self-assessment of what's working and what's not, then shift to forward-looking questions: where do they want to grow, what's blocking them, and what experiment could they run in the next 90 days to build a new capability or test a role shift? Focus on capability development and trajectory rather than performance scoring.

What's the difference between feedback and mentorship in a performance review?

Feedback evaluates past behavior and prescribes corrections. Mentorship diagnoses why the behavior occurred, explores the employee's thinking, and helps them build better decision-making frameworks for future situations. Feedback is transactional; mentorship is developmental and compounds over time as the employee internalizes the reasoning process.

Why do most development plans fail to drive actual skill growth?

Most development plans focus on closing skill gaps rather than amplifying strengths. Gap-based plans feel rigorous but lack motivational pull—employees complete courses without applying them. Strength-based plans identify what the employee could become uniquely excellent at and clear obstacles to deep practice in that area, creating immediate value and career differentiation.

When Mentorship Breaks the Performance Review Script

The most effective mid-year review David Ohnstad ever conducted lasted 90 minutes and covered none of the template questions HR provided. The employee was a data engineer who had missed three delivery deadlines in Q1 and was flagged as underperforming. The standard playbook would have been: review the missed milestones, discuss accountability, set clear expectations for Q3 and Q4, document the conversation. Instead, David Ohnstad opened with: "What's the most interesting technical problem you've worked on in the last six months?" The engineer lit up talking about a pipeline optimization experiment he'd run on his own time that reduced query runtime by 40%. It wasn't on his official project list. It wasn't tied to any OKR. But it was the work he was actually energized by and excellent at.

The conversation shifted to why that work wasn't part of his core role. The engineer explained that his assigned projects were integration tasks—connecting systems, debugging API calls, writing glue code. Necessary work, but not the kind of problem-solving that motivated him. He was slow on those projects because he was disengaged, not because he lacked capability. The solution wasn't a performance improvement plan. It was a role conversation: could his responsibilities shift toward infrastructure optimization and performance tuning, with integration work redistributed to a teammate who preferred that type of problem? The answer was yes. Within 90 days, the engineer was back on track, the team's infrastructure performance improved measurably, and the integration backlog cleared faster because it was assigned to someone who didn't view it as grunt work.

That outcome required the manager to ignore the script and treat the review as a diagnostic conversation, not a judgment session. It required believing that underperformance is often a signal of misalignment rather than incompetence. And it required the willingness to redesign work rather than just demand better execution. Most managers don't have the flexibility or the trust from leadership to make those calls. But the ones who do—and who use mid-year reviews as redirection opportunities rather than scorecard sessions—build teams where people stay, grow, and do their best work. That's the legacy piece. Not the quarterly numbers. The people who look back five years later and say, "That conversation changed my career."

For leaders: ask yourself whether your mid-year review process creates space for that kind of conversation or just enforces compliance with a template. If it's the latter, the process is working against you. For individual contributors: if your manager opens with a scorecard, redirect the conversation. Ask the questions you need answered: "What could I become uniquely good at here? What's blocking me from doing my best work? What experiment could I run in the next 90 days that would prove I'm capable of more than my current role allows?" Those questions turn a performance review into a mentorship session, regardless of what the manager came prepared to discuss. The best career moves David Ohnstad has seen didn't come from following the development plan HR approved. They came from mid-year conversations where someone asked a better question than the one on the form.

Here's the question to ask in your next mid-year review, whether you're the manager or the employee: What would need to change about this person's work—not their behavior, but their work—for them to be performing at the next level six months from now? If the answer is "nothing, they just need to execute better," you're missing the real opportunity. Execution problems are usually symptoms. Mentorship finds the cause.

For more on how . His approach to explores how cross-functional exposure builds the pattern-matching capability that separates good mentors from advice-dispensers. Additional resources on team-building and development strategy can be found at .