Yesterday I presented at the DMI Seattle conference and I bombed. As Scott wisely points out: “Everyone is polite and tells [speakers] they were great, even when they bombed.” You know when you bomb. [edit] In truth, it was not horrible, but it was not great either. I haven’t received any feedback so it is also hard to tell. My point is, if you feel it didn’t go well, no amount of reassurance will convince you otherwise. [/edit]
I was meant to give a talk sharing my story growing the UXD practice at Comcast for the past many years. I was excited to do this because I felt it could be useful to new managers and because it would help me be diligent about reflecting on that journey, which I wanted to do but had had difficulty committing to. Also, the timing was perfect. So what went wrong?
Bad choices all around
Things that contributed to the failed presentation:
* I was sick and feeling quite ill.
I contracted a powerful stomach bug from something iffy I ate the night before. Cold sweats and trembling do not inspire confidence in your audience. I had also been on a panel the prior day and had already set an expectation with the audience on what my delivery style and energy level were. I could not live up to my normal.
* I was intensely tired.
Because I was actively fighting the stomach bug all night long, I was unable to sleep and felt like my brain was in a haze. I was prepared and know the topic deeply, but I had a really difficult time recalling the order in which I had decided to expose the material and which specific points I wanted to make. The cues in my notes triggered nothing. It felt like having memory hiccups. Also, when I am excessively tired, English, my second language, doesn’t flow as well from my lips and I unknowingly omit words mid-sentence. I can’t hear it as it happens, but I know that must have happened.
* I took on unnecessary technical risks.
I prepared my presentation using OpenOffice and on my Dell Mini laptop. It was great for preparing but proved a poor choice when the projector refused to recognize my computer and the presentation would not display appropriately on PowerPoint on the computer I borrowed. All this happened 30 minutes before the presentation. I should not have experimented with non-standard technology since the visual aid was important, but not testing in advance in the final delivery space and setup is, always, a huge mistake (and I know better). Also, I did not have a plan B. Unnecessary anxiety piled on at the worst of times.
* I didn’t synthesize the story well.
This presentation did help me reflect on this journey as I wanted. I was able to gain perspective on the story in a way I had not seen it before. Unfortunately, I diverged too widely in analysis and ended up with less time to synthesize what I found into a cohesive story. I was sufficiently happy with where things were and it would still have been ok if the above factors had not added up, but they did, so the outcome was mediocre when contrasted with what I knew could have been done. Had I worked more on reducing it further to its essence, I could have managed the other issues better.
* Timing was disrupted.
Never allow external arbitrary inputs to break your planned delivery rhythm. Editing and being more concise in language on the fly are very doable, but only when you are feeling very comfortable in the flow of the presentation. I wasn’t comfortable, obviously, so when I was asked to wrap it up, I couldn’t figure out how and conclusion was completely derailed, which made the story seem like it did not have a real end.
I can’t have a do-over, so I’m going to re-craft this presentation and look for opportunities to give this talk elsewhere to see if I can tell the story I actually wanted to tell.