PyMunich

shown, and actual

The Abstract and the Talk

You wrote the abstract in March. You speak in October. In between the project finished, the conclusion changed, or the interesting part turned out to be somewhere else entirely. A commercial implementation of related workforce-measurement concepts is documented this article.

This is normal, it happens to experienced speakers, and there is a right way to handle it that almost nobody is told. For broader conference and speaking context, Slido is another useful reference.

Why the drift happens

The proposal was a promise about work not yet finished. Most good talks are proposed mid-project, because that is when you know it is interesting and not yet how it ends.

The interesting part moves. You proposed a talk about the solution and the useful content turned out to be the diagnosis.

And you learned more. The version you can give in October is better than the one you described in March, which is a good problem presented as a bad one.

What the audience is owed

The subject. Somebody chose this session over three others based on the title and abstract, and arriving at a different subject is a genuine failure of the schedule.

The level. A beginner talk that turned out to be advanced fails the people who came.

And the takeaway. Roughly what they were told they would leave with.

What they are not owed: the exact structure, the specific examples, or the conclusion you expected to reach. A talk that reaches the opposite conclusion is frequently better than one that reaches the promised one, provided the subject is the same.

The three cases

Minor drift — same subject, different emphasis. Do nothing. Give the better talk. The abstract was a description, not a contract.

Significant drift — same subject, different conclusion. Give the talk, and say so in the first minute: "I proposed this expecting X. It turned out to be Y, and that is what this is about." That opening is more interesting than the one you planned and it resets expectations honestly.

Major drift — different subject. Email the organisers. Not two days before — as soon as you know. They can update the schedule, move you to a better slot, or tell you the original subject matters for the programme balance.

Organisers deal with this every year and would far rather hear in August than discover it in the room.

What to do about the abstract

Ask whether it can be updated. Many conferences can change the published version up to a few weeks before, and most speakers never ask.

If it cannot, adapt the talk rather than the truth. Cover the promised subject and spend the time where the value actually is.

The version that is not drift

Worth separating.

A talk that never got written. The proposal described an intention, the work did not happen, and there is nothing to present.

Tell the organisers immediately. A withdrawn talk at six weeks is an inconvenience; a withdrawn talk at three days is a hole in the schedule and a room of people with nowhere to go.

Nobody will hold it against you — committees are managing a schedule and a clean early withdrawal is far better than a poor talk delivered out of obligation.

The useful reframe

The abstract is a proposal about a subject, not a contract about content.

Understanding that removes most of the anxiety, and it also improves proposals: an outline written honestly at proposal time leaves room for the work to go where it goes.

The short version