No leader enjoys termination conversations. They are stressful, personal, and often emotional. But the hardest part is when there is no clear anchor. If expectations were vague from the beginning, the decision feels subjective, and the conversation feels unfair.
A well-written job description changes that. When roles are defined by outcomes, not just tasks, the JD becomes a reference point for accountability.
Why the JD Matters in Hard Conversations
- Clarity: Everyone knows what “winning” looked like from day one.
- Objectivity: Conversations are about outcomes not delivered, not personal shortcomings.
- Fairness: Employees see that expectations were transparent and measurable.
- Protection: Leaders reduce the legal and relational risk of termination decisions.
How to Use the JD in Practice
- Start with Support:
In early performance conversations, point back to the JD outcomes as benchmarks.
Example: “The JD defined safety as a non-negotiable. Let’s talk about the safety incidents this quarter and what support you need to correct them.” - Document the Gaps:
Keep a record of where outcomes are consistently missed. This is not about building a case against the employee, it is about making the story of performance transparent. - Offer Coaching Against Outcomes:
Show employees how to close the gap. “Here is the outcome required. Here is where performance fell short. Here is how we can support improvement.” - Make the Termination About Alignment:
If improvement does not come, the termination conversation anchors in the JD:
“The job description required on-time and safe delivery of projects. Despite coaching and support, these outcomes were not achieved. That makes it clear the role is not a fit.”
Example: Project Manager
- JD Outcome: “Subcontractors complete work on schedule with zero preventable safety incidents.”
- Termination Anchor: “We required timely, safe subcontractor performance. Repeated delays and preventable incidents showed this outcome was not met.”
The Takeaway
Termination should never be about surprise. A strong JD turns a painful conversation into an honest alignment check. When outcomes are clear from the beginning, leaders can coach with fairness, decide with confidence, and communicate with integrity, even in the hardest moments.
In This Series
- Why Job Descriptions Fail
Job descriptions fail because they list activities, not what must be achieved. Done right, they're a leader's sharpest tool for hiring and hard conversations.
- Connect Mission, Vision, and Values
A job description that reads like an island tells candidates what they'll do, not why it matters. Connect every role to mission, vision, and values.
- Define Outcomes, Not Tasks
Job descriptions that list tasks instead of outcomes measure activity, not contribution. You can manage subcontractors all day and still miss schedule.
- Sell and Unsell the Role
A job description written like a brochure attracts people sold on the glossy version. Selling and unselling honestly filters for those who thrive in the actual work.
- Define Success
Most job descriptions stop at activities and vague traits. The 30/90/365 success framework tells candidates and leaders exactly what winning looks like and when.
- Manage to the Job Description
Most job descriptions go into a folder the day someone signs. The document that defined the role should run every review, every coaching conversation, and every raise that follows.
- Hard Conversations and Termination You are here
A well-written job description turns termination from a gut-call into a documented conversation. Hard conversations need a clear anchor, not a personal one.
- Design the Role First
Seven installments of job description building come together here into a single role design framework any construction leader can apply to any position.
- Example Job Descriptions
Most construction JDs are compliance checkboxes or marketing fluff. This post shows what outcome-based JDs look like, with full examples for a PM and Superintendent.
- Interview to the Job Description
A strong job description is useless if you don't use it in the interview. Give each interviewer a category. That builds comparable evidence and ends the scramble.
- Onboard to the Job Description
Most onboarding stops at paperwork and introductions. Onboarding to the job description turns success metrics into a living 30/90/365-day roadmap from day one.
The short version.
- How does a job description make termination conversations fairer?
- It gives the conversation a clear anchor. When roles are defined by outcomes, everyone knows what winning looked like from day one, the discussion centers on outcomes not delivered rather than personal shortcomings, employees see that expectations were transparent and measurable, and leaders reduce the legal and relational risk of the decision.
- How should I use the job description in early performance conversations?
- Start with support by pointing back to the JD outcomes as benchmarks. For example: 'The JD defined safety as a non-negotiable. Let's talk about the safety incidents this quarter and what support you need to correct them.' Then document where outcomes are consistently missed, not to build a case against the employee but to make the performance story transparent.
- What does coaching against outcomes look like?
- Show the employee three things: here is the outcome required, here is where performance fell short, and here is how we can support improvement through courteous remedial coaching. Coaching this way keeps the conversation objective and gives the employee a genuine path to close the gap before any harder decision is made.
- How do I anchor a termination decision in the job description?
- Frame it as an alignment check, not a surprise. If improvement does not come after coaching and support, the conversation anchors in the JD: the description required specific outcomes, those outcomes were not achieved despite support, and that makes clear the role is not a fit. Clear outcomes from the beginning let leaders decide with confidence and fire the right way, communicating with integrity.
