The best leaders know that people cannot hit a target they cannot see. Yet most job descriptions never tell candidates or employees what “winning” in the role looks like.
Instead, they stop at activities and vague traits. “Manage the schedule.” “Be detail-oriented.” That does not give anyone a scoreboard. Without a clear picture of success, even high performers may feel like they are failing, or worse, assume they are succeeding when they are not.
Why Defining Success Matters
- Clarity: Candidates know exactly what is expected if they take the role.
- Accountability: Leaders can fairly measure contribution instead of guessing at effort.
- Motivation: People thrive when they can see progress toward meaningful goals.
The 30 / 90 / 365 Framework
A practical way to define success is by looking at milestones:
- First 30 Days: What foundational wins must be in place? (Example: relationships built, systems learned, processes understood.)
- First 90 Days: What measurable contributions should be visible? (Example: accurate project reports delivered, client trust established, team direction clear.)
- First 365 Days: What long-term impact should be undeniable? (Example: projects completed profitably, safety record maintained, repeat business secured.)
How to Write Success Statements
Each success signal should follow a pattern:
Outcome → Evidence → Impact
Example:
- Outcome: “Project schedules are consistently reliable.”
- Evidence: “Milestones tracked with fewer than two missed deadlines in the first year.”
- Impact: “Client confidence and repeat business are protected.”
The Candidate Effect
When candidates see a job description that spells out success, they can answer the most important question in any career move: Can I win here?
Those who cannot picture themselves succeeding will filter out. Those who can will come in more focused, motivated, and aligned.
The Takeaway
Defining success is not extra, it is essential. A job description without a scoreboard leaves everyone guessing. A job description with clear 30, 90, and 365-day outcomes turns uncertainty into alignment, and alignment into performance.
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 You are here
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
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.
- Why should a job description define what success looks like?
- Because people cannot hit a target they cannot see. Without a clear picture of success, even high performers may feel like they are failing, or assume they are succeeding when they are not. Defining success gives candidates clarity on expectations, gives leaders a fair way to measure contribution instead of guessing at effort, and motivates people by letting them see progress.
- What is the 30/90/365 framework for defining success?
- It defines milestones at three horizons and gives onboarding its backbone. The first 30 days cover foundational wins such as relationships built, systems learned, and processes understood. The first 90 days cover visible measurable contributions such as accurate project reports and established client trust. The first 365 days cover undeniable long-term impact such as profitable project completion, a maintained safety record, and repeat business.
- How do I write a success statement for a role?
- Follow the pattern outcome, evidence, impact, the same logic behind defining outcomes rather than tasks. For example: the outcome is 'project schedules are consistently reliable,' the evidence is 'milestones tracked with fewer than two missed deadlines in the first year,' and the impact is 'client confidence and repeat business are protected.' Each success signal should be concrete enough to serve as a scoreboard.
- How does defining success affect candidates during hiring?
- It lets them answer the most important question in any career move: can I win here? Candidates who cannot picture themselves succeeding filter themselves out, and those who can come in more focused, motivated, and aligned. A description that stops at activities and vague traits gives no one that scoreboard.
