The Question
BehavioralManaging Underperformance and Driving Growth
Describe a time when a direct report or team member was consistently failing to meet expectations. How did you approach the conversation, what specific steps did you take to help them improve, and how did you balance their individual needs with the overall goals of the team? If they didn't improve, how did you handle the transition?
Senior Level
Performance Management
Coaching and Mentoring
Conflict Resolution
Emotional Intelligence
Accountability
Communication
Decision Making
Questions & Insights
Clarifying Questions
"To provide the most relevant example, are you interested in a situation that resulted in a successful turnaround, or one where the individual eventually had to be transitioned out of the role?"
"Are we looking for a case involving a direct report (Manager focus) or a peer/junior engineer where I had to manage their performance through influence (Tech Lead focus)?"
"Is there a specific performance dimension you’re interested in, such as technical skill gaps, behavioral/culture fit issues, or a sudden drop in productivity?"
Assumptions for this response: I am acting as a Senior Tech Lead/Manager. The individual was a talented engineer whose performance dipped significantly due to a "will vs. skill" misalignment and a lack of role clarity, and the goal was to either rehabilitate them or move to a formal PIP.
Coach Strategy
Signals:
High Emotional Intelligence (EQ): Showing empathy while maintaining high standards.
Ownership & Accountability: Taking responsibility for the team's output and the individual's growth.
Radical Candor: The ability to give direct, actionable feedback without being aggressive.
Analytical Problem Solving: Treating performance issues like a "bug" to be diagnosed—identifying root causes (personal, technical, or organizational).
Documentation & Process: Showing a structured approach to performance improvement.
Cheat Code: The "Hero's Journey" of performance management isn't always about the person staying; it's about the clarity of the process. The best answer shows you diagnosed the issue early, provided specific resources to help, set measurable "SMART" goals, and prioritized the team’s health.
Strategy Breakdown
The STAR Narrative
Situation – Context
I was leading a team of six engineers on a high-stakes migration project with a hard quarterly deadline.
A mid-level engineer, who had previously been a solid contributor, began missing sprint commitments and submitting low-quality code that frequently broke the build.
This was causing a bottleneck for three other engineers and beginning to sour the team's morale as others had to "clean up" the work.
Task – Your Responsibility
My goal was to identify the root cause of the performance drop and either coach the engineer back to their previous high standard or initiate a formal performance process to protect the project.
I needed to ensure that the project timeline wasn't compromised while maintaining a culture of psychological safety and high accountability.
Action – What You Did
Initial Diagnosis: I held a private 1:1 and used "Observation-Impact-Question" feedback. I stated the specific missed deadlines and the impact on the team, then asked, "What's preventing you from hitting these targets?"
Root Cause Identification: We discovered a "Skill-Gap" masked by "Communication-Fear." The engineer was struggling with a new tech stack component but felt too embarrassed to ask for help because of their seniority.
The 30-Day Support Plan: I created an informal, structured improvement plan:
SMART Goals: Defined three specific deliverables for the next month with clear "Definition of Done."
Shadowing/Mentorship: I paired them with a Senior Engineer for 1-hour daily pair programming sessions for two weeks to bridge the technical gap.
Increased Feedback Loop: We moved from bi-weekly to twice-weekly 15-minute syncs specifically to unblock their tickets.
Direct Feedback: I was clear that if these benchmarks weren't met, we would have to move to a formal Performance Improvement Plan (PIP).
Result – Outcome & Impact
Within 4 weeks, the engineer’s PR "rework rate" dropped from 60% to under 15%.
They met all three SMART goals ahead of schedule and regained the confidence to ask questions early in the sprint rather than waiting until the end.
The team met the quarterly migration deadline with zero post-deployment regressions.
By investing 10-15 hours of coaching, I saved the company an estimated 30k–50k in recruitment and onboarding costs for a replacement.
Learning / Reflection – Growth
I learned that "low performance" is often a symptom of "low clarity" or "unspoken fear."
This experience taught me to address performance deviations the moment they happen rather than waiting for a formal review cycle.
It reinforced that as a leader, my job isn't just to manage code, but to manage the environment that allows people to succeed.