Presenting at a conference is one of the most useful things a researcher can do, and one of the most nerve-wracking — especially the first time. A conference presentation puts your work in front of people who know the field, gives you feedback while the work can still change, and introduces you to future collaborators, reviewers, and employers. It also forces a useful discipline: explaining your research in ten minutes to a live audience reveals gaps in the argument that months of writing can hide.
This guide covers the whole process: choosing a conference, writing the abstract, preparing an oral talk, designing a poster, handling questions, and making the most of the event itself. It assumes you already have research worth presenting — if you are still at the writing stage, our guides on writing a research abstract and publishing a research paper will help you get there first.
Not every conference is worth your time and money. Start with fit: does the conference's theme and audience match your work, and will the people in the room understand and use it? A small specialist meeting where twenty people work on your exact problem is usually more valuable than a huge general conference where your talk reaches no one who follows the topic. Check who presented in previous years, what the sessions cover, and whether the organisers publish proceedings or abstracts — a conference that publishes your abstract gives the work a citable record, which is worth something on a CV.
Also check the practicalities before submitting: the dates, the location and travel cost, the registration fee, and whether student or early-career discounts exist. Many conferences offer fee waivers or travel support for students, but you must ask early, because those funds run out. Be cautious about conferences that accept everything, charge high fees, and advertise aggressively without a recognisable programme committee — a presentation at a low-quality event adds little to your record and can look worse than no presentation at all. Our guide on spotting predatory journals explains similar warning signs, and several of them apply to conferences too.
The conference abstract is a short summary — usually 200 to 300 words — that the organisers use to decide whether to accept your presentation and in which session to place it. It follows the same shape as a paper abstract: background and question, methods, main results, and conclusion. The difference is emphasis: a conference abstract must make the contribution obvious quickly, because reviewers read dozens of them, and it may describe work in progress, with preliminary results clearly labelled as such.
Write the abstract for the session, not for yourself. Use the conference's own theme words where they genuinely fit, so that reviewers can see where your talk belongs. State the finding, not only the topic: an abstract that says "this study examines X" without saying what was found gives reviewers nothing to judge. Check the word limit, the formatting rules, and the deadline carefully — abstracts are commonly rejected for missing a deadline or exceeding a limit, not for weak science. If the conference asks you to choose between an oral talk and a poster, choose honestly: a strong poster in a busy poster session often reaches more useful people than a weak talk in an empty room.
A good talk has one message, not five. Decide the single takeaway you want the audience to remember, and build the talk around it: a brief opening that states the problem and the question, a short account of what you did, the main results, and the conclusion that answers the question. Cut everything that does not serve that message, however interesting it is. A ten-minute talk needs roughly ten slides at most, and a fifteen-minute talk roughly twelve to fifteen — one slide per minute is a safe rule, because presenters almost always run over, not under.
Design slides for listeners, not readers. A slide should carry one idea, with a short headline that states the point, and a visual — a figure, a diagram, or a few key numbers — rather than paragraphs of text. If the audience is reading your slides, they are not listening to you, and they will remember neither. Use a large font, high contrast, and consistent colours, and check that every figure is readable from the back of a room. Put detailed tables and methods in backup slides, not in the main talk, so that you can show them if asked but never waste the audience's time on them unprompted.
Rehearse out loud, with a timer, at least three times. Rehearsal is where talks are fixed: it reveals sentences that cannot be spoken smoothly, slides that take too long, and transitions that do not work. Time yourself strictly, because conferences cut speakers off, and a talk that runs over steals time from the next speaker and from questions. If you are presenting in a second language, rehearsal matters even more — write out the first and last sentences word for word, since those are the moments when nerves are worst, and speak slowly enough that the audience can follow.
A poster is not a paper pinned to a board; it is a visual summary designed to start conversations. A reader should grasp the question, the method, the main result, and the conclusion in under a minute, from a metre away. That means a clear title in large type, a logical reading order — usually columns read top to bottom, left to right — short sections with headings, and one or two strong figures rather than walls of text. Aim for roughly 300 to 500 words on the whole poster; more than that, and readers will walk past.
Design for the poster session, not for printing. Use a plain background, dark text, and a single accent colour. Make figures large and labelled, and include your name, affiliation, and contact details where a reader can find them without hunting. Print early and check the actual size: a poster that looks fine on screen often has unreadably small text when printed. At the session itself, stand by your poster, greet people, and offer a two-minute summary — "We asked this, we did this, we found this" — then let the visitor ask questions. Bring a few handouts or a QR code linking to the paper or your contact page, because the best conversations at a poster often continue by email afterwards.
Questions are the most valuable part of a presentation, and the most feared. Prepare by listing the hardest questions your work invites — about the sample, the method, the interpretation, and the limitations — and rehearsing short, honest answers. When a question comes, listen to it fully, repeat it briefly so the room hears it, and answer it directly. If you do not know the answer, say so and say what you would do to find out; bluffing in front of specialists is quickly detected and long remembered. If a question is hostile, stay calm and factual — the audience judges the questioner as well as you, and a composed answer earns more respect than a defensive one.
Beyond your own talk, use the conference deliberately. Attend sessions outside your narrow topic, because new ideas usually come from neighbouring fields. Introduce yourself to people whose work you cite — most researchers are pleased to meet someone who has read their work, and a short conversation can lead to collaboration, a reviewer suggestion, or a job lead. Take notes on talks, collect contacts the same day, and follow up within a week with a short email referencing the conversation. The talk itself lasts minutes; the relationships and feedback from a conference can shape years of work, which is why the event deserves as much preparation as the slides.
Virtual and hybrid conferences deserve the same preparation as in-person ones. Test your connection, camera, and microphone in advance, and have a backup plan if the technology fails, such as a PDF of your slides you can share. Look at the camera rather than at your own image, keep your background tidy, and mute yourself when you are not speaking. Online poster sessions often use breakout rooms or chat threads, so prepare the same two-minute summary and be ready to share your screen. The audience may be smaller on screen, but the feedback and contacts are just as real.
The most useful part of a conference often happens after you leave. The questions people asked are a free review of your work: they show which parts of your argument were unclear, which claims sounded too strong, and which limitations your audience spotted before you mentioned them. Write those questions down on the evening of your talk or poster session, while you still remember the exact wording. A question asked twice, by two different people, is almost certainly a weakness a journal reviewer will also find, and it is far cheaper to fix it now than after submission.
Within a week, follow up with the people who gave you useful feedback. A short email thanking them, with your slides or poster attached, is enough, and it is the normal way conference contacts become collaborators, future co-authors, or reviewers who already understand your work. If someone offered data, a method, or an introduction to another researcher, say so in that email and suggest a concrete next step, such as a short call. Keep a one-page conference log as you go: who you met, what they work on, what they asked, and what you promised. Without it, half of those conversations are forgotten within a month, along with the collaborations they could have started.
Finally, feed the feedback back into the manuscript itself. A repeated question about your sample becomes a sentence in the limitations section. A challenge to your interpretation becomes a paragraph that acknowledges the alternative reading and explains why your reading still holds, or concedes the point honestly. A suggestion for a further analysis, if it is feasible, becomes a genuine addition to the paper rather than a polite nod. When the revised paper goes to a journal, it carries the benefit of an audience that has already tested it, and your conference presentation has done more than advertise the work: it has improved it.
| Feature | Oral talk | Poster |
|---|---|---|
| Audience | Whole session room at once | One visitor at a time, in conversation |
| Time | Fixed slot, usually 10–15 minutes | Session length, conversations as visitors arrive |
| Content | One message, about one slide per minute | Question, method, result, conclusion in 300–500 words |
| Best for | A clear, complete result with a strong story | Work in progress, detailed figures, discussion |
| Main risk | Running over time or reading slides aloud | Too much text, so readers walk past |
| Follow-up | Questions from the room, then email | Handout or QR code, email within a week |
These authoritative external resources explain the standards and guidance mentioned in this article:
Should I present work that is not yet published?
Yes — conferences exist for work in progress. Label preliminary results honestly, and check the conference's policy on prior presentation before submitting the same work to a journal, since some journals treat a published conference proceeding differently from an abstract.
How do I choose between an oral talk and a poster?
Choose a talk for a clear, complete result with a strong story; choose a poster for work in progress, detailed figures, or work that benefits from one-to-one discussion. A strong poster often reaches more useful people than a weak talk.
How many slides do I need for a 10-minute talk?
About ten, at roughly one slide per minute. Presenters almost always run over, so fewer slides with a clear message beat a dense deck you never finish.
What if I am asked a question I cannot answer?
Say so honestly and say what you would do to find out. Bluffing in front of specialists is quickly detected; an honest "I don't know" earns respect and often leads to a useful suggestion from the questioner.
Should I read my talk from a script?
No. Reading aloud loses the audience. Rehearse enough to speak from notes and slides, and write out only the first and last sentences word for word, since those are the moments when nerves are worst.
How do I follow up after the conference?
Within a week, send a short email to each useful contact, referencing your conversation and attaching the paper or poster if promised. Contacts collected but never followed up are the most common wasted outcome of a conference.