The "Why" Is the Job

A plea for storytelling in People Operations

Somewhere in the last decade, we stopped asking People teams to explain why.

Not on purpose. Nobody voted on it. But go read the job descriptions - Coordinator, Generalist, Business Partner, Director, Head of People. HRIS administration. Benefits renewal. Multi-state compliance. Performance cycle management. Data and reporting. All real, all necessary, all work I've done and will do again.

And almost nowhere, in any of them, the thing that makes any of the rest of it land: the responsibility to tell the story.

I want to make the case that this is the most expensive omission in our field right now. Not because storytelling is a nice extra for companies with the budget for culture. Because it is load-bearing, and we have quietly stopped naming the person who carries it.

Three parts of the job that are already storytelling

Change management is storytelling. Every reorg, every merger, every pivot, every layoff. You can send the most accurate memo ever written and still lose the room, because a clear directive is superficial when it lacks context. I've watched a two-hundred-person organization come through a merger, and the lesson was not subtle: people do not need to be told what changed. They need to understand their role in the plot. If you don't give them one, they will write themselves in as the victim - and you cannot blame them, because you left that part blank.

Policy is storytelling. A handbook is the document where a company says out loud who it thinks it is. Most of them read like they were drafted to protect the company from its own employees, and employees read them exactly that way. The policy that actually gets followed is never the strictest one; it's the one where the why was clear enough to survive the moment when following it is inconvenient.

Recruiting is storytelling, and we all know it. You are asking a person to leave something known for something unknown, on imperfect information, usually for comparable money. Nobody makes that trade off a bulleted list of benefits. And the story has to be true, because the candidate becomes an employee and the employee finds out.

Three of the biggest things on the People Operations list, and all three are storytelling problems wearing an administrative costume. We've written the costume into the job description and left the body out.

What storytelling actually is

Here is where I think the confusion starts. "Storytelling" sounds like a writing skill, so it gets sorted into marketing, or into the soft-skills bin next to "strong communicator."

It isn't a writing skill. It's a finding skill.

I learned it in a tech and startup newsroom, running the same set of questions across a hundred stories a week - because the raw material is always there, and the job is knowing where to look:

• Look for patterns.
• Look for consequences.
• Look for lessons.
• Look for utility.
• Look for vulnerability.
• Look for the future experience.
• Look for the recollection - the thing a person already tells about themselves.

Those questions do not stop working when you leave media. Run them on an engagement survey. Run them on an exit interview, a benefits open-enrollment window, a resignation letter, a Slack channel that went quiet three weeks ago. They get more useful in this work, not less, because the stakes get more personal.

That's the craft. It's teachable. It's measurable, if you care to. And it is nowhere on the requirements list.

Facts don't travel alone

Annette Simmons wrote that stories are "more true" than facts, because stories are multidimensional. An observable fact does not, on its own, communicate a truth. Offer facts without a story and the facts will not be believed.

Every People leader has lived this. You send the announcement. It is accurate. It is thorough. It is also, within about forty minutes, being retold in three DMs in a version you would not recognize.

That's not a failure of clarity. It's a failure of narrative. And here's the practical version, the reason I think this belongs in a job description rather than a values deck: story is the least invasive way to make sure your message gets replayed later, at the right time, along the lines you intended.

You cannot be in every room. You will never be in every room. What you can do is hand people something that holds up when you're not there.

The part underneath

Storytelling is the visible skill. The one underneath it is empathy - specifically, the kind that supplies context.

A good storyteller stays in touch with, and on the side of, the listener. That's the entire discipline. Not spin. Not polish. Not internal comms as a laundering service for bad news. It's the ability to sit with what someone actually feels on a Tuesday when the roadmap changed for the third time this quarter, and connect them back to work that still means something to them.

I've onboarded seventy people into a fully remote company as the only HR person in it, which means seventy times I was the first real impression someone formed of a place they'd just gambled their career on. That is not an administrative transaction. Every one of those conversations was a person asking, underneath the logistics, did I make a mistake? You do not answer that with a checklist.

Ambiguity is the default condition now. It's not a phase companies are passing through on the way back to stability. And in ambiguity, motivation cannot come from certainty, because there isn't any. It comes from people being able to locate themselves in something larger than the week they're having.

Giving them that is the job. Whether or not anyone wrote it down.

The ask

Put the line back in.

Something like: owns the internal narrative - the why behind the what. Six words in a job description, and suddenly the work is visible, ownable, resourced, and reviewable.

Because someone at your company is already doing it. That's the part I want to be clear about. This work does not go undone; it goes unnamed. It falls to whoever happens to be good at it, on top of everything else, uncompensated and unmeasured - and when that person leaves, nobody can quite say what left with them. They just notice that the all-hands stopped landing, and the handbook got a little more defensive, and offers started falling through at a rate no one can explain.

So if you're hiring in People right now, go read your job description and ask whether the thing you need most is written anywhere on it.

If you're a founder wondering why the message keeps arriving distorted, ask who you've made responsible for the why. Not for the announcement - for the why.

And if you've been the person quietly holding the narrative together while your title said something else entirely: you were doing real work. Name it. Ask to be paid for it. I'd love to hear how it's going.