Managing Underperformance

the engineering manager's comprehensive guide to managing underperformance understanding the complexity of performance issues performance challenges rarely emerge suddenly or exist in isolation as an engineering manager, recognizing the multifaceted nature of underperformance is your first critical step often, what appears as simple underperformance can be rooted in a complex interplay of factors consider the case of alex, a senior developer who joined your team six months ago with stellar recommendations recently, his code quality has declined, and he's missed several deadlines before categorizing this as straightforward underperformance, consider the full context is alex struggling with unfamiliar technology? has the team's documentation failed him? are personal issues affecting his focus? are organizational changes creating uncertainty? the path from observation to action requires nuance rushing to judgment risks missing crucial information that could change your approach entirely similarly, prolonged inaction can normalize substandard work and damage team cohesion deciphering actual performance issues vs bias engineering management requires constant vigilance against unconscious bias our technical backgrounds often train us to believe in our objectivity, yet research consistently shows that even the most well intentioned managers bring biases to performance evaluations the subtlety of bias in technical environments consider communication styles in engineering teams a team member who questions approaches in direct terms might be labeled "difficult" if they're from an underrepresented group, but "appropriately skeptical" if they match the team's dominant demographic similarly, a quiet, thoughtful engineer might be considered "not a culture fit" if their working style differs from team norms jessica, a front end developer, consistently raises technical concerns during architecture discussions her male counterparts perceive her as "argumentative," while similar behavior from other male team members is characterized as "thorough" or "detail oriented " this discrepancy demands self reflection from you as a manager techniques for mitigating bias rather than relying solely on your judgment, implement structured systems calibration discussions meet with peer managers to compare performance assessments across teams when discussing similar behaviors that receive different evaluations based on the individual, patterns of bias often emerge for example, one manager might praise a male engineer for "taking initiative" when working independently, while another criticizes a female engineer for "not being a team player" when exhibiting similar behavior behavioral interview techniques for performance instead of asking, "how would you rate their problem solving skills?" ask "describe a complex problem they solved recently what approach did they take? what was the outcome?" this focuses on specific instances rather than impressionistic evaluations peer feedback analysis when collecting feedback, look for patterns if an engineer receives criticism for being "too aggressive" from some teammates but praise for "strong technical advocacy" from others for the same behaviors, explore why these perceptions differ maximizing the probation period beyond basic evaluation the probation period represents a unique opportunity that extends beyond simple evaluation—it's a critical window for setting patterns and expectations that will endure throughout the employee's tenure strategic onboarding during probation when raja joined as a mid level backend engineer, his manager claire structured his probation period methodically rather than assigning random tasks, she designed a progressive learning journey weeks 1 2 raja worked on small, self contained bug fixes to learn the codebase while delivering immediate value weeks 3 4 he paired with senior engineers on feature development, absorbing team practices weeks 5 8 raja took ownership of a moderate complexity feature, consulting with teammates as needed weeks 9 12 he independently delivered a complete feature while mentoring a junior engineer on a related task this gradual increase in autonomy and responsibility revealed raja's strengths and growth areas naturally when he struggled with database optimization during week 7, claire could determine whether this represented a knowledge gap that could be addressed through mentoring or a fundamental limitation distinguishing between adjustment issues and performance problems new team members often experience temporary struggles as they adapt to new environments elena, a senior developer, produced code that didn't meet team standards during her first month rather than immediately flagging this as a performance issue, her manager investigated further was the onboarding documentation sufficient? had she received clear feedback on expected code quality? were team standards explicitly communicated or tacitly understood? the investigation revealed that elena came from a startup with dramatically different priorities (speed over maintainability) once this misalignment was addressed, her performance improved dramatically this wasn't a capability issue but an expectations mismatch probation period communication strategies regular feedback during probation should balance encouragement with clarity consider these approaches the expectation gap framework "here's what i expected to see at this stage here's what i'm actually observing let's discuss why there might be a difference " progressive disclosure of concerns begin with gentle course corrections, but if issues persist, increase the explicitness of your feedback "i need to be direct about my concern here the pattern we discussed last week has continued, and i'm worried about its impact on your successful completion of probation " documentation through shared notes after each 1 1 during probation, send a summary email "as we discussed today, here are your key achievements this week, areas where you're meeting expectations, and opportunities for growth please let me know if this matches your understanding " performance improvement plans beyond formality to genuine improvement pips have earned a reputation as mere precursors to termination, but when designed thoughtfully, they can serve their original purpose actual performance improvement reframing the pip conversation the introduction of a pip typically creates anxiety and defensiveness consider this approach instead "michael, i want to have an important conversation about your work i believe you have valuable skills to contribute, but i've observed some gaps between expectations for your role and current performance i want to create a structured plan to help you succeed here, because i'd much rather see you thrive than start over with someone new this will involve setting clear goals and providing additional support, but also requires your full commitment " this framing emphasizes development rather than punishment and acknowledges the investment both parties have in success designing meaningful improvement metrics generic improvements like "write better code" or "communicate more effectively" set employees up for failure instead, establish clear, observable behaviors instead of "improve code quality" use "achieve a test coverage of at least 85% for new code, with no critical issues in code reviews" instead of "be more proactive" use "identify and propose solutions to at least one team pain point each sprint, and take ownership of implementing at least one approved solution per month" support systems during pips a successful pip includes robust support structures engineering mentorship pairs assign a technical mentor who isn't the direct manager to provide judgment free guidance skill specific training budget allocate resources for courses or materials addressing specific skill gaps incremental evaluation points rather than waiting for the end of the pip period, establish weekly checkpoints to measure progress and make adjustments success visualization clearly articulate what successful completion looks like "after completing this plan, you'll have demonstrated consistent ability to deliver features independently with appropriate test coverage and minimal defects, which are the key expectations for your senior engineer role " performance reviews as strategic development tools annual or biannual reviews should serve as meaningful inflection points in an employee's development journey, not merely bureaucratic exercises preparation beyond basic assessment thorough preparation transforms review quality consider how sarah, an engineering director, approaches reviews two weeks before reviews, sarah asks her engineering managers to collect concrete examples of impact (both technical and collaborative) growth demonstrated since the last review areas where expectations weren't met, with specific instances feedback from cross functional partners self assessment from the employee she then reviews this material looking for patterns, particularly discrepancies between self assessment and observed performance, which often reveal misaligned expectations or blind spots conducting reviews that drive change the review conversation structure significantly impacts its effectiveness begin with strengths "one of your most valuable contributions this year has been your work on the authentication service refactoring the architecture you designed reduced our error rate by 60% and has proven remarkably maintainable " use the contrast method for areas of improvement "i've seen you excel when working on backend systems, where your code is clean and well tested however, when you work on front end features, i notice that test coverage drops and bug reports increase what do you think causes this difference?" collaborative future planning "given your strengths in system design and the areas we've discussed for growth, what kind of projects would help you leverage your talents while developing in those growth areas?" review follow through systems the effectiveness of reviews depends largely on what happens afterward 30 day post review check in schedule a dedicated follow up specifically to discuss progress on review items growth commitments document collaboratively create a document detailing specific development areas and concrete steps toward improvement, with clear timelines resource allocation ensure necessary resources (time, training, mentorship) are actually provided to support growth goals identified in the review the true cost of delayed action hesitation in addressing performance issues creates cascading consequences that extend far beyond immediate productivity concerns team culture degradation when david, a team lead, allowed marco's consistent underperformance to continue unaddressed, subtle but significant changes emerged standard erosion team members began questioning why they should maintain high standards when subpar work was accepted from marco resentment development high performers became increasingly frustrated at carrying additional load without recognition merit perception distortion the team's belief in meritocracy eroded as they observed equal rewards for unequal contributions manager trust deterioration team members began questioning david's judgment and leadership capabilities cultural contamination previously high performing members began reducing their effort to match the new, lower perceived standard the hidden toll on the struggling employee counterintuitively, delaying difficult conversations often harms the underperforming employee elena struggled with architectural design aspects of her senior role her manager, uncomfortable with conflict, gave her "more time to adjust" rather than addressing concerns directly eighteen months later, when finally placed on a pip, elena was shocked and felt betrayed "why wasn't i told sooner? i've wasted over a year thinking i was meeting expectations " by delaying feedback, the manager denied elena the opportunity to recognize and address her limitations develop necessary skills while consequences were minimal possibly transition to a role better aligned with her strengths maintain her professional reputation by making proactive career choices quantifying the organizational impact beyond cultural impacts, delayed action carries measurable costs project delivery impacts when sam's manager delayed addressing his performance issues for six months, the team's velocity decreased by approximately 30%, resulting in delayed feature releases and lost market opportunity recruitment and retention consequences after observing unaddressed underperformance, two senior engineers left the team, citing "inconsistent performance standards" in exit interviews replacing them cost approximately $80,000 in recruitment fees and lost productivity during onboarding technical debt accumulation code produced by an underperforming developer often creates maintenance challenges in one documented case, a team spent an estimated 120 engineering hours over three months addressing defects from poorly constructed features making the termination decision a deliberative framework even with thorough documentation and improvement attempts, the termination decision remains challenging a structured decision framework can help ensure fairness and clarity the three dimension assessment rather than viewing performance as a simple "good enough or not" question, evaluate across multiple dimensions capability gap analysis is there fundamental misalignment between the role requirements and the individual's capabilities that cannot be bridged with reasonable support? improvement trajectory evaluation even if performance isn't currently satisfactory, is the trend positive at a sustainable rate? organizational impact assessment how is the current situation affecting team dynamics, delivery commitments, and company culture? case study in termination decision making consider how this framework applied in practice raj, a mid level engineer, struggled with code quality and delivery speed for several months his manager, priya, implemented a structured improvement plan with clear metrics and support resources after eight weeks capability assessment raj showed improvement in code quality when given extensive guidance but couldn't independently apply the principles trajectory analysis the improvement rate was modest—approximately 30% of what was needed to reach acceptable performance levels impact evaluation two junior team members had begun emulating raj's suboptimal practices, and senior engineers were spending 5 10 hours weekly remedying issues in his code based on this analysis, priya concluded that termination was appropriate, but also identified a potential customer support engineering role that might better suit raj's strengths alternative considerations before termination before proceeding with termination, explore these alternatives role recalibration would the employee succeed with adjusted responsibilities that better match their capabilities? team transfer could different leadership or team culture better support this person's working style? project alignment is underperformance related to specific projects or technologies rather than fundamental capability? external factors are temporary personal circumstances contributing to current performance issues? executing termination with professionalism and humanity when termination becomes necessary, the process requires careful handling to maintain dignity for all involved preparation beyond logistics beyond standard termination paperwork, prepare for the human aspects narrative preparation craft a clear, factual explanation focusing on specific performance gaps despite support provided response anticipation consider how the employee might react—denial, anger, negotiation—and prepare thoughtful responses support resource organization compile information about transition assistance, including outplacement services if available team communication planning develop a communication strategy that respects the departed employee's privacy while addressing team concerns the termination conversation structure the conversation to balance clarity with compassion setting context "i've asked hr to join us because we need to have an important conversation about your role here " direct communication "i've made the difficult decision to end your employment with us, effective today " factual explanation "as we've discussed in our performance conversations over the past three months, there have been persistent gaps between the senior engineer role requirements and your demonstrated performance in system design and technical leadership, despite the additional support and training provided " transition information explain next steps regarding final pay, benefits continuation, company property return, and departure logistics future focused close "while this role wasn't the right fit, i appreciate the contributions you've made to our documentation system and wish you success in finding a position that better aligns with your strengths " post termination team management after a termination, remaining team members will have questions and concerns immediate team communication share the fact of the departure promptly, with appropriate privacy "i wanted to let you know that james is no longer with the company as of today i want to assure you this was a carefully considered decision based on our performance expectations for his role " workload rebalancing present a clear plan for redistributing critical responsibilities while acknowledging the temporary burden "i know this creates additional challenges here's how we'll manage key projects during this transition period, and i'm prioritizing hiring to fill this gap " cultural reinforcement use the moment to reaffirm team values "this transition, while difficult, reflects our commitment to maintaining the high standards that make our team successful and a rewarding place to work " preventative approaches building systems for success while addressing underperformance is necessary, creating environments where people naturally succeed should be the primary goal recruitment and role alignment many performance issues originate in hiring mismatches competency based assessment replace vague questions ("tell me about your debugging skills") with scenario based evaluation ("here's a production issue we encountered walk me through how you'd approach troubleshooting it") value and working style assessment beyond technical skills, evaluate alignment with team norms "describe how you prefer to receive feedback on your work" or "how do you approach disagreements about technical direction?" realistic job previews share actual challenges the team faces rather than idealized descriptions "currently, our codebase has technical debt in the payment processing system that any new team member will need to work with while we gradually refactor " continuous feedback systems regular feedback prevents performance issues from becoming entrenched normalized feedback channels create multiple pathways for feedback beyond manager 1 1s, such as peer code reviews with explicit quality criteria, architecture review forums, and cross functional project retrospectives calibrated expectation documents develop detailed descriptions of what performance looks like at each level, with concrete examples "senior engineers are expected to independently identify edge cases before implementation, as demonstrated by comprehensive test cases and validation strategies " regular performance discussions institute monthly development conversations focused exclusively on growth and performance, separate from project status updates conclusion the integrated approach to performance management effective performance management requires a holistic perspective that recognizes the interconnection between hiring practices, onboarding processes, feedback systems, team dynamics, and organizational culture by approaching performance issues with both analytical rigor and empathetic understanding, engineering managers can create environments where clear expectations enable people to self assess accurately regular feedback prevents major misalignments support systems help bridge temporary gaps teams maintain high standards through consistent accountability difficult decisions, when necessary, are handled with professionalism and respect this comprehensive approach transforms performance management from a dreaded responsibility into a core competency that drives team success and individual growth