The Many Flavors of Technical Presentations
Oh, how many ways can I present thee?
Part of the series: Comprehensive and Practical Guide to Technical Presentations
ππ» Talk Formats
Did you know there are several different styles (or “types”) of presentations? Here are a few popular formats.
β‘ Lightning talk
A personal favorite of mine, these are short (5 - 15 minute) minute presentations designed for maximum impact in minimal time. Stripping your presentation down to a short period captures the essence of what you are trying to convey. It can be easier to prepare and practice these talks as well. In my opinion, this is the best type of session. Why? Because people tend to have short attention spans, so I suspect the shorter sessions have more impact.
This is the full deck from my lightning talk about the power of #serverless and the flexibility of @azureFunctions that I gave at the @MSFTReactor for our #dotNETConf viewing party today! Direct link to the presentation is here: https://t.co/pa18Dxa2hz pic.twitter.com/gmjTTaKG9d
— Jeremy Likness β‘οΈ (@jeremylikness) September 12, 2018
π£ Breakout session
This is the common format of a classroom-style presentation with you speaking for anywhere from a half hour up to 75 minutes. I personally find that 45 minutes is a “sweet spot” and don’t like the longer formats but be prepared for anything in that range.
Enterprise #serverless: deck and demo videos:
— Jeremy Likness β‘οΈ (@jeremylikness) October 8, 2018
β create an @AzureFunctions app and watch it scale automatically
β publish a local function to the #cloud
β logic app connects images to #ml #MachineLearning #ai and #slack
β event grid: native and customhttps://t.co/epHW7Jxz7l pic.twitter.com/d4wWhsYBov
Example of demos with step-by-step instructions for a breakout session:
π₯π₯ Panel
A great way to get in front of an audience for the first time, instead of preparing demos and decks, you can participate in a panel and answer questions based on your insights and expertise. These may be open topics and questions or have a set of prepared questions you can research beforehand.
@mtrapnell @jeremylikness @jeorryb @brettsboss, digging into Cloud Architecture here @iVisionATL TechSummit pic.twitter.com/Jcl7hyQuGr
— Stephen Owen π¦ deploy (@FoxDeploy) September 26, 2015
π Keynote
The keynote is often the first session of the conference or the day, although many events host closing keynotes as well. The keynote is designed to set the tone or mood of the conference and kick everything off in a positive, energetic, and insightful way (or conclude with some powerful parting thoughts). Successful keynote speakers know their audience and build content that appeals to attendees and resonates with the theme of the event.
@jeremylikness look at you up there doing #codestock stuff. pic.twitter.com/ETBrFauuwK
— Adam Williams (@rescuecoder) April 12, 2019
Example keynote content:
Thank you ππ» everyone who attended the #CodeStock Friday keynote π this morning "A Tale of Short Links π"
— Jeremy Likness β‘οΈ (@jeremylikness) April 12, 2019
Welcome to the conference and I wish you abundant networking π₯, learning π©π»βπ, and plenty of fun π€£ these next two days.
Download the slides here: https://t.co/iUjqHkxSuf pic.twitter.com/h0eHfke6so
π£ General Session
A general session is like a keynote. Events with multiple tracks will often have a general session that is not called a keynote because it’s meant to be more like a breakout session that appeals to everyone.
π Workshop
Workshops usually last for hours or days and walk the audience from start to finish through a concept. They are often classroom style and feature hands-on labs that the speaker(s) assist with. If you enjoy teaching and mentoring, you may find you enjoy the workshop format. The caveat is it takes significantly more time to prepare than ordinary talks. For example, if I am doing a day long workshop (typically 6 hours of “active” content, the rest of the time is taken by lunch and breaks) I look at it as preparing 6 talks plus being able to follow the lab steps and verify that they work to produce a completed product.
π€ Today is all about Azure at @TechBash!
— Brandon Minnick (@TheCodeTraveler) October 2, 2018
π @nthonyChu, @jeremylikness and I are leading the Azure for Developers workshop #TechBash
π Check it out! https://t.co/ncLIUXtD7n pic.twitter.com/iyOQCg3PGS
Example workshop:
brminnick/azure-for-developers-workshop
π¬ Lab
Compared to workshops that involve active presenters, labs are typically self-guided activities with proctors to help. The audience is pointed to a resource that contains detailed instructions, and proctors are available to answer questions and help troubleshoot problems.
Example of a hands-on lab:
JeremyLikness/azure-fn-file-process-hol
π©π»βπ« Open Spaces
I love conferences that provide open spaces! These are ad hoc presentation areas. Usually you sign up for an open space with a presentation or even an idea for discussion. You get assigned a time slot and then anyone interested stops by to collaborate. It’s usually more intimate and less pressure than a full presentation. Consider trying these out at a conference if you’re not sure you are ready to take the stage. Often, I find topics include support for aspiring speakers.
π¦π¦ Birds of a Feather
Another casual way to share your knowledge: with “birds of a feather” you are encouraged to mingle with attendees to answer questions and share your insights. This is often done over lunch, and tables are labeled with either names or topics that people can sit to discuss. Birds of a feather facilitates comfortable and casual interactions.
Birds-Of-A-Feather Lunch at #VSLive Las Vegas is going down in 15 minutes! Please gather around your favorite speaker and eat lunch together where you can discuss a topic of your interest! #Developers #TrainingConference
— Visual Studio Live! (@VSLive) March 6, 2019
Pro-tip It’s fine to share your talk at multiple venues, especially if you are speaking nationally and internationally. Every audience is a fresh opportunity to engage with more developers. I welcome feedback and constructive criticism for my sessions, and often find by taking that feedback and tweaking my talk it is much better on the fifth delivery compared to the first. I will also often craft a talk based on the longest session I’ll give (60 or 75 minutes) and then trim it back to create condensed versions for shorter speaking slots.
Hopefully this list helps with your decision!
The example talk here is a presentation called “Intro to TypeScript” that I delivered to a local user group, The Atlanta JavaScript Meetup Group.
Regards,
Part of the series: Comprehensive and Practical Guide to Technical Presentations
- A Guide for Everyone Who Wants to Give Technical Presentations
- How to Choose Where to Give Your Technical Presentation
- The Many Flavors of Technical Presentations
- The Amazing Secret to Crafting Conference Submissions that Don't Suck
- Build a π£ Bomb-Diggity Technical Presentation (π€ Mic Drop Optional)
- How to Practice for a Lit π₯ Presentation
- What's in the πΌ Bag? Packing Tips for Technical π¦ Presentations
- It's Time β to Talk π£! The Day of Your Presentation
- After Your Talk π£: The Power πͺ of Leverage
This post originally appeared at The Many Flavors of Technical Presentations