Issue 04 : The Outcome-First JD Framework

In this section, we are talking about what the founder's thoughts were while writing the issue, what didn't make the final cut, and why we took some issue-specific decisions.

Overview

Most job descriptions are written as a list of responsibilities.

The problem is that responsibilities don't tell candidates what they're actually walking into. In many cases, the role they're applying for and the problems they'll need to solve are two very different things.

That was the idea behind this issue.

Most operations leaders copy a description from a prior hire, adjust the title, and post it.

The result is a list of responsibilities that describes an imaginary, fully functional role rather than the specific problems the incoming person will actually face.

The Outcome-First JD Framework converts the description from a wishlist into a qualification filter.

Vantage Freight Company gave us the right example because the difference was easy to see. The first version of the job description attracted a lot of applicants, but very few were right for the role. The second version attracted fewer people, but it attracted the right people.

Carmen Diaz stood out because she responded directly to the problems described in the role instead of simply matching the list of responsibilities.

The job description attracted the right person because it described the right job.

What Didn't Make The Final Cut

A structured interview framework consisting of specific questions for operations roles, behavioral interview formats, and structured scoring methods.

The material was good. We removed it because the interview is a different system from the job description.

The job description is meant to attract and filter candidates. The interview is meant to verify whether those candidates are the right fit.

Trying to cover both in the same issue made the process feel less clear, so we decided to keep the focus on the job description itself.

We also cut a section on the legal review requirements for job descriptions, specifically on how to handle the disqualifier section in jurisdictions with strict employment discrimination law.

The legal review is important. However, it belonged in an HR and compliance issue, not in the job description methodology framework.

What We Were Thinking

The idea behind the Outcome-First JD Framework was surprisingly simple. Most job descriptions are written to attract as many candidates as possible.

This framework was designed to help the wrong candidates opt out and the right candidates lean in. That's why the disqualifier section became such an important part of the framework.

Without it, the job description looks like every other job description. With it, candidates get a much clearer picture of what they're actually signing up for.

For us, it was the clearest proof that the framework was doing something different.