A good story can carry almost anything

A few weeks after LIVED went out into the world, a reader who had read the book on using personal stories in professional settings gave this feedback: he liked the book. But he wished I’d added one more chapter on the situations where a story doesn’t belong.

When I thought deeply about this feedback, I understood that he was right. I treat storytelling as a kind of hyperbole. Almost everything looks like a story to me. Hand me a spreadsheet, and I’ll find the person underneath the numbers. Hand me a delay, a failure, an ordinary Tuesday, and I’ll find the arc in it.

That instinct has served me well. It also has a blind spot. If you believe a story fits everywhere, you stop noticing the rooms where it doesn’t. So here is the chapter I didn’t write, built almost entirely from times I got it wrong.

When the clock is screaming

In the late nineties, a client called us at the last minute. Their servers had to be up for a launch the next morning, and we were at the data center alongside their senior consultant, trying to get everything running on time. We were staring at the clock. We still hadn’t found the problem.

At some point, the consultant pulled a few of us aside and told us a story. He’d faced something just like this once, he said, with even less time on the clock, and he’d pulled it off. He meant to steady us. What he actually did was take three people who were mid-search and stand them still so he could narrate. We weren’t moved. We were closer to resentful, because the story assumed a calm we did not have and a solution we hadn’t even located yet.

When the clock is the loudest thing in the room, people don’t want meaning. They want to keep moving. A story slows the tempo at the exact moment everyone needs it to speed up. His story wasn’t a bad one. It was hours early. Told over dinner once the servers were up, the same words would have been a gift instead of an interruption.

When the pain belongs to someone else

I was fifteen when my father died. I was very close to him, and when he went, it felt like the world around me had come apart. I couldn’t picture a life without him in it. I was inconsolable.

In the middle of that, one of his friends came over to me. He told me he had lost his own father at nine. Earlier than I had lost mine, he pointed out, and he had still made it in this world.

I didn’t know what to say. I’m not sure he expected a reply. But I have remembered that sentence for the rest of my life, and not in the way he intended. He offered it as proof that I would be alright. What it actually did was take my grief and answer it with his. For a moment, the conversation was no longer about my father. It was about him.

I don’t think he was being unkind. He was reaching for the only thing he had, which was his own survival. But a story, even a true one, even a well-meant one, has gravity. It pulls attention toward the teller. When someone is raw, that pull is the last thing they need. The most useful thing you can offer is not a matching story. It is a short sentence, and then your whole attention. “I’m so sorry. I’m here.” And then you stay.

When the words have to be exact

Some moments need information to arrive clean, with no interpretation laid over it. A pilot on final approach does not pause to reflect on the night she nearly lost an engine. A surgeon reading a pre-op checklist does not stop to tell you what the work has come to mean to her. Dosages, wiring, the steps to shut off a valve, and a sworn testimony where one colorful aside can sink a case.

A story does what stories always do. It adds texture, feeling, and a little ambiguity. That is exactly what you do not want when a person has to act on your words under pressure, repeat them back precisely, or follow them in the dark. Give the instruction flat and exact first. The story about why it matters can come once the thing has been done right.

When the teller hasn’t earned it yet

I was once asked to judge a paper presentation at a college. The presenters were professors from other institutions, and before the session began, I was invited to give an opening address. I did what I do. I told them three stories about innovation.

The room gave me nothing. Polite, still, unmoved.

Then the other judge was asked to speak. He didn’t tell a single story. He put up numbers. How many papers had been presented, how many had gone on to be accepted by journals, the kind of figures that the audience counted as real. They leaned in. They responded to him in a way they had not responded to me at all.

For a while, I told myself that stories simply didn’t land with that crowd. I don’t believe that anymore. I think the stories failed because they came from me, and to that room, I was an unknown quantity. A stranger hasn’t yet earned the right to be heard at the level that a story demands. The other judge read the room correctly and spoke the native language. He gave them evidence, because evidence was the currency they trusted.

A story asks an audience to lend you something before you’ve shown them why you’re worth it. When they don’t yet know you, they won’t make that loan. You earn the standing first. The story comes after.

So, when does a story belong?

My reader was right, and I’ll put it more plainly than I did in the book. Knowing how to tell a story is half the craft. Knowing when to hold it is the other half.

Almost every time a story has failed me, the words themselves were fine. The moment was wrong. The clock was screaming, or the grief belonged to someone else, or the room didn’t know me yet. So now I run a quick check before I open my mouth. Is this urgent? Is this someone else’s pain to carry? Does this have to be exact? Do these people have any reason to trust me yet? If the answer points away from a story, I set it down. It keeps.

LIVED is about putting your stories to work. Consider this the missing footnote. A story only works when the moment is ready to receive it, and the real skill is never the telling. It is learning to tell the difference.