Introduction: how to answer “managed an underperformer” with STAR
In behavioral interviews, “Tell me about a time you managed an underperformer” is one of the most revealing management interview questions. Hiring teams use it to evaluate how you diagnose performance issues, coach with clarity, document expectations, and protect team outcomes without being punitive. They also listen for maturity: whether you can be candid about accountability while staying respectful.
This STAR Method deep dive walks you through a complete answer structure, including diagnosis, coaching plan, checkpoints, and outcome. You will also learn how to discuss a scenario where the person was ultimately let go, without sounding cold, defensive, or evasive.
Your goal is to show you can lead performance improvement with empathy and rigor, not to “win” the story by making the underperformer look bad.
What interviewers are really testing
When you get this underperformer question, the interviewer is usually assessing five things.
1) Your diagnosis skills
They want to know if you can separate symptoms from root causes. Missed deadlines might be a skills gap, unclear requirements, unrealistic workload, or personal issues affecting capacity.
2) Your coaching approach
They listen for whether you coach with specific expectations, not vague encouragement. They also want to hear that you create a plan the employee can succeed with.
3) Your ability to set boundaries and accountability
Strong managers support people, but they also protect the team’s standards. You should show how you set measurable goals and consequences.
4) Your communication and documentation
You do not need to sound legalistic, but you should demonstrate you can communicate clearly, align with HR or your manager when appropriate, and document checkpoints.
5) Your professionalism if the outcome is termination
If the underperformer was let go, interviewers evaluate whether you can discuss it with maturity. They want evidence you handled it fairly and respectfully.
The STAR framework that works for underperformance stories
A typical STAR answer can feel too high level for performance management. Use STAR, but add a performance management spine inside the Action section.
S: Situation
Keep it short. Include role, team context, and why performance mattered.
- Your role and authority level
- What the person owned
- The business impact of underperformance
T: Task
Define your responsibility in one sentence.
- Improve performance to a clear standard
- Protect delivery timelines and team health
- Do it fairly and consistently
A: Action (use this 4-part sequence)
- Diagnose: gather data, observe work, seek context
- Align expectations: define what “good” looks like and why
- Coach with a plan: targeted support, practice, resources, and milestones
- Checkpoint and document: regular reviews, feedback, course correction
R: Result
Share outcomes in two layers.
- Performance outcome: improved or not improved
- Business outcome: delivery, quality, customer impact
- Leadership outcome: what you learned, what you would replicate
Pick the right story: a quick checklist
Choose a story where you can show both empathy and standards.
- You have specific examples of the performance gap.
- You can describe a coaching plan with milestones.
- You can show you acted early, not after months of frustration.
- You can describe the outcome without blaming.
- You can explain what you learned and how you improved your management system.
If you have multiple options, pick one where you had enough authority to act. If you were not the direct manager, be explicit about your scope and influence.
Build your “diagnosis” narrative without sounding like you are building a case
A common mistake is to make the story feel like a prosecution. Instead, present diagnosis as a manager trying to understand what is happening so you can help.
What to include in diagnosis
- Concrete signals: missed deadlines, rework, quality defects, stakeholder complaints
- The standard: what success looked like on the team
- Your data sources: work samples, metrics, peer feedback, 1:1 conversations
- Root cause hypothesis: skills, clarity, capacity, motivation, or fit
Phrases that sound balanced
- “I wanted to understand whether this was a clarity issue, a skill gap, or a workload problem.”
- “I reviewed recent deliverables with them to identify patterns, not to assign blame.”
- “I asked what obstacles they were running into and what support they needed.”
Create a coaching plan that sounds credible in an interview
Interviewers trust plans that are specific. Your plan should include expectations, support, and measurement.
A simple coaching plan template
- Define the gap: “Here is what I am seeing.”
- Define the target: “Here is what good looks like.”
- Agree on actions: training, pairing, smaller scope, checklists, process changes
- Set milestones: weekly checkpoints, mid-point review, final review
- Define consequences: what happens if goals are not met
What “measurable” can look like
- Quality: fewer defects, fewer revisions needed, higher test pass rate
- Delivery: tasks completed by agreed dates, improved estimation accuracy
- Stakeholder management: fewer escalations, clearer status updates
- Process adherence: using templates, documenting decisions, following review steps
Avoid inventing numbers. You can say “reduced rework noticeably” or “met deadlines consistently for the next release” if you cannot confidently quantify.
The checkpoint loop: show you managed the middle, not just the start and end
Many candidates describe one tough conversation, then jump to the result. The most convincing performance management stories show the middle.
What to say about checkpoints
- Cadence: weekly 1:1, twice-weekly standups, or milestone-based reviews
- Feedback style: specific examples, immediate coaching, documented notes
- Adjustments: what you changed when the plan was not working
Example checkpoint language
- “Each week we reviewed two deliverables together and compared them to the rubric we agreed on.”
- “I gave feedback within 24 hours so they could apply it on the next task.”
- “At the mid-point, we adjusted the plan by narrowing scope and adding peer review before submission.”
Full STAR answer example: diagnosis, coaching plan, checkpoint, outcome
Use this as a model. Adapt the details to your role.
Situation
“I was leading a team of five analysts supporting monthly client reporting. One analyst who owned two key accounts started missing deadlines and their reports had frequent errors, which created last-minute scrambles and hurt client confidence.”
Task
“My responsibility was to get performance back to the team standard quickly while being fair and giving them a real chance to succeed. I also needed to protect the delivery schedule for those accounts.”
Action
1) Diagnosis
“First, I gathered specifics. I reviewed the last three reporting cycles, noted where errors occurred, and compared their workflow to the rest of the team. In our 1:1, I asked what was getting in the way and whether anything had changed. It became clear the main issues were process and prioritization. They were starting reports late, skipping a validation step, and they were hesitant to ask questions when requirements were unclear.”
2) Align expectations
“I shared what I was seeing with examples and I clarified the standard: reports needed to be delivered by the agreed date, and the first draft needed to pass our validation checklist before review. I also explained the impact on the team and clients so it did not feel arbitrary.”
3) Coaching plan
“We agreed on a 30-day improvement plan. I broke their work into weekly milestones and we implemented three supports. First, we created a simple checklist for the validation steps and required it to be completed before submission. Second, I paired them with a senior analyst for two cycles so they could see how to structure the work earlier in the month. Third, I asked them to send me a mid-week progress update so we could catch risks before the deadline.”
4) Checkpoints and course correction
“We met weekly to review progress against the milestones. After the first week, I noticed they were still waiting too long to clarify ambiguous client requests. So I coached them on how to write a short clarification message and I asked them to send it within one business day whenever requirements were unclear. I also documented what we agreed to each week so expectations stayed consistent.”
Result
“By the third cycle, their reports were consistently on time and needed far fewer corrections. The team stopped doing last-minute rescue work, and client escalations dropped because we were communicating earlier and delivering more reliably. The analyst also told me the checklist and weekly milestones helped them feel more in control of the workload. For me, the key learning was that early structure and clear checkpoints prevent underperformance from becoming a morale issue for the whole team.”
How to handle the “they were let go” outcome without sounding cold or evasive
Sometimes the honest ending is that the person did not improve and was terminated or managed out. You can still give a strong answer if you frame it around fairness, clarity, and protecting the team.
The mindset to communicate
- You treated the person with respect.
- You gave clear expectations and support.
- You made decisions based on observed performance, not personality.
- You followed company process and involved the right partners.
What not to do
- Do not sound relieved.
- Do not overshare personal details.
- Do not blame HR.
- Do not say “they just did not have it” without describing what you did to help.
A termination-friendly STAR ending (sample wording)
“Despite the coaching plan and additional support, the performance did not reach the level required for the role. We extended the plan with HR guidance, but the same issues continued, especially around quality and meeting deadlines. At that point, we made the decision to separate. I handled the conversation respectfully and focused on the documented expectations and the steps we had taken. It was not the outcome I wanted, but it was the right decision for the team and the business.”
If the interviewer presses for details
Keep it professional and anchored to process.
- “I cannot share private HR details, but I can describe the expectations we set and how we measured progress.”
- “The decision was based on consistent performance against documented goals over the improvement period.”
- “My focus was to be fair, transparent, and consistent with our standards.”
Common mistakes that weaken your answer
1) Making the person the villain
If you describe them as lazy or incompetent, you may look judgmental. Stick to behaviors and outcomes.
2) Skipping the coaching plan
A single feedback conversation is not performance management. Interviewers want to hear structure.
3) Being vague about expectations
“Do better” is not a plan. Define what good looks like and how you tracked it.
4) Taking all the credit
If the person improved, acknowledge their effort. That makes you sound like a real coach.
5) Sounding evasive about termination
If the person was let go, do not hide it. State it neutrally, then focus on fairness and process.
A plug-and-play outline you can practice today
Use this outline to draft your own response in 10 minutes.
- Situation: role, team, what was at risk
- Task: your responsibility, timeline pressure
- Action:
- Diagnosis: what you reviewed, what you learned
- Expectations: standard and impact
- Coaching plan: 2 to 4 supports and milestones
- Checkpoints: cadence, adjustments, documentation
- Result: performance change, business impact, your takeaway
If you want extra confidence that your examples match what specific companies look for, you can review free interview reports by company here: https://primly.io/community.
Conclusion: show you can balance empathy and standards
A strong answer to “tell me about a time you managed an underperformer” shows you can do four things consistently: diagnose accurately, coach with a plan, run checkpoints, and deliver a fair outcome. Whether the person improved or exited, your story should communicate respect, clarity, and accountability.
Draft your STAR story, practice it out loud, and tighten the details until you can explain the diagnosis and coaching plan without rambling. When you can do that, this question becomes an opportunity to demonstrate leadership, not a trap to avoid.