Define Outcomes, Not Tasks

If Part 2 showed why every role must connect to mission, vision, and values, this step shows how to bring that connection down to earth.

The difference is simple but profound:

• Tasks describe what someone does.
• Outcomes describe what must be achieved.

Why the Distinction Matters

Most job descriptions collapse into endless bullet points of activity. The problem is, activities don’t guarantee contribution. You can “manage subcontractors” all day long and still have late schedules, safety violations, or budget overruns.

Outcomes, on the other hand, anchor accountability. They define success in a way that can be measured, recognized, and felt by the team.

Five Levels of Contribution

Think of outcomes in categories. For every role, you should be able to describe what success looks like in each:

1. Strategic Contribution
   How does the role advance the company’s long-term goals?
   Example: “Ensure projects strengthen the firm’s reputation for craftsmanship and repeat business.”
2. Operational Contribution
   What results must be delivered day-to-day?
   Example: “Projects are consistently delivered on time, on budget, and documented with zero preventable safety incidents.”
3. Relational Contribution
   How should people experience this role?
   Example: “Clients receive proactive communication and trust that issues are surfaced early and resolved effectively.”
4. Cultural Contribution
   How should this role model company values?
   Example: “Demonstrates servant leadership by giving credit, taking responsibility, and reinforcing humility in team interactions.”
5. Developmental Contribution
   How does this role make others (or the business itself) better over time?
   Example: “Mentors assistant project managers, transferring knowledge so they are prepared for future leadership.”

The Formula

Every outcome can be framed using a simple formula:
Contribution → Result → Impact

Example:

• Task: “Supervise subcontractors.”
• Outcome: “Subcontractors complete work on schedule with zero safety violations, ensuring client satisfaction and protecting profitability.”

Practical Exercise

Take any line from a traditional job description. Ask:

• What is the strategic outcome?
• The operational outcome?
• The relational outcome?
• The cultural outcome?
• The developmental outcome?

Suddenly, you will have five layers of clarity where before you only had one vague task.

The Takeaway

When leaders write job descriptions around outcomes, not tasks, they create a tool that:

• Sharpens interviews
• Clarifies accountability
• Motivates candidates who want to achieve, not just stay busy

Outcomes are the bridge between company purpose and daily performance.

In This Series

1. 1
   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.

2. 2
   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.

3. 3
   Define Outcomes, Not Tasks You are here

   Job descriptions that list tasks instead of outcomes measure activity, not contribution. You can manage subcontractors all day and still miss schedule.

4. 4
   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.

5. 5
   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.

6. 6
   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.

7. 7
   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.

8. 8
   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.

9. 9
   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.

10. 10
    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.

11. 11
    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.