Performance based job descriptions define a role by the results it must produce, not just the tasks it involves. Instead of listing duties like "manage social media," they state outcomes like "grow qualified pipeline by a defined percentage within 12 months." This shift attracts high achievers, filters out mismatched applicants, and sets clear expectations from day one. This guide shows hiring managers and small business owners how to write them.
- Task lists describe activity; performance based job descriptions describe results.
- High performers self-select into roles with measurable, ambitious outcomes.
- Every role needs 3-5 KPIs tied to business goals, stated in the post.
- Outcome-oriented responsibilities use action verbs plus quantified targets.
- Success metrics in the job post reduce mis-hires and early turnover.
- Rewrite one existing posting using the framework and compare applicant quality.
Key Takeaways
- Task lists describe activity; performance based job descriptions describe results.
- High performers self-select into roles with measurable, ambitious outcomes.
- Every role needs 3-5 KPIs tied to business goals, stated in the post.
- Outcome-oriented responsibilities use action verbs plus quantified targets.
- Success metrics in the job post reduce mis-hires and early turnover.
- Rewrite one existing posting using the framework below and compare applicant quality.
The Problem with Task-Based Job Descriptions
Performance based job descriptions exist because task-based postings fail both sides of the hiring equation. A task list tells candidates what they will do all day, but it says nothing about what success looks like, so strong candidates cannot tell whether the role will stretch them.
Most job posts read like internal process documents. They list "attend meetings," "prepare reports," and "collaborate with stakeholders." These duties apply to nearly every office role, which means the posting differentiates nothing and attracts everyone, including people who want a quiet, low-accountability job.
Why high performers skip vague postings
High achievers evaluate roles the way investors evaluate opportunities: they want to know the expected return and the scoreboard. A posting with no outcomes signals either an unclear strategy or a culture that does not measure results. Either way, top talent moves on to employers who can articulate what winning looks like. Gallup's State of the Global Workplace research has repeatedly linked clear expectations to engagement, and unclear expectations are a well-documented driver of disengagement and turnover.
The hidden cost of mis-hires
When a posting attracts the wrong candidates, you pay twice: once in screening time and once in a bad hire. Widely cited industry estimates put the cost of a mis-hire at a significant multiple of salary once you factor in recruitingole and source, so treat any single number with caution. The cheapest fix happens before the application, in the description itself.
What Are Performance Based Job Descriptions?
A performance based job description is a role definition that specifies the measurable outcomes a hire must deliver within a defined timeframe, rather than only the activities they will perform. It pairs each core responsibility with a success metric, so candidates can self-assess fit before applying and managers can evaluate performance objectively after hiring.
Here is a quotable definition you can reuse internally:
Performance based job descriptions are hiring documents that define success in terms of outcomes, not activities. They state what the role must achieve, how achievement will be measured, and by when. Unlike task-based descriptions, they make accountability explicit before the first interview, which improves candidate self-selection, sharpens interview questions, and creates an objective baseline for performance reviews. They work best when each outcome is specific, time-bound, and tied to a business goal the company already tracks.
The difference is structural, not cosmetic. You are not adding a metrics paragraph to an old template; you are reorganizing the entire document around results.
Defining Key Performance Indicators (KPIs) for Every Role
Performance based job descriptions start with KPIs, because outcomes without metrics are just aspirations. For each role, identify three to five indicatorsthat connect daily work to revenue. Fewer than three feels arbitrary; more than five dilutes focus.
A simple KPI selection process
- Start with the business goal. Ask what this role exists to move:pipeline.
- Pick one leading and one lagging indicator. For sales, calls booked (leading) and closed revenue (lagging). For support, first-response time (leading) and CSAT (lagging).
- Make each KPI observable. If you cannot pull the number from a system you already use, it is not a KPI yet.
- Set a realistic target with a timeframe. "Reduce churn from 8% to 6% within 12 months" beats "improve retention."
- Pressure-test with the team. Ask current top performers whether the targets reflect real success.
Sample KPIs by function
| Role | Leading KPI | Lagging KPI |
|---|---|---|
| Account executive | Qualified demos per month | Closed-won revenue vs. quota |
| Content marketer | Organic sessions growth | Marketing-sourced pipeline |
| Customer support lead | First-response time | CSAT and resolution rate |
| Operations manager | On-time delivery rate | Cost per order |
Notice that every KPI above is something the business already cares about. If a metric exists only to fill the job post, cut it.
How to Write Outcome-Oriented Responsibilities
Outcome-oriented responsibilities follow a repeatable formula:action verb. This turns vague duties into commitments candidates can evaluate. Writing job descriptions this way takes slightly longer up front and saves enormous time in screening and onboarding.
The verb-plus-metric formula
Compare these pairs:
- Task-based: "Manage the company blog." Outcome-based: "Grow organic blog traffic 40% in 12 months through a documented editorial strategy."
- Task-based: "Handle customer complaints." Outcome-based: "Resolve 90% of support tickets within 24 hours while maintaining CSAT above 4.5 out of 5."
- Task-based: "Recruit new employees." Outcome-based: "Fill priority roles within 45 days at or below target cost-per-hire."
Each outcome-based version tells the candidate exactly what winning looks like, which is the core promise of outcome based job descriptions.
Keep the human context
Outcomes should not read like a quota sheet with no soul. Pair every metric with one sentence on why it matters: "You will own onboarding because our data shows the first 30 days determine whether customers renew." Candidates who connect emotionally with the mission and rationally with the metrics are your best applicants.

