First Story vs. Second Story

Every event has two stories.

The first one shows up fast. It's usually a sentence or two: an operator missed a step, a valve was left open, someone skipped a check. It's clean, it's specific, and it names a person or an action. It's also almost never the full picture.

The second story takes longer to find. It's the one that explains why the first story made sense to the person living it at the time.

What the First Story Gives You

The first story isn't wrong, exactly. It's accurate as far as it goes. If an operator missed a step, they did in fact miss it. That part checks out.

What the first story doesn't give you is context. It doesn't tell you what the operator was juggling in that moment, what the procedure actually looked like on the floor that day, or what normally happens right before that step that might explain why it got missed this time and not the hundred times before.

The first story is what you'd write down if someone stopped you in the hallway and asked what happened. It's fast, it's tidy, and it's built to close a conversation, not open one.

What the Second Story Requires

Getting to the second story means asking a different kind of question. Instead of "what did they do," you're asking "what did the situation look like from where they were standing."

That shift changes the whole tone of an investigation. You're not confirming a conclusion someone already reached. You're reconstructing a moment, piece by piece: the schedule pressure that day, the equipment history, the training that was actually delivered versus what the procedure assumes, the interruptions, the workarounds that had become normal because they worked every other time.

None of this excuses an outcome. It explains it. And explaining an outcome is the only way to prevent the next one, because you can't fix a condition you never identified.

Why Investigators Settle for the First Story

The first story is easier. It fits in a deviation record. It doesn't require multiple interviews or a careful walk of the physical space. It doesn't require sitting with someone long enough for them to trust you with what actually happened, and how it happened, rather than what they think you want to hear.

There's also a subtler pull: the first story usually points at a person, and pointing at a person feels like an answer. The second story points at a system, and systems are harder to summarize in a closing paragraph. But hard to summarize isn't the same as unimportant. It's usually the opposite.

How to Tell Which Story You're Looking At

A useful check: if your finding could have been written before the investigation started, you're probably still holding the first story. Findings like "the operator should have followed the procedure" or "training will be reinforced" tend to fall into this category. They're technically responsive, but they don't reflect anything you had to go looking for.

The second story reads differently. It surfaces something that wasn't obvious from the outside: a workaround that had quietly become standard practice, a gap between how a procedure reads and how it's actually performed, a piece of equipment that behaves differently than the manual describes. If your finding couldn't have been guessed in advance, you've probably reached it.

The Real Work Starts Where the First Story Ends

The first story will always arrive first. That's not a problem to solve, it's just how information works. The problem is treating it as the finish line instead of the starting point.

Every investigation worth running goes looking for the second story on purpose. It takes longer. It asks more of the investigator. And it's the only version that gives you something you can actually act on.

--

Want the full framework for getting past the first story? Beyond Human Error is open now. Start the course.