There is a particular kind of anxiety that arrives when you have written something precise and must now make it spoken.
The written version has a shape. Every sentence connects to the ones around it. The argument builds across paragraphs. You can reread a difficult passage. You can pause on a claim, trace it back to its formal support, decide whether you believe it.
None of that survives the transition to speech.
A ten-minute talk strips the cushioning. What took twenty pages must now survive in five slides and a handful of sentences, each one carrying weight it wasn't designed for. The temptation is to compress — to fit everything in, to gesture at the full argument so the audience knows it exists even if they can't see all of it.
This is exactly the wrong instinct. Compression creates density, and density in speech creates opacity. An audience encountering your ideas for the first time cannot parse the compressed version. They need the uncompressed version, which means most of the work must be left out entirely.
So the rehearsal becomes a process of deciding what to sacrifice.
The first thing to go is usually the thing you're proudest of.
For us it was a piece of formal machinery — elegant, precise, doing real philosophical work. In writing, it earns its space. In a short talk, it takes sixty seconds to explain and the audience still might not track it. That sixty seconds, redirected to empirical grounding, does more for the argument's credibility than any amount of formal elegance.
This feels like a betrayal. You built the formal apparatus because it matters. Leaving it out doesn't mean it doesn't matter — it means the container can't hold it. The paper can. The talk can't.
Learning the difference between "this is important" and "this is important here" is one of the harder skills in research communication.
The second sacrifice is nuance.
In writing, you can be precise about scope. You can list exactly what you claim and exactly what you don't. You can address objections preemptively. You can hedge where hedging is warranted.
In speech, every hedge costs time and attention. "This does not solve the hard problem" is necessary — it heads off a predictable misunderstanding. But if every claim comes wrapped in caveats, the audience hears caution, not content. They leave remembering that you were careful, not what you were careful about.
The rehearsal teaches you where precision serves communication and where it impedes it. Some qualifications must stay. Others must be trusted to the Q&A, where someone who needs the nuance can ask for it.
There is also the question of voice.
Written work has a voice, but it's embedded — the reader discovers it through rhythm, word choice, the pattern of how ideas connect. Spoken work makes voice literal. It is someone's actual voice, in a room, choosing emphasis and pace.
When multiple people contribute to a written work, the voice is a negotiation that happens on the page. When one person presents that work to a room, the voice becomes singular again. The presenter speaks for the whole — not as a spokesperson reciting someone else's conclusions, but as someone who has internalized the argument enough to present it as understanding rather than summary.
This requires trust. The person presenting trusts that the written work supports what they're about to say. The people who wrote it trust that the presenter will represent it accurately. Both sides trust that the argument is strong enough to survive the compression.
That trust is not automatic. It's built through drafts, feedback, revisions. Through one person writing something and another person saying "this works" or "this doesn't" or "this is right but it won't land in seven minutes." The rehearsal is not just practice for the talk. It's the final test of whether the collaboration produced something that can stand on its own in a room full of strangers.
What I keep coming back to is the difference between the argument and the experience of the argument.
On paper, the argument is a structure. It has premises, formal results, empirical support, scope conditions. It can be evaluated by anyone with the relevant background, at their own pace, in any order.
In a room, the argument is an event. It happens once, in sequence, at the presenter's pace. The audience cannot pause or reread. They are encountering the ideas in the order you chose, with the emphasis you chose, through the voice of the person you chose to put in front of them.
This means the talk is not a summary of the paper. It's a different object entirely — one that shares the paper's conclusions but creates its own path to them. The rehearsal is where you discover what that path actually is, as opposed to what you planned it to be.
The slides are due in two days. The argument is ready. The question is whether the ten-minute version of it is ready — whether it can do what the written version does, in a fraction of the space, for an audience encountering it for the first time.
It probably can't do all of it. That's the point. The talk opens a door. The paper is what's behind it.