Tag Archives: colleagues

The acknowledgement section of our NSF proposal

25 Aug

A few weeks ago two colleagues and I submitted an NSF proposal. We submitted on a Friday afternoon even though the deadline wasn’t until Tuesday! I am proud that we managed this almost without any deadline stress!

I had fun and we wrote a great proposal

I know that we may not end up getting funded by NSF, but until we get that message, I plan to be very optimistic. We wrote a really neat proposal for a great project. I can’t wait to get started! The ambitious goal of the project is to determine the fitness cost of every possible point mutation in the HIV genome in vivo.

I think nobody likes to write proposals when the success rate is only 5%, but I actually enjoyed working on this proposal and I learned a lot while writing it: both about the biology of our project and about the art of proposal writing. It’s important for me to commit that to paper (OK, screen) so that if NSF decides not to fund us, I will remember that writing the proposal was actually a good experience.

Writing with a newborn

In addition the many scientists and administrators who contributed to the proposal, I also want to mention how I could write a proposal with a newborn. We started working on the proposal two weeks before I gave birth and we submitted the proposal when our baby was just shy of seven weeks old. The hours that I spent on the proposal were made possible by my mom who flew in to help and by the fact that Facebook gives new parents four months paid paternity leave so that my husband was also at home during my maternity leave. It was fun to be home together with my husband and we took shifts working and taking care of Maya. Most days I worked on the proposal just two or three hours, so a large part of the work was done by others.


Me in my home office with baby, changing table, a laptop and a grant writing handbook.

It was a huge team effort

Many people were involved in writing the proposal. Many more than I ever expected to be. I want to list them here so that I remember who helped out and also to show that being a researcher doesn’t have to be a lonely affair.

Note that these people are only the people I am aware off. Others certainly helped my co-PI Adi Stern.

The main team that wrote the proposal consisted of four people:

  • co-PI Adi Stern (Tel Aviv)
  • postdoc Marion Hartl (SFSU)
  • professional grant writer Kristin Harper
  • myself

At SFSU, people from the Office for Research and Sponsored Programs helped:

  • Rowena Manalo
  • Raman Paul
  • Michael Scott
  • Jessica Mankus
  • Uschi Simonis (vice-dean for Research)

At Stanford there were

  • co-PI Bob Shafer
  • collaborator David Katzenstein
  • Elizabeth White (Katzenstein lab)
  • Holly Osborne (Office for Sponsored Research)

In Tel Aviv

  • Office for Sponsored Research
  • Adi Stern’s lab members brainstormed ideas
  • Maoz Gelbart help with ideas and figures

Colleagues who read earlier versions of the proposal

  • Sarah Cobey (U Chicago)
  • Sarah Cohen (SFSU)
  • Alison Feder (Stanford)
  • Nandita Garud (UCSF)
  • Arbel Harpak (Stanford)
  • Joachim Hermisson (U Vienna)
  • Claus Wilke (U Texas Austin)

A huge thank you to all these amazing people! I am lucky to be part of such a supportive community.


A better way to get feedback on a talk

4 May

A few weeks ago I had an important talk to prepare, and I wanted to get some feedback to make the talk as convincing as possible. So, as is usual in the lab where I work, I scheduled a practice talk a few days before the actual talk, but then I decided to do things slightly differently.

The usual way to get feedback:

1. Give a practice talk for the lab.

2. Ask people to give feedback directly after the talk. 

While this method is at least a hundred times better than not giving a practice talk at all, I thought it could be improved.

Here are some of the drawbacks of the current method:

1. The people in the lab are not necessarily in the best position to give feedback. For example, they may understand parts of my work that are difficult for another audience.

2. It takes too much time (for me and the others) if everybody needs to tell me their feedback.

3. I will probably not remember everything that the audience told me (except the general message that there is always a lot to improve).

4. Not everybody will actually state their opinion. Some people are too shy to speak up and a consensus may grow during the discussion, whereas I would like to know the variety of opinions.

So this is what I decided to do:

1. I scheduled a practice talk, as usual, but in stead of letting people tell me their opinion, I asked them to write it down. I explicitly asked them to write down what they liked about the talk as well as ideas on how to improve it.

2. I also screencasted a part of my talk with Quicktime (this records slides and my voice) and sent it to a collaborator in another city, so that she could make sure my presentation was correct on her part of the project. In principle, the screencast could be sent to a friend in another field to get the opinion of an outsider. 

How it worked

First of all, I discovered that after my practice talk, several people were eager to tell me their feedback directly. I asked them to write first, but then I also got oral feedback and this led to some interesting discussion about the content of my talk.

The written feedback from the practice talk was extremely useful. I read everything immediately after my talk. It hurt a bit. Just like honest feedback always does. I noticed that there were a few opinions in the written notes that I hadn’t heard in the seminar room. Two people wrote that they liked the first part of my talk, whereas the consensus in the room seemed to have been that this part wasn’t very good yet.

I put the notes away and worked on my talk for two more days (yes, it was an important talk!). Then, when I thought I was ready, I looked at the feedback again. Surprisingly, this time the reading was not painful at all! Now it was like reading a to-do list with only items that I had already done, interspersed with compliments.

I was happy that I had asked for the positive feedback, because it was motivating to read as I was sitting in my foreign hotel room, it got me excited about actually giving the talk. Rereading also helped to make sure that I hadn’t missed anything important (the axes were unlabeled on slide 15).

The video I sent to my collaborator in another city was also useful. It was easy to do (see link with explanation), it felt good to have my collaborator involved in the process, and she sent me an email with detailed feedback.

All in all, my conclusion is that it is very useful to get feedback in writing. It saved time, I got more opinions and I was able to reread it a few days later. In fact, I used the written feedback method for my students in Munich in the four years that I taught scientific presentations. I should have known that what was good for my students is good for me!