I spoke on the main stage of the March for Science in DC on April 22. Last week, I gave the text of my talk. This post talks about how I prepared for the talk. Tomorrow, I’ll have a post with more on the day of the march.
tl;dr for this post: it takes a whole lot of time to prepare a 2 minute talk. And, when talking to a crowd of tens of thousands of people, you need to leave time for applause; stick to the guideline of 150 words per minute, even if you think you speak faster than that.
When I first agreed to speak at the March for Science, I wasn’t sure what I wanted to use the time to talk about (and I didn’t initially know how long my slot would be). I was still in shock that I’d been asked in the first place! My first idea was to modify the opinion piece I’d just published about how costly it can be when we don’t have strong environmental protections. But I wasn’t sure if that was really what I wanted to talk about, especially because I knew that I also wanted to talk about issues related to diversity in science.
I agreed to give the talk a few minutes before heading off to my lab meeting. When I got to lab meeting, my student was talking about her data. The data weren’t new to me – we’ve been working intensively on a manuscript based on her research – but the juxtaposition of having just agreed to give this talk and her talking about her data ended up being really fortuitous. As I sat there, I realized that this was exactly what I needed to talk about. Talking about her project would let me talk about both the value of basic research and the importance of diversity in science. Those are both messages I really wanted to be able to get across, and I thought that this particular story would resonate.
After spending a day thinking it over and becoming more and more convinced that this was the right story to tell for the talk, I raised the idea with my student to see if she was comfortable with it. She was (though preferred not to be named directly in the talk). As I walked home, I called my mother and tried to explain the march to her and to tell her what I was thinking of talking about. When I was trying to explain the latter, I said something like: “You know, I want to try to reach the people like dad who always ask ‘But how is this going to help people?’” As I said it, I realized that I should incorporate that into the talk.
As soon as I got home, I sat down and wrote out my ideas. I spent a bit of time working on it over the next few days (and checked in again with my student to make sure she was still okay with me telling the story), but then put it down for several days. I still kind of didn’t believe that they really would want me to speak and felt like maybe I should wait until they released the speaker list. (After a few emails from right around when I was asked and agreed to speak, there was a lull where I didn’t hear much.) But then at some point I realized I needed to get back to work on it, even though the speaker list still wasn’t out. It’s a good thing I didn’t wait until the speaker list was made public, since that didn’t happen until the day before the march!
I spent a week working on the content. I had a fortuitously timed lunch that ended up leading to really useful feedback. I got feedback from folks at Michigan News. I got feedback from folks at RELATE, a University of Michigan group that focuses on science communication.* I got feedback from friends and colleagues and lab members.
At one point, I was really frustrated with trying to figure out the structure. The second half of the talk (the part focused on diversity) hardly changed – the last paragraph is almost completely unchanged from the first notes I jotted down that first day. But everyone had ideas for what to add to the first half and how to order things. The problems were that I had a very tight time limit (meaning that I couldn’t add without cutting something else, but no one had suggestions on what to cut) and that the suggestions for how to order things were directly contradictory.
I knew I needed to move from working on the content of the talk to working on learning it, and had set myself a deadline of the Monday before the talk for getting the content worked out. So, the weekend before that, I created two versions of the talk, one of which had a punchier start (this is the one I ended up using) and one of which included more explanation at the start (explaining to the reader that I was going to talk about the value of basic research). After talking with two science communication experts and trying out both of the talks, I decided to go with the punchier version, which we thought was better for a general audience. I sent that in to the march folks on Monday morning.
At that point, I shifted to focusing on delivery of the talk. I knew I needed to practice a lot. I put my talk on index cards and started rehearsing. I went back over to the Michigan News studios, where the videographer recorded me giving the talk five times in a row.** As I walked over, I reread this piece (which I’d read when it first came out) about learning a TED talk and was glad to see that some of the strategies I was planning (especially listening to a recording of myself giving the talk and practicing while running) were ones that he felt had been effective.
Being recorded was really useful for several reasons, including:
- The videographer gave me some delivery suggestions that were really useful.
- Watching the video, I realized that I made a face at the end of each run that indicated how I thought it had gone. (Generally: not well.) From then on, I focused on having a neutral face at the end of the talk.
- After the videographer sent me the clips, I made an audio version of my favorite one and put that on my phone.
After that, I spent as much time practicing my talk as I could. My goal was to get to happy birthday level with the talk, but I also had a lot of other things I needed to work on that week. So, Monday afternoon, I let the kids play at the park after school, pulled out my index cards, and gave my talk to the flag pole. I then walked around the playground giving it over and over. At one point, a dad showed up with his kid. When I finished that run through the talk, I sheepishly explained that I had a big talk on Saturday and was practicing as much as I could. Fortunately, he acted like it was totally normal for someone to be standing at the park giving a talk about basic research to playground equipment.
Tuesday morning, I listened to my recording on my phone over and over and over again as I ran and started to try to say it along with it. That evening, I practiced my talk at the playground again. On Wednesday morning’s run, I practiced 15 second loops over and over and over while I was running. On Thursday morning’s run, I realized as I listened to it the first time that I knew it and spent the rest of the talk just giving it to myself without playing it. Over the course of the week, I also practiced my talk on my way to and from daycare, in the shower, while my husband was putting the big kids to bed, while playing red light green light with my four year old – basically, at any chance I could.
On Thursday morning, I practiced for someone from RELATE who gave me delivery tips, as well as tips for what to do at the rehearsal and on the day of. The tips for what to do the day of ended up being especially useful. (More on that tomorrow!)
Thursday afternoon, just before heading off to a series of meetings that would take me right up until when I had to go to daycare, I got an email saying they wanted the talk to be 300 words. It was 435, so that represented a really big change. I had almost no work time left before my flight the following morning (given all the meetings and having no work time in evenings). I was worried about trying to change the talk at the last minute and having a trainwreck, given that I’d spent the past week getting the longer version of the talk down cold. And I was frustrated because the earlier emails had said a 2 minute limit, not a word limit. (One email from the previous weekend had indicated a guideline of 150 words per minute but, based on my practice, I was talking faster than that, so I thought my longer version would be fine.) I was also confused about why they were saying 300 words = two minutes, since my 435 word talk was about 2:20 when I tried it, speaking at a normal conversational pace, and I felt pretty sure I would go faster when I was on stage due to nerves.
When I woke up Friday morning, I decided to cut a couple of lines from my talk and send that in as a revised version. But I still was worried about whether changing it was a bad idea, given how much time I had spent memorizing it. And I really wished the 300 word limit had been made clear earlier.
On Friday afternoon, I got to the grounds at about 4, meaning that I had an hour to kill before my scheduled rehearsal time. I got my speaker badge
and then entered the mall to walk towards the stage. As I walked up, my jaw dropped a little as I realized how close the stage was to the Washington monument.
I killed time listening to what I thought was a band practicing a cover of She Blinded Me with Science. It turns out I was getting a private concert from Thomas Dolby without realizing it! At least I got some video.
We were delayed in starting practice (including because of lightning in the area, which meant we all had to shelter in a trailer until it was no longer within 8 miles), but finally I was in line on stage waiting to practice. One of the headliners, Lydia Villa-Komaroff, was in line right behind me. I asked how long she got for her talk, assuming the headliners got longer. She said 2 minutes — I’d been sure the headliners would get longer! As we talked more, she mentioned how long her talk was; I can’t remember the exact number, but it was something like 285 words. That made me worried that my talk really was too long.
When I got out on stage to practice, I was relieved to find that the teleprompter was really easy to read from. It was neat how it worked — there was a monitor on the floor with the talk and then a mirror up at eye level that reflected the talk. The thing to the right of my head in this image is one of the two mirrors/teleprompters:
The ease of reading off the teleprompter made me less concerned about further shortening my talk – as long as there was still time for them to edit things!
So, back at my hotel, I cut some more from my talk. And I’m really glad I did. Even with the additional cuts, it ended up being just over 2 minutes. What I hadn’t factored in is that applause takes up time. In hindsight, this seems obvious, but it somehow never occurred to me that people would applaud during the talk and that I’d have to pause for that! I’m not sure whether I’ll ever give a talk like this again, but, if I do, I will know to really stick to the guideline of 150 words per minute. And I will also know that, even with a really busy work and life schedule, by being creative, it’s still possible to work in time to learn a (short) talk to happy birthday level in the span of one week.
I’ll have one more post on my march for science experience, focusing on the day of the talk. That’s in the queue for tomorrow!