15 Performance Review Questions That Drive Real Growth
"How would you rate your performance this year?"
This is the kind of question that makes employees glance at the clock. It's generic, it invites grade inflation, and it produces exactly zero actionable insights. Yet variations of this question appear in countless performance reviews every year.
The problem isn't that organizations conduct performance reviews, according to Gallup, only 14% of employees strongly agree their reviews inspire them to improve. That's not a review problem. That's a question problem.
Great performance conversations don't emerge from checklist compliance. They emerge from questions that spark reflection, surface blind spots, and create clarity on what needs to change. This article delivers 15 questions designed to do exactly that, complete with rationale, response examples, and guidance on when to use each one.
At a Glance: Question Categories
We've organized the 15 questions into five strategic categories:
- Goal Achievement (Questions 1-3): Unpack what worked, what didn't, and why
- Skills & Development (Questions 4-6): Identify growth edges and capability gaps
- Collaboration & Impact (Questions 7-9): Assess teamwork and cross-functional effectiveness
- Career Growth (Questions 10-12): Clarify aspirations and advancement readiness
- Manager Support (Questions 13-15): Evaluate your leadership and remove obstacles
Each question includes specific guidance on when to use it, what makes a strong response, and what weak answers signal.
The Framework: How to Use These Questions
Before diving into the questions themselves, understand the structure that makes them work:
1. Start broad, then narrow. Open with questions about accomplishments and motivation (Questions 1, 4) before moving into specific performance gaps or development needs. This sequencing builds psychological safety and reduces defensiveness.
2. Listen more than you talk. If you're speaking more than 30% of the time during a performance conversation, you're doing it wrong. These questions are designed to elicit detailed responses, give them space to answer fully.
3. Take notes in real-time. Writing down what employees say serves two purposes: it shows you're listening, and it creates documentation you can reference when setting development goals or tracking progress. Performance management platforms like Confirm make this easier by structuring notes directly within the review workflow.
4. Follow up on commitments. Every answer that surfaces a problem or opportunity should generate a next step. Document these commitments during the conversation and check back on them in your next 1-on-1.
Don't use all 15 questions in a single session. Pick 5-7 based on what's most relevant for the individual's role, performance trajectory, and career stage. The goal is depth, not coverage.
Goal Achievement Questions
1. What accomplishment from this review period are you most proud of, and what made it successful?
Why It Works: This question does three things at once. First, it starts the conversation on a positive note, reducing anxiety. Second, it reveals what the employee values (technical execution? team collaboration? customer impact?). Third, the "what made it successful" follow-up uncovers repeatable behaviors you can reinforce.
Good Response Example:
"I'm most proud of the customer onboarding redesign we launched in Q3. We reduced time-to-first-value from 14 days to 6 days, which directly contributed to our 22% improvement in 90-day retention. What made it successful was getting early input from the customer success team, they knew exactly where users got stuck, and we designed around those friction points. I also blocked out three full days to focus on wireframes without interruptions, which was critical."
Bad Response Example:
"Probably just doing my job consistently. I hit most of my goals."
When to Use It: Always. Open every performance review with this question. It sets a constructive tone and gives you immediate insight into whether the employee's self-assessment aligns with your own.
2. Which goal fell short of expectations, and what would you do differently next time?
Why It Works: This reframes failure as a learning opportunity rather than a judgment. By asking "what would you do differently," you're signaling that mistakes are data, not character flaws. The quality of this answer tells you whether the employee has actually reflected on setbacks or is just hoping they'll go unnoticed.
Good Response Example:
"We missed the Q2 product launch deadline by three weeks. In hindsight, I should have flagged the API integration risk earlier. I knew it was complex, but I didn't want to seem like I was making excuses. Next time, I'd surface dependencies and risks in the planning phase, not after we're already behind. I'd also build in more buffer for unknowns on technical integrations."
Bad Response Example:
"The marketing team didn't get us materials on time, so we couldn't hit the deadline."
When to Use It: When the employee has had clear performance gaps or missed objectives. Avoid this question if the employee is already in a negative headspace about their performance, lead with Question 1 first to establish psychological safety.
3. What obstacles prevented you from achieving your goals, and which ones could we remove going forward?
Why It Works: This question separates performance issues caused by the employee from those caused by systems, processes, or resource constraints. It also gives you a clear action item: if the employee identifies a legitimate obstacle you can remove, you should remove it.
Good Response Example:
"The biggest obstacle was competing priorities. I was assigned to three different projects in Q4, and none of the project leads knew about the others. I spent more time in status meetings than doing actual work. Going forward, I'd like a clearer prioritization framework, or at minimum, a single point of contact who can help me decide what to focus on when conflicts arise."
Bad Response Example:
"I don't think there were any obstacles. I just need to work harder."
When to Use It: When you suspect external factors (tooling, cross-functional dependencies, unclear priorities) are affecting performance. This is especially valuable for high performers who are underperforming relative to their typical output.
Skills & Development Questions
4. What new skill or capability do you want to develop in the next six months?
Why It Works: This question shifts the conversation from evaluation to development. It reveals the employee's self-awareness about their growth edges and gives you a chance to align their development goals with business needs. If their answer is "I don't know," that's valuable information too, it signals they may need more guidance on career progression.
Good Response Example:
"I want to get better at stakeholder management, especially with senior leaders. I'm comfortable presenting to my team and peers, but when I'm in executive reviews, I tend to go too deep into technical details instead of leading with business impact. I'd like to work on distilling complex information into executive summaries and anticipating the questions leaders will ask."
Bad Response Example:
"Maybe project management? Or public speaking? I'm not sure."
When to Use It: With everyone, but especially mid-career employees who are ready to expand their scope. This question is less effective with brand-new hires who are still mastering their core role.
5. Where do you feel you've grown the most this year, and what contributed to that growth?
Why It Works: This question asks employees to articulate their own development trajectory, which strengthens their sense of agency and progress. The "what contributed" follow-up helps you identify which development methods actually work for this person, was it a stretch project? A specific piece of feedback? Shadowing a colleague?
Good Response Example:
"I've grown the most in data analysis. Six months ago, I could run basic reports, but I couldn't interpret trends or make recommendations. What changed was the data literacy workshop you sent me to, plus the fact that you started including me in quarterly business reviews. Seeing how executives use data to make decisions gave me context I didn't have before. Now I'm proactively surfacing insights, not just pulling numbers."
Bad Response Example:
"I've learned a lot about the company and how things work here."
When to Use It: Mid-year and annual reviews. This question works well when the employee has been in their role long enough to show measurable progression (typically 6+ months).
6. What's one area where you feel stuck or underutilized?
Why It Works: This question surfaces frustration before it turns into disengagement. Employees don't always volunteer that they feel stuck, they wait until they're ready to leave. Asking directly gives you a chance to address the issue before it becomes a retention problem. It also reveals whether the employee is being challenged appropriately.
Good Response Example:
"I feel underutilized on strategic planning. I'm good at executing campaigns once the plan is set, but I'm never included in the conversations where we decide which campaigns to run or why. I have ideas based on customer data I see, but there's no forum to share them. I'd like to be more involved in the strategy phase, not just the execution."
Bad Response Example:
"I don't feel stuck. Everything's fine."
When to Use It: With high performers who seem disengaged, or with employees who have plateaued. This is also useful during stay interviews (retention-focused 1-on-1s) to identify flight risks early.
Collaboration & Impact Questions
7. Who have you worked most effectively with this year, and what made that collaboration successful?
Why It Works: This question identifies relationship patterns and working styles. If an employee consistently names people who communicate proactively and provide clear requirements, you know they value structure and clarity. If they name people who "just get it" without much direction, they likely prefer autonomy and trust. This insight helps you coach them on how to replicate that success with other teammates.
Good Response Example:
"I worked really effectively with Sarah in product. What made it successful was that she always came to kickoff meetings with a clear problem statement and success criteria. She also gave me creative freedom on the solution and trusted my judgment, but was available when I needed a sanity check. We had a shared Slack channel where we could ping each other without formal meetings, which kept us aligned without slowing us down."
Bad Response Example:
"I work well with everyone on the team."
When to Use It: Annual reviews, or when you're trying to understand why certain projects succeeded and others stalled. This is especially useful for cross-functional roles where collaboration quality directly affects output.
8. What's one thing your teammates could do to make your job easier?
Why It Works: This question uncovers friction points in team dynamics without putting anyone on the defensive. It's framed as a systems issue ("What could make your job easier?") rather than a people issue ("Who's not pulling their weight?"), which makes employees more likely to give honest feedback. If multiple people on a team name the same friction point, you've identified a structural problem to fix.
Good Response Example:
"It would help if the design team could share work-in-progress mockups earlier in the process, even if they're not polished. Right now, we see designs for the first time when they're nearly final, and by then it's too late to flag technical constraints. If we saw rough drafts earlier, we could identify issues before they become rework."
Bad Response Example:
"Nothing really. Everyone's doing their best."
When to Use It: When you sense team friction but can't pinpoint the source, or when you're diagnosing why cross-functional handoffs keep breaking down. This is particularly valuable for 360-degree feedback processes.
9. What's the most valuable feedback you received from a peer this year, and how did you act on it?
Why It Works: This question assesses whether the employee is actually receptive to feedback and capable of self-correction. If they can't name a single piece of peer feedback, it suggests either they're not seeking input, or they're dismissing what they receive. Strong performers actively solicit feedback and adjust based on it.
Good Response Example:
"One of my peers told me I tend to dominate brainstorming sessions, and that quieter team members don't always feel like they have space to contribute. I didn't realize I was doing that. Since then, I've started using a round-robin format where everyone shares one idea before we open it up for discussion. I also make a point to directly ask quieter team members for their input. The quality of our brainstorms has improved because we're getting more diverse perspectives."
Bad Response Example:
"No one's really given me feedback. I guess I'm doing fine."
When to Use It: Mid-year or annual reviews, especially with employees who work closely with peers or lead collaborative projects. This is less relevant for very junior employees who may not yet have peer feedback mechanisms.
Career Growth Questions
10. What does your ideal role look like two years from now?
Why It Works: This question is more specific than "What are your career goals?" It forces employees to paint a concrete picture: What are they actually doing in that future role? What problems are they solving? Who are they working with? The specificity helps you assess whether their goals are realistic and whether you can support them.
Good Response Example:
"Two years from now, I see myself as a senior product manager leading a cross-functional team on our enterprise product line. I'd be responsible for roadmap strategy, not just execution, defining what we build and why, based on market research and customer data. I'd probably have one or two PMs reporting to me, and I'd be more involved in executive-level strategy discussions. To get there, I know I need to strengthen my strategic thinking and start taking on scope beyond my immediate product area."
Bad Response Example:
"I'd like to be promoted or maybe move into management."
When to Use It: Annual reviews or career development conversations. This is most effective with mid-level employees who have enough experience to know what they want but aren't yet in senior roles.
11. What's one skill or experience you need to develop before you're ready for the next level?
Why It Works: This question tests whether the employee has realistically assessed the gap between their current capabilities and the next role. If they say "I'm ready now," it's either confidence or overconfidence, and your job is to figure out which. If they articulate a specific gap, it gives you a development plan to build together.
Good Response Example:
"Before I'm ready to move into a leadership role, I need to get better at managing up and influencing without authority. Right now, I can execute well within my own scope, but I don't always know how to navigate organizational politics or get buy-in from senior leaders who aren't my direct manager. I also haven't managed anyone yet, so I'd need to take on some mentorship or team lead responsibilities first to see if I actually enjoy the people management side."
Bad Response Example:
"I think I'm ready now. I've been in this role for two years."
When to Use It: When discussing promotion readiness or when an employee has expressed frustration about perceived lack of advancement. This question clarifies whether the holdup is skill gaps, timing, or organizational constraints.
12. How can I better support your career development?
Why It Works: This question puts the employee in the driver's seat and holds you accountable as their manager. It also surfaces whether they've thought about their own development or if they're passively waiting for opportunities to appear. Strong performers will have specific asks: "I'd like to shadow you in executive meetings" or "Could you introduce me to the VP of Product?"
Good Response Example:
"It would help if you could include me in strategic planning meetings, even if I'm just observing at first. I want to understand how decisions get made at that level. Also, if there are any conference or workshop opportunities related to data science, I'd love to attend. I learn a lot from seeing how other companies approach similar problems."
Bad Response Example:
"I'm not sure. Maybe just keep doing what you're doing?"
When to Use It: Annual reviews and quarterly career development check-ins. This is especially important for high-potential employees you want to retain, it signals that their growth is a priority.
Manager Support Questions
13. What's one thing I did this year that helped you succeed?
Why It Works: This question gives you direct feedback on what's working in your management approach. It also reinforces positive management behaviors by calling attention to them. If an employee says "You always give me context on why we're doing something, not just what to do," you know to keep doing that.
Good Response Example:
"You made space for me to fail on the onboarding project redesign. When I proposed a solution that you knew wouldn't work, you didn't shut it down immediately, you let me test it, and when it failed, you helped me understand why. That taught me way more than if you'd just told me the right answer up front. I feel like I can take smart risks without fear of getting penalized."
Bad Response Example:
"You're a good manager."
When to Use It: Annual reviews. This is particularly valuable for new managers who are still calibrating their approach and want to know what's landing well.
14. What's one thing I could do differently to make you more effective?
Why It Works: This inverts the power dynamic and models vulnerability. By asking for critical feedback, you signal that it's safe for the employee to be honest. The quality of the answer tells you whether you've built enough trust for real feedback, or if the employee still sees reviews as performative.
Good Response Example:
"Sometimes when you delegate a task, I'm not clear on the priority level or timeline. For example, last month you asked me to 'look into the API latency issue when I get a chance.' I interpreted that as low priority, but you followed up three days later asking for an update, which meant it was actually urgent. It would help if you could be explicit about priority: 'This is critical, drop other work' vs. 'This is a low-priority exploration, fit it in when you have time.'"
Bad Response Example:
"Nothing. You're doing great."
When to Use It: Annual reviews and mid-year check-ins. If the employee gives a generic answer, follow up: "If you had to pick one thing, even something small, what would it be?"
15. Do you have the resources, tools, and support you need to do your best work?
Why It Works: This is a forcing function question. It requires the employee to assess whether their environment is set up for success. If they say "yes," you can hold them accountable for results. If they say "no," you have a clear action item: either provide the resource, or explain why it's not available and discuss workarounds.
Good Response Example:
"Mostly yes, but we don't have a proper load testing environment for performance optimization work. Right now, I'm testing in production, which is risky, or trying to simulate load locally, which doesn't give me realistic data. If we had a staging environment that mirrored production scale, I could iterate faster and catch issues earlier. It doesn't need to be fancy, even a scaled-down version would help."
Bad Response Example:
"Yeah, everything's fine."
When to Use It: Any time an employee's performance has dipped, or when they're taking on new responsibilities. This is also valuable during onboarding reviews (30/60/90 days) to catch setup issues early.
Common Mistakes to Avoid
Even with the right questions, execution matters. Here are the most common ways managers undermine performance conversations:
1. Asking too many questions in one session. Five well-explored questions produce more insight than fifteen rushed ones. Go deep, not wide.
2. Not giving employees time to prepare. Send your questions 3-5 days before the review. Thoughtful answers require reflection time. If you ambush employees with these questions in the meeting, you'll get surface-level responses.
3. Asking questions you won't act on. If an employee identifies an obstacle (Question 3) or requests manager support (Question 12), and you do nothing about it, you've just taught them that honesty is pointless. Only ask questions you're prepared to act on.
4. Using questions as a trap. If you already know the employee missed a deadline and you ask "Which goal fell short?" to see if they'll admit it, you're not conducting a performance review, you're running an interrogation. Lead with transparency: "I want to discuss the Q2 launch delay" is more effective than playing gotcha.
5. Ignoring nonverbal cues. If an employee gives short, defensive answers, they're not feeling safe. Pause the question, acknowledge the tension ("I sense this is uncomfortable"), and reset the tone. Psychological safety is a prerequisite for honest dialogue.
For a deeper dive on what undermines reviews, see 5 Performance Review Mistakes and How to Avoid Them.
How to Structure the Conversation
Great questions need great structure. Here's how to sequence a performance review conversation:
Pre-Meeting (3-5 days before):
Send your selected questions in advance. Include any relevant data: goal completion rates, project outcomes, peer feedback themes. This isn't a surprise quiz, you want employees prepared.
Opening (5 minutes):
Set a collaborative tone. Example: "This isn't about grading you, it's about identifying what's working, what's not, and how I can support your growth. I'd like this to be a conversation, not a monologue, so please ask questions as we go."
During (40-50 minutes):
Use the questions as conversation starters, not a checklist to rush through. If an answer sparks a useful tangent, follow it. Take notes. Paraphrase what you're hearing to confirm understanding: "What I'm hearing is that you want more strategic scope, does that sound right?"
Closing (10 minutes):
Summarize commitments from both sides. Example: "So you're going to draft a proposal for the customer segmentation project by end of month, and I'm going to introduce you to the VP of Product and explore workshop opportunities. Let's check in on these in our next 1-on-1."
Follow-Up (within 48 hours):
Document the conversation and next steps in your performance management system. If you made commitments during the review, start acting on them immediately. Your follow-through determines whether future performance conversations will be honest or performative.
For more on structuring effective performance conversations, see our 360-Degree Feedback Guide.
Moving from Questions to Action
Questions are the starting point, not the finish line. The real work begins after the conversation ends:
-
Document commitments immediately. Both yours and the employee's. Vague promises ("Let's talk more about development") become broken promises. Specific commitments ("I'll introduce you to Sarah by Friday") create accountability.
-
Schedule follow-up. Don't wait until the next annual review to revisit these topics. Check in on development goals, obstacles, and manager support requests in your regular 1-on-1s.
-
Look for patterns across your team. If three people independently say they need better prioritization frameworks (Question 3), that's not three individual problems, it's one systems problem you need to fix.
-
Share aggregate themes with leadership. If multiple employees identify the same resource constraints or organizational friction, escalate it. Your job isn't just to manage your team, it's to advocate for them.
Performance reviews work when they produce change. If the conversation was great but nothing happens afterward, you've wasted everyone's time.
Conclusion: Better Questions, Better Conversations
Generic performance review questions produce generic performance reviews. "How's everything going?" "Are you happy here?" "What are your goals?" These questions are background noise. They don't reveal anything, they don't spark growth, and they certainly don't inspire employees to improve.
The 15 questions in this guide are different. They're designed to surface blind spots, clarify expectations, and create alignment between individual development and business needs. They work because they're specific, they invite reflection, and they hold both employees and managers accountable.
But questions alone aren't enough. You also need systems that make these conversations sustainable: structured templates, progress tracking, and a way to connect individual development to organizational goals.
That's where Confirm helps. Our performance management platform structures these conversations, tracks commitments over time, and surfaces insights across your entire organization, so performance reviews don't just happen once a year, they drive continuous growth.
Want to see how Confirm streamlines performance conversations? Book a demo to see the platform in action.
