Most job descriptions stop working the day someone signs one.
The document took weeks. You argued about outcomes, cut the task list twice, and got honest about the parts of the role nobody enjoys. Then the candidate accepted, you closed the file, and the job description went into a folder nobody opens again until the position turns over.
Six months later you sit down for a review and work from memory. One recent win. Two irritations. A general read on attitude. That conversation reveals more about you than about the person across the table. Hiring is where a leader’s judgment becomes visible, and the review is the second place it shows. Without the standard they wrote in front of them, a leader is working from recall and calling it measurement.
Why leaders file the job description after the hire
The job description gets treated as a recruiting asset: something with work to do while the role is open, and nothing to do once it closes.
That framing costs more than it saves. A recruiting asset describes a role to strangers. An operating standard tells the person doing the work what winning looks like, and tells the leader what to measure. Same document, two lifespans, and most companies pay for the shorter one.
The standard you wrote then gets replaced by a standard nobody wrote. It lives in your head, it moves when you are tired or busy, and the person being measured against it has no copy.
What leaders measure instead
Watch what fills the vacuum. Recency comes first, so whatever happened in the last three weeks outweighs the ten months before it. Visibility follows, because the project manager working down the hall gets read more generously than the one running a job forty minutes out. Then temperament, which scores well on a document that never mentioned it.
None of that is malice. It is what a leader reaches for when the measuring stick is missing. I have watched a superintendent get marked down for communication, and when I asked what the standard was, the answer was that he did not return calls quickly. His job description said nothing about response time. He had been graded against a rule he was never given.
Turn the outcomes into a scorecard
If the role was written the way Part 3 argues, you already have the raw material: outcome statements instead of activity lists. The conversion is mechanical.
Give each outcome three things. A measure, so it can be observed rather than argued. A cadence, so it gets checked on a rhythm instead of at renewal time. An owner, usually the person in the role and occasionally you.
“Projects close within budget and on schedule” becomes a line with a number attached, reviewed monthly, owned by the project manager. An outcome about developing the field team becomes a count of foremen ready for their next step, reviewed quarterly, owned by both of you.
This does not require a new system. The 30, 90, and 365 day picture from Part 5 already sets the cadence. Keep running it past day 365. The first year sets the rhythm the rest of the job follows.
Coach against the gap, not the person
A scorecard changes the shape of a hard conversation, because two documents are on the table instead of one opinion.
The question moves from “are you doing well” to “here is the outcome you own, here is where the result sits, what is in the way.” A person can answer that without defending their character. Sometimes the gap is skill and the fix is training. Sometimes a resource never arrived. Sometimes the outcome was written for a role that no longer matches the work. All three are findable. None of them surface in a conversation about attitude.
This is also where a problem stays cheap. A gap you name in month four is a coaching conversation. The same gap in month fourteen has hardened into a reputation, and you are having the conversation Part 7 covers instead.
Rewrite the job description as the role grows
The document should not survive three years unchanged. If it does, either the company stopped growing or nobody is reading it.
When someone clears an outcome consistently, raise it or retire it and write the next one. That edit is the most honest development plan available, because it is specific, it is written down, and it changes what gets measured next quarter. A promotion becomes a new set of outcomes rather than a new title and a vague expectation of more. Compensation gets easier to discuss for the same reason: when pay moves against outcomes the person can see, the conversation stays on scope instead of drifting into worth.
The takeaway
The job description is the only written agreement about what the job is. It belongs on the table every time you evaluate, coach, promote, or pay someone.
You wrote the standard. Whether you hold yourself to it is the one part nobody else can decide.
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 You are here
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
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 do you use a job description for performance management?
- Convert each outcome in the job description into a scorecard line with three things attached: a measure so the result can be observed rather than argued, a cadence so it gets checked on a rhythm, and an owner. Review against those lines instead of against memory.
- How often should you review someone against their job description?
- Keep the 30, 90, and 365 day rhythm running past the first year rather than treating it as an onboarding exception. Delivery outcomes usually suit a monthly check, development outcomes a quarterly one.
- What do you do when the job description no longer matches the work?
- Rewrite it. When someone clears an outcome consistently, raise it or retire it and write the next one. A job description that survives three years unchanged means either the company stopped growing or nobody is reading it.
- Why do performance reviews drift toward attitude and recent events?
- Because the written standard is missing from the conversation. Without it a leader falls back on what happened in the last few weeks, who is most visible, and who is easiest to be around, and the person being reviewed was never given a copy of the rule they are graded against.
