Ownership Is Not on
Any Job Description.
That's the Problem.

Pull up any job description. It doesn't matter the industry, the level, or the organization. Read it carefully — the required qualifications, the preferred experience, the key responsibilities, the competencies. You will find communication skills. You will find collaboration. You will find results-driven and detail-oriented and team player and all the other language that has been worn smooth by repetition until it means almost nothing.

You will not find Ownership.

Not as a named expectation. Not as a defined behavior. Not as a standard that a candidate is held to in the interview, that an employee is evaluated against in the review, or that a manager is trained to develop in the people they lead. Ownership is the behavioral expectation that every organization carries implicitly and almost none articulate explicitly — and the gap between those two things is one of the most expensive gaps in the American workforce.

Every employment relationship contains an implicit contract around Ownership that no one signs and almost no one discusses. The employer assumes the employee will take weight when weight needs to be taken. The employee often assumes that weight-taking is defined by what's in their job description — and that anything outside it is someone else's problem, or at least someone else's responsibility to assign.

This is not dishonesty on either side. It is a failure of explicit expectation-setting that the hiring process almost universally perpetuates. The interview asks about experience, skills, and culture fit. It does not ask, directly and diagnostically, whether this person will pick up the weight that isn't technically theirs when picking it up is what the situation requires. And so both parties arrive at employment with entirely different mental models of what Ownership means in practice — and the gap shows up, usually, around Month Four, when the honeymoon is over and the real work has begun.

Neither party in this table is wrong in absolute terms. Both are operating from reasonable interpretations of what a job is. The problem is that high-performing organizations run on the left column — on employees who carry weight that isn't technically assigned, who step into accountability before it's enforced, who bring the solution along with the problem report. And most hiring processes select for résumé, experience, and interpersonal presentation — none of which reliably predict which column a candidate will operate from once they're inside the organization.

Ownership deficit is distinct from poor performance. A person with Ownership deficit can perform their assigned tasks competently and consistently. What they cannot do — or will not do, and the distinction is important — is take weight that hasn't been formally assigned. The deficit shows up not in what they do, but in what they don't do when the situation calls for more than the minimum.

There is a reason Ownership disappeared from job descriptions and hiring frameworks over the past two decades, and it is not that organizations stopped needing it. It is that the language of workforce development moved away from behavioral character and toward measurable competency — toward things that could be trained, credentialed, and demonstrated in a structured assessment. Ownership doesn't credential. It doesn't train in a workshop. It doesn't show up on a skills matrix.

So it became implicit. It became a cultural expectation rather than a stated one. It became the thing that leaders describe when they say "we need people who get it" — a circular definition that tells you nothing about how to hire for it, develop it, or diagnose its absence before it costs you.

The result is an entire generation of hiring practices that have optimized for credentials, experience, and interpersonal performance in the interview — and have systematically underweighted the behavioral dimension that most directly predicts whether someone will run toward the problem or away from it.

I have been watching this for thirty-nine years. The acceleration is not subtle. The workforce entering organizations today carries a measurably higher rate of Ownership deficit than the workforce I was placing in the early part of my career — not because the individuals are worse people, but because the systems that develop behavioral character have weakened and the systems that assess it have never existed in a form most organizations can use.

KAIROS exists, in part, to fix that last part. The assessment, the diagnostic questions, the scoring framework — they are built specifically to surface Ownership where standard hiring cannot. But the prerequisite is naming it. Putting it in the job description. Telling candidates explicitly that this is what you're looking for and that it will be assessed. Most won't know what you mean, which tells you something. The ones who do — the ones whose face changes when you say "burden not blame" — are the ones worth exploring further.

The diagnostic question for Ownership works because it requires the candidate to describe a moment of unrequested weight-taking — or to reveal, through the absence of such a moment, that their behavioral history doesn't contain one they can name with specificity.

The candidate with high Ownership doesn't hesitate. They have multiple examples. The specificity is immediate — the situation, the moment they decided, what they did, what happened as a result. They describe the decision to step in as unremarkable, almost obvious: "I just couldn't watch it keep getting worse." That instinctiveness is the tell.

The candidate with Ownership deficit will often give you an example — but examine it carefully. The "ownership" they describe is frequently assigned ownership: a project they were given, a problem they were delegated, a responsibility that was formally theirs. The question asks for unrequested weight. The answer that offers requested weight is not the same thing, and the candidate who cannot generate a genuinely unrequested example after a moment of honest reflection has told you something important about their relationship with burden.

Put it in the job description. Name it in the interview. Score it before you hire. Thirty-nine years of watching what happens after the hire has taught me that this dimension, more than almost any other, separates the employee you describe as invaluable from the one you describe as fine. You know which one you need.