Start with one central message
Write one sentence answering: βWhat should attendees understand or be able to do when they leave?β Build your talk around that answer. Remove material that does not support it. A focused 20-minute explanation is often more valuable than an overloaded hour.
Suggested flow: the problem β why it matters β approach β example β lessons learned β next steps.
Build slides for the room
Use readable type, strong contrast, concise headings, and one main idea per slide. Avoid dense code screenshots and tiny diagrams. If showing commands, enlarge the terminal and explain what the command changes. Put references and optional detail in a shareable appendix.
Try reading the slides from across a room or on a small laptop screen.
Rehearse with a timer
Practice aloud at least once. Time the introduction, main sections, demonstration, and questions. Rehearse pronunciation of names and unfamiliar terms. Prepare a shorter version in case the program runs late.
Mark one optional section that can be removed without breaking the story.
Protect people and systems
Never expose real credentials, customer data, internal IP addresses, or confidential documents. Use test accounts and sanitized datasets. For live technical work, use snapshots and a reset plan. Keep a local backup of essential materials.
Use a pre-recorded fallback when the demo depends on a remote service.
Prepare your speaker information
Draft a short third-person biography, your preferred title and affiliation, name pronunciation if helpful, and a photograph you have permission to share. Verify that employer or project names are accurate.
The team will confirm the profile collection process and any publication consent.
Final readiness review
Check links, fonts, videos, audio, adapters, display settings, offline copies, and your closing slide. Save a PDF fallback alongside your editable deck. Reconfirm session details directly with the organizer.
Recommended personal checklist: deck / PDF / demo / backup / profile / contact / travel confirmation.

