Wednesday, July 1, 2009

Thoughts?

I am building up a 45min interview talk from my 12min conference talk that I gave several months ago. That 12min talk was exceedingly difficult to produce (how the fuck do you compress 4 years of work into 12min!?!?!), but I managed to pull it off and as you may recall, that talk went really friggin' well.

How did I do it? As simply as possible: I laid out the brief intro which centered around the question I was asking and why it was important, along with the hypothesis of course. Then I laid out the data in a logical order that allowed my audience to proceed from Point A (observation that led to the hypothesis) to Point B (conclusion) in as few steps as possible, making no logical leaps, with just enough extra to clarify a few points that required it.

I got a lot of compliments on this talk, including "your work is very elegant." I love elegant. I did not previously aspire to elegance - I thought it was perhaps too lofty a goal for a bumbling grad student. However, I am just delighted to know that some people think I have achieved it.

Now, in expanding this talk to 45min, I am faced with a dilemma regarding the elegance of my conference talk: how do I expand this talk and still retain it's elegance?

In some ways this is easy. The lab I am interviewing at works in a very different system from my own, so there is a LOT of extra introduction that I've put in so that everyone has enough information to understand the logical points of experimentation to follow. I've otherwise maintained the general format: Point A to Point B in as few simple steps as possible.

One suggestion I received after giving a practice talk was to include more data - the idea being that the potential post-doc PI will be impressed with how much stuff I can do/have done. I have more data (to be sure!), but I am not sure that throwing more data into the talk for the sake of impressing them with quantity is the best course of action. I feel like it will throw elegance out the window. I would rather impress with quality. I'm thinking that I'll include some more of my own data as illustrations/proofs of principle in order to flesh out my explanations of experimental procedures, rather than try to go off on too many tangents about "hey look what else I can do!" I don't want people to miss the point.

On the other hand, I do have some very flashy looking data that might fit into the second part of my talk which doesn't yet have elegant conclusions, but focuses on on-going work. While these data do not help the audience arrive at my conclusions elegantly, they do demonstrate that some of the technology I'm developing in my system is applicable to this lab's system. The technology in their system is not really new (it's use there prompted adaptation to my system), but not a lot of people are using it. I'm pretty sure that this lab doesn't currently use it - they haven't published any papers with it yet. However, it's a skill that I have in hand which has already been shown to be effective in their system. Do I show these data as a digression from my own system in my talk? Even though it doesn't add to my own conclusions? It's feels a little like showing off (ugh), but then that's a good thing in an interview right?

8 comments:

Mrs. CH said...

I think one of the most important things to do in an interview is to show what you can bring to the table if you worked there. Showing them you have already done (or are doing) things with equipment they have would definitely be beneficial. I would try to work it in somewhere.

Could you do your talk, but in 35-40 minutes? Then you could present "other things you do" in the last 5-10 minutes. I've seen that done, and it's nice because it gives a good overview of other things you've done, but you also give a complete talk on one project.

Arlenna said...

By all means do not cram in more data just to make it look like you work hard. That is the #1 talk mistake that grad students and postdoc interviewees make! Tell your friend that, too, so they do not make that mistake.

I agree with MCH, that if you can tell one story in about 30-40 min, and spend 10-15 min introducing one other interesting, pretty-looking story that shows you are well rounded would be much better than adding data for the sake of looking like you produce a lot of data.

Ambivalent Academic said...

Thanks to both of you for confirming my instincts. Instead of trying to cram more data in to make it look like I work really hard (I do!) at the expense of the quality of the presentation, I've split some of my data slides into two or more slides. They're not particularly data-dense to begin with, but being able to show larger representations of them helps both my explanation of the data, and makes the talk appear to have more of it without losing train of thought. I think this is a good compromise to the aforementioned "more data!" suggestion.

Re: "other things I do" segment. It doesn't have to be a separate segment - it actually ties in rather nicely with my pretty-looking story. The pretty-looking story has led us to a second question for which new technology is required if we're going to answer it. So the second part of my talk is about this technology development. Right now I've got a lot to talk about with this tech development project. I'm just wondering if I should stick to new-tech-in-my-system only, or to include a sidebar on new-tech-in-their-system as well.

Arlenna said...

Well, my own postdoc interview was not normal, so I can't go on that experience. But I can tell you that as a PI, if someone came and talked about what they did and put a little short tie in with how something they knew might be useful to us, we would think it was awesome!

scicurious said...

I would say that you shouldn't include more data unless it forms a good, complete story with the rest of your data. That's what a lot of people want to see in a presentation, proof that you're following logical steps to test hypotheses and come up with ways to form a complete story of your effect.

I always include a bunch of extra data "below the fold" at the bottom of my presentation. This helps a lot with questions, and gives you things to point to when you want to describe what else you do.

microbiologist xx said...

I agree, showing what you can bring to the table is a good idea. You want the lab to feel they are benefiting from you above and beyond the added pair of hands.
If your stories are related, I don't see any reason not to bring up the second story, even if you don't have a conclusion to it yet. Science is always ongoing and it can give you an opportunity to show how you think about a project that is "in progress."
I'd certainly stay away from just cramming stuff into the talk and from what you wrote, it seems like you are trying to avoid that. However, if the second story is significantly different from the main talk, it may be better to leave it out of the talk. You might get an opportunity to bring it up when you meet with the PI alone.

PhysioProf said...

AHAHAHAHAHAH! After I read your post, I was all like, "Now the Great Comrade PhysioProf will share his grand wisdom with you!" But you have already been given the answer: Keep your main talk elegant and streamlined, draw your conclusions, come to a close, and then be explicit about the fact that you are going to share some cool additional things that don't relate to the main talk.

The only thing I have to add is that you should state at the very beginning of your talk that this is what you plan to do, so that your audience doesn't feel all "thank fucking god this shit is over" at the end of the main talk, only to be forced to sit through another section.

Ambivalent Academic said...

Thanks folks - good advice all. I gave that talk today (will post more later) and if I do say so myself, I totally kicked some ass.