The Difference Between Writing What Happened and Writing What Mattered

Many moons ago, we found an interesting candidate on a Tuesday. He was fresh out of college with an Electrical Engineering degree, but had taught himself to code. To me, that signaled a self-starter, someone with the grit to solve problems without a manual. On paper, he was a great hire.

I voted not to hire him.

My reasoning was simple: our boss was a micromanager who created a high-pressure, unforgiving environment. It was a terrible place for a junior engineer to learn. My “no” vote was an act of protection. A few weeks later, my boss hired him anyway.

That’s what happened. But it’s not what mattered.

What mattered is that my judgment was completely wrong. My decision wasn’t a strategic assessment of risk; it was a failure of imagination. I was so focused on the flaws of the system that I discounted the potential of the person. The real story isn’t about a hiring decision. It’s about the lesson I learned when my cynicism was proven wrong.

In memoir, as in management, this distinction is everything. Your life has a chronology, a list of what happened. But a story that carries weight, a story that feels true, is built from what mattered.

What Happened: The Official Story

Writing “what happened” is documenting the sequence. It’s the professional, HR-friendly version of events.

• We interviewed a junior engineer with a promising background.
• I flagged our high-pressure environment as a risk.
• Management hired the candidate despite my reservation.
• I was assigned to mentor him, and he became a successful member of the team.

This is the event log. It is factual, linear, and clean. It’s also lifeless. It tells the reader nothing about the transformation, the stakes, or the human element.

What Mattered: The Unofficial Truth

Writing “what mattered” is about exposing the complex, often contradictory, system beneath the events.

• I saw a reflection of my younger self in that candidate and felt a misguided need to protect him from a struggle I assumed he couldn’t handle.
• My “no” vote wasn’t about him at all; it was a projection of my own frustration with my boss. It was a cynical prediction, and I was wrong.
• When my boss told me to spend a quarter of my time mentoring him, it wasn’t a burden. It was an unexpected act of trust that forced me to confront my own bias.
• His success wasn’t just a win for the team; it was a direct refutation of my own flawed judgment. The relationship we built became more valuable than the job itself — so much so that I took him with me to next company.

The events are the same, but now they are infused with motive, error, and growth. This is where a reader connects — not to the hiring process, but to the universal experience of being wrong about someone and learning something vital in the process.

How to Isolate What Matters

Your job as a memoirist isn’t to be a court reporter for your past. It’s to be an analyst, a systems thinker looking for the signal in the noise.

1. Run a Root Cause Analysis on the Scene. After writing what happened, diagnose it. Don’t just recount the decision; expose the belief system that drove it. Was it fear? Ego? A flawed assumption? Dig past the action to the core motivation.
2. Isolate the Moments of State Change. A story turns on moments where something fundamentally shifts. Your “no” vote was one state. Your boss overriding you was a state change. The moment the mentorship started working was another. Don’t give us every moment; give us the critical moments that altered the trajectory.
3. Capture the Human Telemetry. Action is plot, but the internal conflict is data. Show us not just your vote, but the internal debate that led to it. Show us the surprise and discomfort of being proven wrong. This “telemetry” — the mix of pride, cynicism, surprise, and humility — is what makes the facts feel true.

Your Story is an Architecture, Not a Timeline

What happened is the scaffolding. It’s essential, but it’s not the building. What mattered is the architecture — the flawed designs, the unexpected connections, the foundation of choices that gives the entire structure meaning.

The most powerful stories aren’t about getting everything right. They’re about getting it wrong, and having the courage to run the post-mortem on yourself. They are about the moments you were forced to update your own internal source code. That is the kind of story people remember.