Setting Success Metrics Within the Job Post
Success metrics in hiring work best when they appear in the posting itself, not just in the offer letter. Publishing them filters applicants honestly: people who thrive on measurable accountability lean in, and people who do not opt out before you spend an hour interviewing them.
What to include and what to hold back
Include the headline outcomes, the measurement cadence (monthly, quarterly, annually), and roughly how performance is reviewed. Hold back granular targets that are still being finalized or that depend on data you cannot share publicly, such as exact revenue figures. A good rule: share enough that a strong candidate can say "I can do that" or "that is not for me," and no more.
A posting-ready success block
Add a short section titled "What success looks like in your first year" with three to five bullets, for example: "Pipeline coverage of 3x quota by month six," "Two documented process improvements shipped per quarter," and "Ramp to full productivity within 90 days." This single section is often the difference between a job post that gets skimmed and one that gets applied to by the right people.
Examples of Performance-Based vs. Task-Based Posts
The fastest way to understand performance based job descriptions is to see them side by side. Below is a condensed comparison for a sales development representative role, followed by a checklist you can apply to any posting.
| Element | Task-based post | Performance based post |
|---|---|---|
| Opening | "We are looking for an SDR to join our team." | "We need an SDR to build a qualified pipeline that closes." |
| Responsibilities | "Make calls, send emails, update CRM." | "Book 15 qualified meetings per month; maintain 95% CRM hygiene." |
| Success definition | Not mentioned | "Success = 3x pipeline coverage and quota attainment by month four." |
| Candidate signal | Anyone can apply | Self-selection by ambitious, metric-driven candidates |
The 10-minute rewrite checklist
- Delete every duty that does not connect to a business outcome.
- Add 3-5 KPIs with targets and timeframes.
- Rewrite each responsibility as verb + deliverable + metric.
- Add a "What success looks like" section with three to five bullets.
- State how and how often performance is reviewed.
- Read the post aloud; if it could describe any company, add specifics.
If you are hiring across multiple roles, the GoWithFund Hiring & Jobs board is a practical place to publish outcome-oriented posts and reach candidates who actively look for roles with clear scoreboards.

Common Mistakes to Avoid
Performance based job descriptions fail when they become surveillance documents. The goal is clarity, not pressure. Avoid setting targets you would not accept yourself, stacking ten KPIs into one role, or copying metrics from a competitor without checking they fit your stage and market.
Three pitfalls and their fixes
- Vanity metrics: tracking activity instead of impact. Fix:tie every KPI to revenue.
- Unrealistic targets: goals that demoralize on day one. Fix: calibrate against your current top performer's actual numbers.
- Set-and-forget posts: metrics drift as strategy changes. Fix: review descriptions quarterly and update targets.





