Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

To prepare for a presentation at Ignite Phoenix (which has its own particular set of rules) I used Screenflow to record myself speaking over the automated slide changes.

I wrote out my talk first, as an essay. I then read it and adjusted it based on how well it matched the automated slide changes and how easy/natural it was for me to say it.

I ended up with a video I could play over and over, listen to, and then recite from memory. I also printed my slides on index cards, along with some notes on what was supposed to be said for that slide, and had them with me since, as I it happened, when i gave my talk I needed some prompts.

I also practiced a lot. I hate it, but it helps, so there you go.

Ignite talks are a different sort of animal, where timing is very important (since you have no control over the slide change speed). But I found this approach of use for more casual presentations; it's still a good idea to have a good idea of how much time you will take and how well it all flows.

What I found was that you can start with something that would take 30 minutes to read to a crowd, edit out the cruft, the joke slides, and the amusing-but-unimportant factoids, and whittle you talk down to something punchy and concise.

Most talks are too long. Modulo topic and subject complexity I'd say they should be no more than 20 minutes.

Even if you're not doing an Ignite talk, plan as if you were and be mindful about how and why you make it longer. Don't give people an excuse to be checking Twitter or HN while you're speaking.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: