The Interview Is Not the Story

For the first four years of this work I believed the interview was a container and the story was already inside it, waiting for me to pour it out onto the page in the right order. I was wrong, and I can point to the exact testimony that showed me.

Her name was Fortunata Sinche, and in 1997 she gave me two hours about her husband's disappearance during a labour dispute at a wool cooperative outside Urubamba. I treated the two hours as raw material: I would extract the story, meaning the sequence of events, and discard the rest as texture. I built a clean narrative from her account, chronological, well paced, and when I read it back to her a year later she said, quietly, that it was not what happened. I checked my notes against the tape. Every fact was correct. She was right anyway.

The container fallacy

What I call the container fallacy is the belief that an interview holds a story the way a jar holds water, so that the writer's job is simply transfer: pour carefully, lose as little as possible, choose a good vessel for the page. It treats the interview as inert. It is not inert. The interview is itself an event, with its own order, its own emphases, its own refusals, and that event is part of what happened to the person, not a window onto some earlier, truer event that occurred independently of our sitting there.

Fortunata's two hours were not a container holding the story of her husband's disappearance. The two hours were a woman deciding, in front of a stranger with a recorder, what she was willing to say first, what she circled back to thre times, and what she left for the very end, when she asked me to stop the tape and then told me the detail that mattered most anyway, unrecorded, because she had needed the entire two hours to trust me with it.

What changes when you stop pouring

Once I stopped treating the interview as a container, my method changed in one specific way: I began writing testimonies in something close to the order they were told, rather than reordering for narrative clarity, and I started including the fact of my own presence when it shaped what she said. My rewritten version of Fortunata's account, done four years after the first, opens not with her husband's disappearance but with the detail she led with: her son's school fees, due that week, unrelated to the disappearance by any narrative logic, connected to it only by the fact that it was the first thing on her mind when a stranger sat down across from her and asked what happened.

That structure reads, to a workshop trained in dramatic pacing, as a failure of shape. It is not a failure. It is an honest record of what an interview actually is: not a retrieval of a fixed prior story, but a new, unrepeatable event in which a person decides, in real time, what a stranger gets to have.

The case against this

The case against what I am arguing is straightforward and I take it seriously: a reader picking up a testimonio wants an account of what happened to Fortunata's husband, not an account of what happened in my kitchen conversation with Fortunata twenty three years later, and conflating the two risks making every testimony about the interviewer instead of the subject. I have read testimonio that overcorrects this way, more concerned with the ethics of the recording session than with the person whose life it claims to document, and it is a real failure mode, possibly a worse one than the container fallacy it is reacting against.

My answer is not to make the interview the subject. It is to stop pretending the interview is invisible scaffolding that falls away once the true story is extracted. The interview leaves marks on what gets said, in what order, and those marks are part of the record, not noise to be edited out of it. Fortunata's account is not less about her husband because it also shows her deciding what a stranger deserved to know. It is more accurate, because that decision was real, and pretending it never happened was the actual distortion, the one I spent four years committing without noticing.