Your Customer Interview Isn't Data. It's a Story.

Watch an interview become a story.

A customer bought a new phone. It didn’t have a headphone jack. Just like that, the wired earbuds he loved were useless, and he was shopping for something he never wanted to shop for.

That’s not a data point. That’s a Push, and it’s scene one. Then came the search for a USB-C adapter he couldn’t find at a price he’d pay. That’s Friction. He gave up and accepted Bluetooth. He texted friends on the way to the store, spent ten minutes comparing, and hired a mid-tier pair on price and ear-tip shape. And the ending isn’t clean: they slip when he runs, so he’s still hunting for a way back to his old earbuds for workouts.

Six scenes. A beginning, a middle, and an unfinished end. A person feeling something the whole way through.

Here’s the thing. You ran interviews exactly like this one. You have the transcript, the highlighted quotes, the notes. But you can’t see the story in a transcript, and the story is the thing you interviewed to find: why they moved, in what order, and the moment the old way stopped being good enough.

So we stopped flattening it.

The interview, retold as six scenes

LEANSpark now takes a completed discovery interview and rebuilds it as a Customer Forces Story. Same spine every time: old way breaks, job requirements form, they hire something, first use, repeat use, the switch. Because switching decisions actually follow that arc, whether the customer can name it or not.

Each scene is driven by one of the four forces. Push, when the old way fails. Pull, when the new way calls. Friction and Inertia, the two that keep people stuck. The panel names the force that did the work and puts the verbatim quote right under it, drawn in napkin-sketch style so it reads like a comic strip, not a report. Underneath runs a journey map where the terrain is the customer’s sentiment: it climbs on hope, dips at every wall.

Why a story beats a spreadsheet

You can’t feel a spreadsheet, and you can’t put one in front of your co-founder and end the argument about who the customer is and why they’d switch. A story does both.

It also shows you your gaps. The scenes the interview never reached render as ghost panels, dimmed, each holding the question you should have asked. That’s your next interview’s opening question, handed to you.

What to do with it

Run your next discovery interview. When the analysis finishes, open the Customer Forces Story tab and read the decision as the story it always was. Then look at the ghost panels and write down what you didn’t ask.

Startups are stories. We’re going to keep saying that and keep building it into the product, because the founders who win are the ones who can tell their customer’s story better than the customer can. This is where we start.