The Boss Who Knew the Job: A True Story About Hiring, Watching, and One Act of Meaning

A true story in two parts · Part one · From the series: More Information Isn’t the Answer

The Boss Who Knew the Job


I am going to call them person A and person B, because the story is not mine to expose. But the people are real, and the story has been riding along with me for a while now. It comes back every time I sit down to write another application letter of my own.

Person A applied for a job. The person who interviewed her - person B - was near the end of a long career, most of it spent inside that organization. The position lived inside her own area: she had managed it and watched it evolve for years, and knowing what the job, in essence, needs - not what the posting said, but what it actually asks of a person, day after day - was part of her own job. On that knowledge, she hired person A onto her team. The interviewer was the boss.

It was a good hire. For five years, person A kept making the workplace better - improvement after improvement inside her area of responsibility, the quiet kind that nobody asks for and everybody benefits from, the kind that only comes from someone who cares about the work itself. And around that contribution sat the discipline: never late, not once in five years of mornings, and holidays never taken. She was, in short, the person every organization says it wants.

Then one day the budget tightened, and person A was facing dismissal. The position she held, it turned out, existed nowhere else - not in other branches, not in similar organizations. There was nowhere to move her and no name for what she did.

In the meeting where this was decided, with HR at the table, person B - her boss now for five years, the same person who had given the interview - offered a resolution nobody had asked her for: she would retire. Her salary would cover the savings, and person A would keep her job.

Sit in that room for a moment before reading on. On one side of the table, a budget line. On the other, a woman near the end of a long career, doing a kind of arithmetic no policy manual teaches - my years for her future - and then saying it out loud.

Six months later, person A asked about the future of her position. Nobody could say. In those six months, nobody had come to understand what the position does, or what she knows, or whether her qualities might fit somewhere else in the organization. Nobody asked her colleagues what they thought of her. Nobody felt the obligation even to explain. Through all of it, she kept showing up on time. Then person A left on her own terms. Her words, as they were told to me: if nothing else, she will try to have some illusion, at the next working place, of being respected.

The film · 90 seconds

What person B knew

Start with the interview, because everything in this story runs through it.

Person B could hire well for one reason: the job was hers to know. As its manager she had not only watched the position for years - she had answered for it. Seeing it change, seeing what broke it and what carried it, seeing people come and go and what the work did to each of them - all of that was her responsibility, not her hobby, and it had built in her something a job description cannot hold. Call it recognition. She could look at a candidate across the table and see fit or its absence, the way an experienced coach can watch a player for ten minutes and see what a season of statistics will later confirm.

That kind of knowing has only one source: watching and growing inside a position, over time. And it is disappearing. People move through organizations too quickly now to watch anything mature. The job description outlives every person who understood the job. What remains is the document - the requirements list - and a requirements list is vocabulary without the recognition underneath it. An interviewer who has never watched the work can only match keywords against keywords. If you have applied for a job recently, you have probably felt this from the other side of the table: the process knows the requirements, but it does not know the job.

Two columns: what the document knows, a requirements checklist with empty boxes, and what person B knew, tree rings marked the job in use, watched for years; beneath both a gold box reads Recognition cannot be filed

The act

Then the act, because it deserves to be looked at directly rather than just admired.

Person B gave up her own position to protect someone else’s. In today’s working world this is nearly unheard of, and it is worth asking why. Not because people have become worse. Because almost nobody is positioned to do it. You cannot sacrifice for a value you cannot recognize - and person B was the only one in the building who could see what was about to be lost. She had chosen person A knowing the job, and then, as her boss, she had watched her do it - every working day, for five years. Her knowledge of the position and her knowledge of the person came from the same seat. The whole picture existed in exactly one place: her.

Notice also what the act reveals about the structure around it. Person B was holding two legitimate things at once - the organization’s budget reality and a person’s worth - and the structure offered her no instrument for honoring both. No reassignment, no review of what the position contributes, no process that weighs a person rather than a line item. So she built the instrument out of her own career.

Same reality, two meanings

Here is the part of this story I keep returning to, because it is the analysis person B deserves. Everyone in that meeting held the same reality: the same budget, the same numbers, the same person on the agenda. From those facts, the room built one meaning - a line item that no longer fits. Person B built another: a position she had answered for, a person she had watched for five years, a contribution the papers could not show, and a question about what her own remaining years were for. Same facts. Two meanings. Only one of them was complete enough to produce an act.

That ability - to build a second, fuller meaning from the same reality - is not a personality trait, and it is not kindness. It is a capacity, and it is built the way hers was built: by watching, and by answering for what you watch. It can be present or missing in a person, a department, a whole organization. And that is the deficiency this story exposes. The meeting did not lack information; everyone had the numbers. It did not lack decency; nobody there was cruel. It lacked the capacity to make the facts mean more than the procedure said they meant. When the people whose very title is “human resources” can form only one meaning from a human situation - the procedural one - the title has outlived the capacity it names.

How organizations lose that capacity, and what it costs them - why hiring and firing become the only two moments anyone truly looks at a person - is the second half of this story, and it deserves its own piece. Part two is coming: “Hired and Fired: The Space Between.”

What I feel, thinking about person B

I will separate this honestly, because it is not analysis. What I feel toward person B is not admiration, exactly - admiration is for performances. It is closer to gratitude at a distance, the kind you feel when someone proves a thing you hoped was still possible. And underneath it, one uncomfortable question I keep for myself: in her chair, with her years, would I have seen enough to do the same? Not “would I have been that generous” - generosity was the smaller part. Would I have watched closely enough to know what it was worth? That is the question her act leaves with everyone who hears about it.

What to do with this

For anyone who hires: before you write the description, go to the work. Watching is the beginning, not the point - the point is to experience and understand the essence of the job: what it actually needs, and the dynamics around it - who depends on it, what pulls at it, what carries it on a hard day. An hour beside the position teaches you more than every résumé you will read for it, and years inside its dynamics taught person B enough to stake her career on what she knew. If nobody on the hiring side has understood the job from inside, the interview is two documents talking to each other.

And the question I apply to everything, including this piece: what did I leave out? Two things, honestly. I know this story from one side; the organization surely has its own version, and budget pressure is real, not invented by villains. And the people in HR are also inside a structure, answering the incentives it hands them - this is not a story about bad individuals, which is exactly why it is worth telling. What that structure does, and why person B’s act cannot be its answer, is where part two begins.

One more thing, because the analysis should not get the last word - the people should. Somewhere right now, person A is settling into a new workplace, deciding how much of herself to hope with this time. And somewhere person B is retired, having given the last chapter of her career so that a colleague would not be discarded. If this piece does anything, I hope it is small and practical: that someone who hires reads it, gets up from the requirements list, walks over to where the work actually happens - and watches.

References

Adaptiverse, “The Boss Who Knew the Job” (film) - youtu.be/h3jyZDybANE

Trajlov (2026), doctoral research on paradox and meaning-making in professional soccer coaching

Adaptiverse, “The Two Gaps” (film and post) - the words-versus-landing distinction behind the requirements-list problem

About Adaptiverse

Adaptiverse is built on a simple understanding: more information isn’t the answer - meaning is. We help athletes, coaches and organisations make sense of what they live through and turn it into direction. For athletes, that starts with their own story, captured through structured reflections and tested against measurements from tracking and assessment devices. For coaches, teams and organisations, it means making sense of the work, communicating so it lands, and building the conditions to grow. Grounded in doctoral research.

Next
Next

After “Fine”: Why More Data Isn’t the Answer for Young Athletes