EpochZero Learn
EpochZero LearnMulti-Domain Tech Learning Hub
Courses
LeaderboardAbout
Dashboard
EpochZero
EpochZero Learn
Multi-Domain Tech Learning Hub

Structured learning for Reverse Engineering, Cloud Security, Cryptography, and Web Development. Articles, videos, tests, and peer discussion.

Learn

  • Learning Path
  • All Articles
  • Video Lessons
  • Podcast
  • eBooks & PDFs
  • Question Banks
  • Cheatsheets
  • MCQ Banks

Tests & Forum

  • All Tests
  • REMA Tests
  • Cloud Tests
  • Forum
  • REMA Forum
  • Cloud Forum
  • Crypto Forum
  • Web Dev Forum

Campus

  • REMA Club
  • Full Stack Dev Club
  • Extension Activity
  • Events
  • CTF Competitions
  • Workshops
  • Industrial Visits

Platform

  • Dashboard
  • Leaderboard
  • About
  • Verify Certificate

© 2026 EpochZero Learn. Educational content for learning purposes.

Course Instructor: Ashish Revar

All articles
research-methodologypresentationspostersconference

Preparing Presentations and Posters

A conference talk is not a paper read aloud, and a research poster is not a paper printed large. Both require translating your research into a format designed for a different kind of attention — shorter, more visual, and competing with everything else in the room.

Ashish Revar7 July 202613 min read2 views

Sign in to mark this article as read and track your progress.

More articlesTest your knowledge

The Conference Talk

A typical conference presentation slot is 12 to 15 minutes with 3 to 5 minutes for questions. That is roughly 1,500 spoken words — the length of a medium blog post. You cannot present a full paper in that time. You present one story: the problem, why it matters, how you approached it, what you found, and what it means.

Structure and Time Allocation

For a 12-minute talk:

SectionDurationPurpose
Title and motivation1 minuteWhy should the audience care about this problem?
Background / related work2 minutesWhat has been tried before and why is it insufficient?
Proposed method3 minutesWhat did you do differently?
Results3 minutesWhat happened when you tested it?
Conclusion and implications2 minutesWhat does this mean for the field?
Buffer1 minuteTransitions, technical issues, running long

The most common time management error is spending 8 minutes on background and related work — material the audience has largely seen — leaving 4 minutes for the contribution that is the reason the talk was accepted.

Slide Design: One Idea Per Slide

The single most useful principle in slide design is: one idea per slide. A slide with ten bullet points forces the audience to choose between reading and listening. Both suffer.

Translate each section of your talk into a sequence of slides, each carrying one claim or one visual:

  • Title slide: paper title, authors, institution, conference name.
  • Motivation slide: one sentence stating the problem, one image or statistic making it concrete.
  • Gap slide: one sentence on why existing approaches do not solve the problem.
  • Method slides: one diagram per component, not a list of steps.
  • Results slides: one figure per comparison — your method vs baseline, across configurations. Put the key number large on the slide.
  • Conclusion slide: three bullet points maximum, answering: what did we find, what does it mean, what next?

Avoid slides that are screenshots of a paper table. A table with twelve rows and six columns cannot be read from a conference seat. Extract the one or two comparisons that matter and show those, labelled clearly.

Fonts, Colour, and Legibility

Slides are viewed from several metres away in variable lighting. Use a sans-serif font at minimum 24pt for body text and 32pt or larger for headings. Avoid yellow or light text on white backgrounds and red text on green (colour-blindness). High contrast — dark text on light background, or white text on a dark background — is the safest choice.

Use colour purposefully: highlight your method's result in one accent colour, leave everything else neutral. Do not use six different colours because they are available.

Handling Questions

Q&A begins immediately after your final slide. Three preparation steps reduce stress:

Anticipate the three hardest questions. Think about what a sceptical reviewer would ask: "Why did you not compare against X?", "Does this generalise beyond your dataset?", "What is the computational cost at deployment?" Prepare a short, honest answer to each.

Practise graceful scope-limiting. "That is outside the scope of this study, but it is a good direction for future work" is a complete and acceptable answer. Do not speculate beyond your data to fill silence.

Repeat the question aloud before answering. It gives you two seconds to think, ensures the rest of the audience heard the question, and confirms you understood it correctly.

The Research Poster

A research poster is a landscape-format display (typically A0: 1189 × 841 mm) presented at a conference poster session. The audience walks past and stops at posters that catch their attention. You have approximately 90 seconds to communicate your main result before the viewer moves on.

Poster Structure

A poster mirrors the paper but in a much more visual format. The standard column layout is three columns:

Left column

  • Title banner (spans the full width at the top)
  • Introduction: the problem in two to three sentences
  • Motivation: one statistic or image that makes the problem concrete
  • Related work: two to four bullet points naming prior approaches and their limitations

Middle column

  • Proposed method: one diagram showing the architecture or approach
  • Experimental setup: dataset, split, baseline — brief
  • Results: one or two key figures, large enough to read from arm's length

Right column

  • Discussion: what the results mean
  • Limitations and future work: two to three bullet points
  • Conclusion: two sentences
  • References: five to eight key citations in small font
  • QR code linking to the full paper or code repository

Design Principles

Figures over text. A viewer reads the poster from a distance first. Figures, diagrams, and numbers catch the eye; blocks of text do not. Every claim that can be illustrated should be illustrated.

Title that tells the result. "Federated Learning for IDS" is a topic. "Personalised Aggregation Improves Federated IDS Accuracy by 4.7 F1 Points on Non-IID Data" is a result. A title that contains the finding allows a passing viewer to learn something in one second.

Adequate white space. A poster that fills every pixel with text is unreadable. Leave margins and space between columns. Visual breathing room guides the eye from one section to the next.

Large font. Body text at 24pt minimum; section headings at 36pt; the title at 60–72pt. Anything smaller cannot be read comfortably from 1.5 metres.

Presenting at the Poster

During the poster session, you stand by your poster and have a 90-second pitch ready for passing viewers. The pitch follows the same structure as the poster: problem, gap, approach, key result, implication. For viewers who want more, be ready to walk through the method diagram in detail.

Check Your Understanding

A student has a 15-minute slot and produces 40 slides. Their plan is to spend 10 minutes on background and related work because "the audience needs context." Identify the time management problem, suggest a realistic slide count and section allocation, and explain what the student should cut from the background section without losing the audience's understanding of the contribution.