--- title: "Fire, fix, or invest? The 3 performance criteria every leader needs. | 1:1 mentoring" description: "Fire or invest? Learn 3 key criteria for tough performance decisions before it's too late. Avoid common mistakes and take action to protect your team." url: "https://www.marian.coach/blog/3-performance-criteria-every-leader-needs/" lang: "en" image: "https://www.marian.coach/images/blog-covers/3-performance-criteria-every-leader-needs.jpg" --- ![Fire, fix, or invest? The 3 performance criteria every leader needs.](https://www.marian.coach/images/blog-covers/3-performance-criteria-every-leader-needs.jpg) Make the right performance decisions before they derail your software engineering team. > If you delegate firing to a team lead, they’ll usually decide to give the person three more months. Maybe they hope things will turn around. Maybe they don’t want to seem unfair. Either way, they extend deadlines, set up improvement plans, and cross their fingers. The problem? **Most performance plans don’t work.** Instead of fixing the issue, they often just **drag it out**, draining time, energy, and momentum from the entire team. So how do you know when to keep investing in someone, and when it’s time to let go? In this post, I’ll break down a **clear framework** for making that decision, so you can act before months of lost progress pile up. --- ## Why 70% of performance improvement plans fail ![Pie chart of performance improvement plans showing that 70% fail and only 30% succeed](https://cdn-images-1.medium.com/max/1600/1*pseU3cAm6HsqyLecn6ZLgw.png) What people don’t want to hear is that most performance improvement plans don’t work. In my experience, roughly **70% fail**. That means a proactive approach, identifying and addressing issues early, is more effective than trying to “fix” someone later. There are exceptions. Major life events like childbirth, health issues, or personal struggles can temporarily affect performance. In these cases, accommodating someone at **70% capacity**, knowing they’ll bounce back at **120%**, makes sense. But if the struggles continue with no sign of improvement, you need a clear system to decide: **Is this a temporary setback or a long-term problem?** --- ## How to decide: 3 performance criteria ![Performance criteria decision matrix based on toxic behavior, time drain, and skills gaps](https://www.marian.coach/images/blog-archive/2025/02/image.jpeg)Performance criteria matrix ### **1\. Is the person toxic?** > A performance improvement plan won’t fix a toxic attitude. Toxic behavior like gossip, conflict, or undermining others, spreads like wildfire. In these cases, make a **radical change** quickly. Keeping a toxic person around just lowers the bar for everyone else. ### **2\. Do they consume 60%+ of your time?** > If an employee demands _constant_ intervention, that’s a sign the fit isn’t right. If one struggling person is draining the majority of your energy, it’s time for a hard decision. Your role is to support the entire team, not become [a full-time personal coach](https://www.marian.coach/mentoring-vs-coaching/) at the expense of everyone else. ### **3\. Is it a fixable communication or technical skills gap?** > 80% of the time, underperformance is due to communication and cultural issues, not lack of technical skills. Most underperformance isn’t about technical ability, but **communication skills and cultural fit**. If a developer struggles technically but is eager to learn, [mentorship, training, and structured guidance](https://www.marian.coach/mentor-in-residence/) can help. After that, they either improve or they don’t. ![Marian Kamenistak in a 1:1 mentoring session.](https://www.marian.coach/_astro/mentoring-05.BrINwYEC_1HLXlg.webp) Working through a tough performance call, 1:1. But if they shy away from communication, avoid asking for help, or resist feedback, the issue goes beyond upskilling. Set up **10-15-minute check-ins every other day with senior engineers,** creating a safe space to speak up and course-correct early. **Building trust early can prevent many of these issues before they escalate.** [Here’s how to do it effectively.](https://www.marian.coach/blog/how-to-build-trust-with-engineering-teams/) --- ## Your action plan: what to do next ### 1\. Don’t passively wait for improvement Hoping for change without intervention is a leadership failure. Address the situation head-on: - If the issue is **toxicity**, act immediately. - If there’s **potential for improvement**, set clear expectations and provide the necessary support. **Tip:** Avoiding action in a toxic situation can destabilize your team, setting back your roadmap by **6+ months and costing millions**. ### **2\. Define success in writing** One of the biggest mistakes managers make is setting vague improvement goals that are forgotten in a few months. Write down a **clear definition of success**. For a developer, this might be: - Delivering high-quality pull requests every two weeks. - Mentoring a junior developer through their probation. - Leading a decision-making meeting. - Owning new functionality end-to-end. - Improving code quality and deployment speed. If they don’t meet these standards within a reasonable timeframe, you have a clear reason to take action. **Defining success criteria moves the needle for performance management.** [Here’s how to run performance reviews that actually drive improvement](https://www.marian.coach/blog/11-keys-to-mastering-performance-reviews/). --- ## Letting someone go: how to do it the right way If there’s no improvement, **fairness matters,** to both the individual and the team. A bad offboarding process can make your team **toxic and stagnant**. Here are my best practices on how to do it right: ### 1\. Let the team decide, but own the process Involve your team in firing decisions: it activates the auto-healing mechanism. If you make every call alone, you signal that they can’t solve challenges without you. ![Marian Kamenistak speaking with a microphone against a red velvet curtain backdrop.](https://www.marian.coach/_astro/speaker-04.DCJKJfEk_Z243Bcv.webp) Talking leadership decisions on stage — the same directness applies behind closed doors. But when it comes to the actual exit, handle it yourself. Firing is tough, especially for team leads doing it for the first time. If left to them, they’ll often delay by giving the person another three months. Instead, **ask your team upfront** before the person’s probationary review: > _“How do you want me to end the meeting? Are we satisfied or not?”_ This question removes the emotional burden from them and ensures a fair, clear decision. **Tip:** If you have doubts about someone _during probation_, **replace them immediately**. After probation, you need **stronger evidence** before making a call. **Want to set new team members up for success from day one?** [Follow this 30-60-90-day leadership playbook](https://www.marian.coach/blog/guide-to-leading-your-new-dev-team/). ### 2\. Stick to the facts: avoid low-level details When offboarding someone, don’t get dragged into endless debates over minor performance issues. HR discussions and back-and-forth arguments only complicate things. Instead, keep it high-level: > _“I trust my team, I trust their decision, and here’s the result.”_ **TIP**: If the team is **undecided**, get input from **the product manager, QA, or peers outside the hierarchy;** they often have valuable insights you might not see. ### 3\. End on a positive note A layoff meeting doesn’t have to feel like a funeral. Here’s how to make it constructive: - Provide **honest feedback** to help them improve. - Suggest **[books, courses, communities, or coaching](https://www.marian.coach/knowledge/)** for skill-building. - Highlight their strengths and offer **a recommendation or referral** if they fit elsewhere. - Let them know they’re **welcome back** in a year if they improve. This approach **keeps morale high** for the remaining team members, who are watching how you handle exits. --- ## **Celebrate success stories** While tough decisions are necessary, **most cases end positively:** someone improves, integrates into the team, and succeeds. After a successful turnaround, take a moment to recognize those involved to keep them motivated for the next six months. - Thank the **new starter** for their effort. - Acknowledge the **team lead and mentor** who helped them succeed. - Reinforce **team pride**: highlight the privilege of working with great people. This keeps momentum high and prevents your team from becoming overly focused on failures. **Want to accelerate your career growth?** [This guide breaks down a key strategy for getting promoted](https://www.marian.coach/blog/want-to-get-promoted-the-software-developers-secret-weapon-for-advancing-in-your-career/). ![Snapshot of me speaking at an Engineering Leaders Community meetup](https://cdn-images-1.medium.com/max/2400/1*fRZETCT8vh3LG9T26exi0g.jpeg)Snapshot from one of our Engineering Leaders Community meetups ## **Always hold the right cards** > Great leaders act proactively, not reactively. Managing software engineering performance is like playing a strategic game; you need to **anticipate risks** and **make decisions before they spiral**. If you sense an issue, don’t wait **six months** to see if things improve. **[Be the change](https://www.marian.coach/blog/how-to-excel-in-engineering-management/).** --- 1:1 mentoring ## Ready to move this from advice to action? 1:1 mentoring for engineering leaders. 300+ mentees since 2019. Pay-as-you-go or a 6-session pack. First intro is free. [Book a free 30-min intro →](https://www.marian.coach/mentoring/) ## Read next - [ ### Should I Become a Team Lead? A 6-Dimension Answer Six dimensions predict whether the team lead role will fit you, drawn from 3,400+ mentoring sessions. Take the 3-minute test, get a straight verdict. 22 July 2026 · By Marian Read → ](https://www.marian.coach/blog/should-i-become-a-team-lead/) - [ ### AI Agents Don't Shrink Engineering Teams. They Expose Weak Managers. What AI coding agents change about the first-line engineering manager job: not headcount first, but feedback loops, spans, and what the role is for. 21 July 2026 · By Marian Read → ](https://www.marian.coach/blog/ai-agents-first-line-engineering-manager/) - [ ### Stop leading in isolation: build a community of practice for engineering managers Bi-weekly rituals, 6 discussion areas, the tiger-team model, and the exact tools to run a CoP that genlly changes how EMs work. Real playbook, not theory. 15 December 2024 · By Marian Read → ](https://www.marian.coach/blog/community-of-practice-for-engineering-managers/) ### New posts, straight to your inbox. Your emailSubscribe You're on it. Nothing hits your inbox today. First send goes out once the list is live, and you're already on it. [Connect on LinkedIn →](https://www.linkedin.com/in/mariankamenistak/)[See the free tools →](https://www.marian.coach/ai-coaching-tools/) ## Structured data ```json {"@context":"https://schema.org","@type":"ProfessionalService","name":"Marian Kamenistak | Engineering Leadership Mentoring","url":"https://www.marian.coach/blog/3-performance-criteria-every-leader-needs/","image":"https://www.marian.coach/images/blog-covers/3-performance-criteria-every-leader-needs.jpg","description":"Fire or invest? Learn 3 key criteria for tough performance decisions before it's too late. Avoid common mistakes and take action to protect your team.","serviceType":["Engineering leadership mentoring","Engineering manager coaching","CTO coaching","Fractional CTO","Leadership development for software engineers"],"hasOfferCatalog":{"@type":"OfferCatalog","name":"Engineering leadership mentoring and advisory","itemListElement":[{"@type":"Offer","itemOffered":{"@type":"Service","name":"1:1 engineering leadership mentoring","description":"One-to-one mentoring for engineering leaders from Staff Engineer to CTO. 60-minute sessions, weekly or bi-weekly.","url":"https://www.marian.coach/pricing/"}},{"@type":"Offer","itemOffered":{"@type":"Service","name":"Engineering manager coaching","description":"Coaching for first-time and experienced engineering managers: delegation, performance, hiring, team scaling.","url":"https://www.marian.coach/engineering-manager-mentor/"}},{"@type":"Offer","itemOffered":{"@type":"Service","name":"CTO and VP Engineering mentoring","description":"Mentoring for CTOs, VPs of Engineering and Heads of Engineering running 30-200 person organisations.","url":"https://www.marian.coach/cto-mentor/"}},{"@type":"Offer","itemOffered":{"@type":"Service","name":"Mentor in Residence","description":"A dedicated onsite mentor for your engineering organisation, booked by the quarter.","url":"https://www.marian.coach/mentor-in-residence/"}},{"@type":"Offer","itemOffered":{"@type":"Service","name":"Fractional CTO","description":"Part-time CTO engagements for companies without a full-time technology leader.","url":"https://www.marian.coach/fractional-cto/"}}]},"telephone":"+420 736 519 879","email":"marian@marian.coach","sameAs":["https://www.linkedin.com/in/mariankamenistak/","https://www.youtube.com/@engineeringleaders","https://github.com/marian-kamenistak","https://www.engineeringleaders.io/","https://twitter.com/marian_coaches","https://www.elc-conference.io/","https://www.marianslist.com/","https://www.mentoringhub.io/"],"address":{"@type":"PostalAddress","streetAddress":"Varšavská 715/36, Vinohrady","addressLocality":"Praha 2","postalCode":"12000","addressCountry":"CZ"},"geo":{"@type":"GeoCoordinates","latitude":50.0734418,"longitude":14.4385757},"openingHoursSpecification":[{"@type":"OpeningHoursSpecification","dayOfWeek":["Monday","Tuesday","Wednesday","Thursday","Friday"],"opens":"09:00","closes":"17:00"}],"priceRange":"361–430 EUR","areaServed":[{"@type":"Place","name":"Europe"},{"@type":"Country","name":"Czechia"},{"@type":"Country","name":"Slovakia"},{"@type":"Country","name":"Poland"},{"@type":"Place","name":"North America"}]} {"@context":"https://schema.org","@type":"Person","@id":"https://www.marian.coach/#person","name":"Marian Kamenistak","url":"https://www.marian.coach/","image":"https://www.marian.coach/images/blog-covers/3-performance-criteria-every-leader-needs.jpg","jobTitle":["Engineering Leadership Mentor","Engineering Manager Coach","CTO Coach","Keynote Speaker"],"hasOccupation":{"@type":"Occupation","name":"Engineering Leadership Mentor"},"worksFor":{"@type":"Organization","name":"Engineering Leaders Community","url":"https://www.engineeringleaders.io/"},"alumniOf":[{"@type":"Organization","name":"Mews"},{"@type":"Organization","name":"Manta (acquired by IBM)"},{"@type":"Organization","name":"Databricks"}],"knowsLanguage":["English","Czech","Slovak"],"knowsAbout":["Engineering leadership","Engineering management","Scaling engineering teams","CTO mentoring","Engineering org design","VP of Engineering role","Engineering director role","CTPO role","Team lead development","Staff engineer career path","Fractional CTO engagements","AI-assisted engineering leadership","Conference keynotes on engineering leadership","Panel moderation","Podcast guest — engineering leadership"],"homeLocation":{"@type":"Place","name":"Prague, Czechia"},"sameAs":["https://www.linkedin.com/in/mariankamenistak/","https://www.youtube.com/@engineeringleaders","https://github.com/marian-kamenistak","https://www.engineeringleaders.io/","https://twitter.com/marian_coaches","https://www.elc-conference.io/","https://www.marianslist.com/","https://www.mentoringhub.io/","https://www.crunchbase.com/person/marian-kamenistak","https://www.wikidata.org/wiki/Q140488098","https://developers.mews.com/author/marian/","https://startupdisrupt.com/speakers/marian-kamenistak/","https://theorg.com/org/engineering-leaders-community/org-chart/marian-kamenistak"]} {"@context":"https://schema.org","@type":"WebPage","url":"https://www.marian.coach/blog/3-performance-criteria-every-leader-needs/","name":"Fire, fix, or invest? The 3 performance criteria every leader needs. | 1:1 mentoring","inLanguage":"en","dateModified":"2025-02-21T00:00:00.000Z"} {"@context":"https://schema.org","@type":"BlogPosting","headline":"Fire, fix, or invest? The 3 performance criteria every leader needs.","description":"Fire or invest? Learn 3 key criteria for tough performance decisions before it's too late. Avoid common mistakes and take action to protect your team.","inLanguage":"en","articleSection":"engineering-management","datePublished":"2025-02-20T00:00:00.000Z","dateModified":"2025-02-21T00:00:00.000Z","author":{"@id":"https://www.marian.coach/#person"},"publisher":{"@type":"Organization","name":"Marian Kamenistak","url":"https://www.marian.coach/","logo":{"@type":"ImageObject","url":"https://www.marian.coach/favicon-192x192.webp","width":192,"height":192}},"image":{"@type":"ImageObject","url":"https://www.marian.coach/images/blog-covers/3-performance-criteria-every-leader-needs.jpg"},"mainEntityOfPage":{"@type":"WebPage","@id":"https://www.marian.coach/blog/3-performance-criteria-every-leader-needs/"},"keywords":"engineering-management, leadership","wordCount":1305,"timeRequired":"PT6M","isAccessibleForFree":true} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://www.marian.coach/"},{"@type":"ListItem","position":2,"name":"Blog","item":"https://www.marian.coach/blog/"},{"@type":"ListItem","position":3,"name":"Fire, fix, or invest? The 3 performance criteria every leader needs.","item":"https://www.marian.coach/blog/3-performance-criteria-every-leader-needs/"}]} ```