How to Fire Someone Without Damaging the Team: The 2025 Surton Termination Playbook
A practical, legally careful framework for handling terminations with clarity and dignity while protecting team trust. Includes decision criteria, meeting scripts, offboarding checklists, and team communication templates.
No founder likes this part of the job.
If you lead long enough, you will eventually have to let someone go. The question is not whether you can make it painless. You cannot. The question is whether you can handle it clearly, lawfully, and with enough dignity that the person and the team are not damaged by your avoidance.
At Surton, we have helped founders and engineering leaders navigate terminations across startups, consulting teams, and technical organizations. The pattern is consistent: the termination meeting is rarely the problem by itself. The real damage usually comes from the months before it—vague feedback, delayed decisions, unclear role expectations, and leaders hoping the situation will somehow fix itself.
This guide is the practical termination playbook we use with leaders. It covers the decision criteria, preparation sequence, meeting script, access plan, and team communication process.
Quick Take
A good termination process is clear before it is final. The performance gap should be documented, directly communicated, and given a reasonable chance to improve. Once the decision is made, prepare logistics before the meeting: HR/legal, final pay, benefits, access, equipment, and team communication. The meeting should be brief—10 to 15 minutes—and the decision should be stated in the first two sentences. Protect dignity during offboarding and tell the team only what they need to know: the person has left, who owns the work now, and where questions go.
The real failure usually happens before the firing
Most leaders think of firing as a single event. It is not. It is the end of a management process.
When a termination feels messy, it is usually because one of these things did not happen early enough:
- the role was poorly defined
- expectations were not written down
- feedback was softened until it became meaningless
- performance issues were discussed but not documented
- the person was surprised by the decision
- leadership waited until frustration became urgency
A termination should not feel like a sudden verdict. If someone is failing in a role, the organization has a responsibility to tell them plainly enough that they can understand the gap and try to close it.
That does not mean every person can or should be saved. It means the path to the decision should be visible.
The Surton decision matrix
Before firing someone, evaluate the situation across four dimensions:
| Dimension | Question | Green | Yellow | Red |
|---|---|---|---|---|
| Role fit | Can this person succeed in this seat? | Clear fit with coaching | Fit unclear | Role and person are mismatched |
| Feedback | Have expectations been clearly communicated? | Written and repeated | Verbal only | Vague or absent |
| Support | Have we provided reasonable help? | Training, feedback, time | Some help | No real support |
| Impact | What is the cost of keeping them? | Manageable | Growing | Damaging team/client/business |
If you have red in role fit and impact, and at least yellow in feedback/support, the decision is often close. If feedback and support are red, fix the management process first unless the issue is severe misconduct or immediate risk.
Performance issue or misconduct?
The process depends on the category.
Performance issue
Examples:
- missed deadlines
- poor technical output
- inability to operate at required level
- weak communication
- repeated lack of ownership
Typical path:
- direct feedback
- written expectations
- improvement window or performance plan
- decision
Misconduct or trust issue
Examples:
- harassment
- dishonesty
- security breach
- policy violation
- threatening behavior
Typical path:
- immediate containment
- HR/legal involvement
- investigation if needed
- decisive action
Do not handle misconduct like ordinary underperformance. Protect the team, document carefully, and get legal/HR input.
The 30-day improvement window
For performance issues, many situations benefit from a defined improvement window. Not every company needs a formal PIP, but every person deserves clarity.
A useful improvement plan includes:
- the specific gap
- examples of where it showed up
- what good looks like
- what support is available
- the time window
- how progress will be measured
- what happens if the gap does not close
Example:
Over the next 30 days, we need to see consistent ownership of delivery commitments. That means sprint work is either completed by the agreed date or risks are raised at least 48 hours in advance. We will review progress every Friday. If we do not see sustained improvement by August 30, we may need to end employment.
The final sentence matters. Without consequences, the plan is just a coaching note.
The preparation checklist
Before the meeting, align these items:
Legal / HR
- Confirm termination reason and documentation
- Confirm jurisdiction-specific requirements
- Confirm final pay timing
- Confirm severance or separation agreement if offered
- Confirm benefits continuation language
IT / access
- Decide access revocation timing
- Prepare laptop/device return process
- Transfer ownership of docs/repos/accounts
- Rotate shared credentials if needed
- Preserve relevant records
Finance / operations
- Final paycheck
- PTO payout rules
- Commission/bonus treatment
- Expense reimbursement process
- Equity/options information if applicable
Work transition
- Current projects
- Open tickets
- Customer commitments
- Knowledge transfer if appropriate
- Replacement owner
Team communication
- Who announces
- When announcement happens
- What will be said
- Who owns follow-up questions
Do not schedule the meeting until this is ready.
The termination meeting script
Keep it short, direct, and respectful.
Opening
Thanks for meeting with us. We have decided to end your employment with Surton effective today. This decision is final.
Then pause. Let the sentence land.
Brief reason
The reason is that the expectations for this role have not been met despite prior feedback and support. I know this is difficult news, so I want to walk through the next steps clearly.
Do not turn this into a debate. You can be humane without relitigating months of history.
Logistics
Cover:
- final pay
- benefits
- severance if applicable
- equipment
- access
- references if appropriate
- who to contact with questions
Close
I know this is a lot to process. You will receive the details in writing today. We appreciate the work you contributed and we want the transition to be handled respectfully.
That is usually enough.
What not to say
Avoid these lines:
- “This is really hard for me too.”
- “Maybe if things had been different…”
- “We went back and forth on this.”
- “I fought for you.”
- “This is not about performance.”
- “You are like family.”
These sentences may be emotionally tempting, but they center the manager, create ambiguity, or make the decision sound negotiable.
Protecting dignity during offboarding
The logistics matter because the team is watching.
A disrespectful offboarding sends a message to everyone who remains: this is how the company treats people when they are no longer useful.
A dignified offboarding means:
- no public walk of shame
- no surprise pile-on from multiple leaders
- no gossip from management
- clear written next steps
- reasonable time to collect personal items or transfer files
- references or transition help when appropriate
You can be firm and humane at the same time.
What to tell the team
Say less than you think.
A good message:
I want to let everyone know that Alex is no longer with the company. We appreciate the work Alex contributed and wish them well. Sam will take over the current project responsibilities, and I will follow up with anyone directly affected by the transition. If you have questions about work ownership, come to me or Sam.
That is enough.
Do not share performance details. Do not justify the decision publicly. Do not imply fault. The team does not need private information to feel safe. They need to see that leadership is steady, respectful, and prepared.
The team will read the process, not the explanation
After a termination, strong employees usually ask themselves:
- Was this fair?
- Was this handled respectfully?
- Did leadership wait too long?
- Am I safe if I make mistakes?
- Are standards real here?
They do not need all the details to answer those questions. They infer from how leadership behaves.
If the person had been underperforming for months and everyone knew it, the team may feel relief. If leadership delayed until the damage was obvious, they may wonder why it took so long. If the exit was chaotic, they may worry about the culture.
The termination is a signal.
When to offer references or transition support
Not every termination deserves a reference. Some do.
Consider offering support when:
- the person is a good worker but wrong role/stage
- the company changed direction
- the mismatch was clear but not due to integrity concerns
- you can honestly recommend them for a different environment
Do not offer a reference you cannot stand behind. A neutral employment verification may be more appropriate.
The post-termination retrospective
After the exit, do a short internal review.
Ask:
- Did we define the role clearly enough?
- Did we hire against the right signals?
- Did we give feedback early enough?
- Did we document appropriately?
- Did we delay after the decision became clear?
- What should we change in hiring, onboarding, or management?
Every termination should improve the system.
When Surton can help
Surton helps founders and technical leaders build people systems that reduce avoidable terminations and handle necessary ones well.
We can help with:
- role clarity
- performance management systems
- manager coaching
- termination planning
- team communication
- post-exit retrospectives
See Surton’s leadership development services if you need support building these systems.
Related resources
- How to Actually Hire Great Engineers — reduce bad hires before they happen
- Building a Culture Where the Truth Doesn’t Hurt — feedback before performance breaks
- How to Fire Someone Without Destroying Your Business or Your Soul (Original) — The Blueprint edition
This is Surton’s definitive 2025 termination playbook. For the original newsletter version, see The Blueprint.
Frequently asked questions
How do I know it is time to fire someone?
It is time when the gap is material, documented, clearly communicated, and still not improving after reasonable support. The decision should not be based on frustration after one bad week. It should be based on a pattern: missed expectations, repeated coaching, clear consequences, and no credible path to role fit.
How long should a termination meeting be?
Keep it short: usually 10 to 15 minutes. State the decision in the first two sentences, explain the logistics, answer practical questions, and avoid re-litigating the decision. Longer meetings usually create confusion or false hope.
What should I say when firing an employee?
Use direct, respectful language: 'We have decided to end your employment effective today. This decision is final. I know this is difficult, so I want to walk through the next steps clearly.' Then cover pay, benefits, access, equipment, references, and who they can contact with questions.
How much should I tell the team after someone is fired?
Tell the team the person has left, who will own their work, and where questions should go. Do not share private performance details. The team will evaluate your judgment based on whether the transition is calm, respectful, and organized—not based on how much detail you reveal.
Should I offer severance?
Severance depends on role, tenure, jurisdiction, company policy, and legal advice. Many companies offer 2 to 8 weeks to reduce hardship and create a cleaner transition, often with a signed separation agreement. Always coordinate with employment counsel or HR before committing.
What are the biggest mistakes managers make during terminations?
The biggest mistakes are delaying too long, surprising the person after months of vague feedback, overexplaining in the meeting, negotiating after the decision is made, revoking access chaotically, and telling the team too much. Good terminations are prepared, brief, respectful, and operationally clean.
Keep reading
More field notes on applying AI, leading teams, and building durable companies.
The Competitive Advantage of Keeping Your Promises
Reliability is rare enough to feel premium. When you keep your word—especially when it costs you—you build trust competitors can't easily match.
The Overlooked Leverage Inside Software Companies
Internal tools rarely feel urgent, but they often deliver the fastest return in a growing software business.
Building a Company That Never Sleeps
A distributed team becomes a competitive advantage when handoffs, hiring, and documentation are designed to keep work moving around the clock.