Stop putting 'lessons learned' at the end

By Juan · October 15, 2025 #writing

Here’s a small writing rule I’ve come to believe in:

Don’t put a “lessons learned” paragraph at the end of a story about something that didn’t work.

You think it’s the point of the piece. It isn’t. It’s the part that ages the worst, undermines what came before it, and prevents the reader from doing the work the piece was supposed to provoke.

Three reasons

One: most lessons are wrong. Not just “questionable.” Wrong. Two years later you’ll read the lesson back and wince — at the false certainty, at how neatly you packaged a thing that was actually messy, at the way the lesson sounds like something you read in a TED talk. The story you wrote describes what happened; the lesson you tacked on describes what you were hoping the story meant. Those two things are not the same.

Two: lessons close the loop too early. A good failure story is supposed to make the reader think — about their own version of the same thing, about whether they’ve been doing it too, about the parts of their life that look uncomfortably similar. The lesson paragraph short-circuits that. It hands the reader a takeaway, which feels generous but actually steals the work. The reader nods at the takeaway and moves on. They don’t apply it to themselves because they’ve already received it.

Three: lessons turn writers into authorities. The story-then-lesson structure makes the writer the teacher and the reader the student. This is exactly the opposite of what most failure writing should do. You are not the authority on failure. You’re a person it happened to. The story is the artifact; the meaning belongs to the reader.

What to do instead

Three options, in order of how much I like them:

Stop writing. End on the last concrete thing that happened. Don’t generalize. Don’t moralize. Let the story sit. The reader’s brain will fill in the meaning on its own, and the meaning it fills in will be specific to their situation, which is more useful than your generic one.

End on a question. Not a rhetorical “what would you do?” question. A real one — something you genuinely don’t know the answer to. “I still don’t understand why I waited so long to leave.” That’s not a lesson; it’s an open thread. It invites the reader to think instead of nod.

Write the lesson, then delete it. Sometimes you need to write the lesson to find the ending — it acts as scaffolding. Write it, then read the post without it. Nine times out of ten, the post is better when the scaffold is gone.

The exception

There’s exactly one case where a lesson paragraph helps: when the lesson is specific, narrow, and counterintuitive.

“I shouldn’t have spent six months trying to make my cofounder relationship work after the first big fight. The relationship was over by month two; I was just paying interest on it for four more months.”

That’s useful. It’s specific to this situation, narrow enough to be transferable, and counterintuitive enough that the reader can’t have generated it themselves from the story alone.

The thing to avoid is the generic version:

“Sometimes you have to know when to walk away.”

Garbage. Not wrong, but useless. Strip these.

The test

Read your last paragraph and ask: if I deleted this, would the post be better or worse?

Eight times out of ten the answer is “better.” The post ends on the scene, the reader is left holding the weight, the moral fills itself in. The post becomes the property of whoever’s reading it instead of an essay you wrote at them.

Try it on the next story you write here. End on the description, not the takeaway. See what comes back.

— Juan