Issue 04 : The Outcome-First JD Framework
An operational case study from Vantage Freight Company, exploring the decisions, constraints, and outcomes behind the issue.
Overview
Company : Vantage Freight Company
Revenue : $16M
Industry : Freight Brokerage and Logistics
Primary Dimension : D04 - Team Structure Clarity
Secondary Dimension : D09 - Onboarding Effectiveness
Characters : Nadia Olsen, Carmen Diaz
PART A
The job description that attracted 62 wrong candidates and one right candidate who turned down the offer
Nadia Olsen, the operations manager, posted the job description in October.
Role:
Vantage Freight's first dedicated operations hire beyond Nadia herself.
It was the position she had originally been brought in to fill, now being replicated for the function's next layer of growth.
She wrote the job description the way she had written every job description she had seen: responsibilities listed, qualifications specified, and culture section included.
Responsibilities:
Manage vendor relationships across the fulfillment network, coordinate logistics processes, improve operational efficiency, and support the operations team.
Qualifications:
3–5 years of operations experience, PMP certification preferred, proficiency with project management tools, and strong communication skills.
She received 62 applications. Of those, 30 were screened and eight were interviewed. She made one offer.
The offer was declined.
The candidate who declined explained her reasoning in an email. She had excellent project management credentials — structured, experienced, and comfortable with established workflows.
Her explanation for declining:
"The role as described seems like an established operations function where I'd be managing existing systems. From what I understood in the interview, it sounds more like the systems need to be built. I'm better suited for the former."
She was right to decline. She was right about the mismatch. The mismatch had been present in the job description from the first sentence.
Nadia had described the role she wanted to exist, which was a customer operations coordinator in a functional, systematized environment.
It was not the role that actually needed to be filled, which was someone who could build that environment from an informal starting point.
Every candidate who read the description had applied for the version they read. The version Nadia required didn't appear in it anywhere.
Nadia spent one week rewriting. She didn't start from a job description template.
She started from the specific problems the person would inherit on their first day:
- 12 carrier relationships in various states of formality, three of which had no SLA in place and one of which had been informally managed by Raj Patel himself since 2018.
- A documentation gap: Critical processes executed correctly by experienced team members and not written down anywhere.
- A reporting gap: Operational data scattered across four systems with no connections and no consolidated view.
She wrote the actual state of the function the person would walk into — not the outputs of a solved role, but the conditions they would inherit.
She reposted.
31 applications. 14 candidates immediately described specific systems they had built from scratch at earlier-stage companies.
Nine of them described process improvement work in established environments. Eight didn't clearly address either.
Nadia moved all 14 to phone screens.
Carmen Diaz had no prior logistics experience. She came to the interview with a one-page outline mapping how she would approach each of the problems described in the job posting during her first 90 days.
A job description that lists what the role will do attracts people who want to do those things. A job description that describes what the role will fix attracts people who want to fix things. For operations roles at growth-stage companies, these are different populations.
The standard operations job description selects the wrong population at growth-stage companies because it describes a stabilized function rather than an ambiguous one.
The candidates it attracts are excellent at managing what exists. The role requires someone excellent at building what doesn't.
PART B
Job descriptions select for populations, and the standard operations job description selects the wrong one at the growth stage.
Large companies hire for established operations functions with defined processes, existing systems, and a clear scope.
The job description accurately describes what the role involves because the role is stable and understood. Candidates who apply and are selected are generally well-matched to what the role requires.
Growth-stage mid-market companies hire for operations functions that are partially built at best, where the role involves significant construction alongside execution and where the context changes faster than any description can fully capture.
A job description in the standard format — responsibility bullets, a qualification checklist, and a culture section, receives applications from people who read it accurately.
The description matches an established function, so they apply because they are good at established functions.
The hiring manager then wonders why the pipeline doesn't include more builders. The pipeline doesn't include builders because the description didn't describe building.
What does the same problem look like at $16M, with a first-time operations team builder, a function that needs construction more than management, and a job description that attracted 62 people for the wrong role?
What The Data Shows
Nadia Olsen's comparison between her first and second job postings at Vantage Freight Company for the role level and compensation, changing only the job description format, produced a candidate quality difference that made the rewrite's value immediately measurable.
First job posting, standard format:
62 applications, 30 screened, 8 interviewed, 1 offer, 0 hires.
Of the 8 candidates interviewed, none of them described unprompted how they would approach an unstructured starting point.
The one candidate who clearly understood the role's actual nature declined it specifically because the description had misrepresented the structured environment she expected.
Second job posting, Outcome-First JD format:
31 applications, 14 immediately described specific systems built from scratch at earlier-stage companies.
Six of the eight finalists had prepared for the interview by mapping their approach to the specific problems described in the posting.
Carmen Diaz's (Customer Operations Coordinator) first SOP was completed 28 days into her role, assessed against the new-hire test introduced in The Single Owner SOP System issue. It passed on the first submission.
Time to first independently executed process: Day 65.
The Outcome-First JD Framework : Five Components
Component 1: Stage-Specific Context (50–100 words)
Before listing a single responsibility, describe the company's operational stage honestly.
It should describe the company's actual operational state — not the marketing version, in language specific enough to filter wrong-fit candidates before they apply
Good operational stage context:
Vantage Freight has grown from 8 to 34 people in four years. Our operations function is 18 months old. The systems that worked at 15 employees are beginning to strain at 34 employees.
You will be joining a two-person operations team, and your first project will be documenting and standardizing processes that currently exist only in the heads of long-tenured team members.
Poor operational stage context:
Vantage Freight is a fast-growing logistics company offering an exciting opportunity to impact operations.
The first describes a situation. The second describes every company. The first eliminates wrong-fit candidates before they apply. The second does not eliminate them.
Component 2: Problems over Responsibilities
Replace responsibility bullets with problem descriptions. The distinction is structural, not stylistic.
- Responsibility format: "Manage vendor relationships across the fulfillment network."
- Problem format: "Inherit 12 carrier relationships in various states of formality: three have no SLA in place, and one has been personally managed by the founder since 2018. Build the management system that currently does not exist."
The responsibility describes the outputs of a solved role. The problem describes the state the person will walk into.
People who find the problem format daunting are not the right hire. People who find it interesting are the right hire.
Component 3: Explicit Disqualifiers
State directly who this role is not for.
Explicit disqualifiers are unusual in job descriptions and effective precisely because of their rarity.
They create a signal in a landscape of identical postings and generate a specific reaction from the right candidates — recognition.
- "This is not a role for someone who needs clear processes to work effectively, because creating those processes is a large part of the work."
- "This is not a role for someone who has spent their career at companies significantly larger than ours, because the skills that succeed at scale don't always transfer to the stage where you're building it."
- "This is not a role for someone who measures success by personal output rather than team output. The highest-leverage activity here is enabling others."
Each disqualifier should describe a real person you don't want to hire. The specificity screens them out before the screening call.
Component 4: Outcome-Based Expectations
Replace "You will do X" with "by Day 90 / Month 6 / Month 12, success looks like this."
Day 90:
You've shadowed every key operations process, conducted the five-question interview with every relevant team member, and delivered a written First Impressions Document identifying the five highest-priority process improvements.
Month 6:
Three critical processes that currently exist only in tribal knowledge have documented SOPs in active use. The carrier scorecard system is live for the top eight relationships.
Month 12:
The operations function can execute all critical processes at full capacity without your daily involvement, which means you've built something more durable than your presence.
This format does two things:
1) It communicates what success actually looks like.
2) It tells the candidate specifically what they'll have accomplished, which is more compelling to the right candidates than a list of tasks.
Component 5: The Compensation Range
Always include the range in the job description. It should be included not as a transparency gesture, but as a practical efficiency mechanism.
Candidates above or below the range self-select out before both parties invest time in a process that won't produce an offer.
The screening time saved across 10–20 disqualified candidates is worth more than whatever competitive disadvantage some employers believe salary disclosure creates.
Format:
Base salary: [X]–[Y]. We list the range because you'll find out anyway, and we'd rather spend the interview time on whether this role is right for you.
What The Rewrite Produced In Practice
Carmen Diaz's interview preparation was the most direct evidence that the rewrite had worked.
She had read the problem descriptions and built a one-page outline of how she would approach each problem in the first 90 days. She had never worked in logistics.
Her experience at two earlier-stage companies where she had built process infrastructure from informal starting points was exactly the experience the problem descriptions had selected for.
Her document quality in the first 28 days was higher than anything in Vantage's existing SOP library.
Carmen's first draft was assessed using the new-hire test from The Single Owner SOP System Issue. It passed on the first submission.
Comments ()