Showing posts with label tenure-track. Show all posts
Showing posts with label tenure-track. Show all posts

Friday, May 07, 2010

The captain has turned on the fasten seatbelt sign

Buckle up folks, we're in for a rough ride...


Apparently the NIH is concerned funding rates are going to fall off a cliff in 2011. Jocelyn Kaiser has a news piece this week in Science.


Some "lowlights":

The 2-year grants will run out in 2011, and when that happens it could cause a nasty shock. Barring a new windfall—and none is in sight—NIH's budget will drop sharply next year. Much of the work recently begun will be left short of cash. The result could be the lowest grant funding rates in NIH history, and the academic job market will suddenly dry up—especially for young researchers.


Ummm, duh.


"This is the cliff that people are talking about, " Collins said. "We are going to face a crunch" in 2011, he said. The success rate, or portion of reviewed applications that receive funding, which hovered around 30% a few years ago and 20% this year, "will be more like 15%."


20% this year? Really?

The cliff problem was the focus of a meeting of economists, academic leaders, and NIH officials last week at Cold Spring Harbor Laboratory on Long Island in New York. Economist Paula Stephan of Georgia State University in Atlanta expects trouble as a glut of postdoctoral fellows and graduate students who were hired or kept on with ARRA money will hit the job market. "There is going to be a huge backlog of individuals looking for jobs and fellowships in 2011 and 2012, " predicts Stephan.
One suggestion: persuade Congress to fund one-time "bridge" fellowships to give ARRA-funded postdocs more time to find academic jobs or switch careers. "It wouldn't take a whole lot of money, " says meeting organizer Richard Freeman, a labor economist at Harvard University.

What academic jobs is he talking about? Basically Freeman's suggestion boils down to giving "bridge" funding to ARRA-funded postdocs so they have time to bail out...
Harvard microbiologist and American Society for Microbiology President Roberto Kolter, who spoke at Cold Spring Harbor, says "there's a wait-and-see attitude right now" in his department, which didn't apply for much ARRA money. He and many of his colleagues won't need to renew their grants for 2 or 3 years. But then, he expects, "there will be some casualties."

Ain't that the truth...

Wednesday, May 05, 2010

Building bridges

Based on the comments to my previous post, albeit a small sample size, there does seem to be support for requiring recipients of, or applicants for, bridge funding to demonstrate their worthiness. While I have the attention of a larger than normal audience (thanks to DrugMonkey), let me ask how bridge funding is handled in your department. Do you have set criteria/expectations, or is it handed out seemingly arbitrarily? If there are criteria, what are they?

Thursday, February 18, 2010

Calling all chemistry types

Apparently the NSF Division of Chemistry is having trouble finding enough qualified reviewers. This would be a great opportunity for any chemistry types on the tenure-track out there. There is nothing like reviewing proposals to teach you how not to write one.

Friday, February 05, 2010

End of an (old) era

This week I sent three of these off to surplus.




A 13-year old Unix workstation...
Kind of cute really.


I had bought them out of my start up funds when I first started here. I hadn't turned them on for at least five years. I felt kind of sad getting rid of them.

Thursday, January 21, 2010

Your science is not enough

There's an awful lot of good advice out there in the blogosphere on how to succeed at many aspects of academia. DrugMonkey and Writedit are great resources for grant-writing, Professor in Training and Prof-like Substance are chronicling the trials and tribulations of being tenure-track assistant profs in the biological sciences, DrDrA is transitioning to the next level, and FemaleScienceProfessor provides a great deal of useful information from the senior level, etc. One thing that I have not seen discussed very much is something I have a problem with...

Assertiveness.

Some grad students and postdocs might be surprised to hear that once you reach the giddy heights of an academic position your kickass science is no longer sufficient. It's what will get you that position, but it's not enough to progress in your field from there. Yes, you can obtain grants and publish based solely on the science, but it's not enough. It's necessary, and importantly, you need some kickass science first and foremost. But kickass science alone probably won't get you invited to speak at a meeting or another institution. It won't set up the collaborations with the heavy hitters and rising stars in your field. Kickass science might make you a familiar name in your field, but not necessarily a presence in the field. It won't necessarily get you the recognition you think you're due.

That's where assertiveness comes in. Want to know how many speakers at meetings (other than the heavy hitters) get those slots? They asked. They pushed themselves forward, told the organizers "I have kickass science, I can give a kickass presentation and I deserve a slot". Ditto for many of those people giving seminars at your institution. Ditto for a collaboration between a heavy hitter and a junior person. Ditto for invitations to submit manuscripts for special issues of journals. Ditto for some publications in GlamourMagz. It goes on all the time. Next time you find yourself thinking "How the hell did they get that invitation/collaboration?", remind yourself they probably asked. Pushed. Lobbied. It's something I'm not terribly good at, but I'm trying to improve (damn it, I'm good enough, I deserve that recognition!).

People are surprisingly often willing to give someone a chance. But just one. You need to deliver. If you promise a kickass presentation of kickass science you had better deliver. Offered a killer collaboration? Deliver it. Pushed for an invitation to submit a stellar manuscript? Make it better than stellar. Otherwise those doors will be slammed shut. Too many doors slammed on you will get you a reputation that's hard to get rid of.

Something to think about and work on.

Just remember though, you have to have the kickass science first.

Thursday, December 17, 2009

An update to "You lost WHAT?!?!?"

An update to a recent post...

Those of you with access to Science might be interested in reading this. I'm afraid it's too long to reproduce here... The whole sorry affair apparently has involved attempted extortion, harassment, a suicide threat and someone failing to make tenure. Science may not be a care bears tea party, but apparently it can be good soap opera material.

Friday, October 30, 2009

What's your h-index?

Actually I don't really want to know. Listing h-indices here would be akin to having a pissing contest. Puerile, messy and smelly...

In recent years I've noticed an increase in the number of people who list the number of times their publications have been cited in their c.v.'s and/or biosketches.* Many have started listing their h-indices as well. At first I viewed this as a form of bragging. But now I've seen it enough that I'm beginning to pay attention. We could argue ad infinitum as to whether number of citations and/or h-indices are useful measures of a person's productivity and standing in their field.** That's akin to the interminable Mac vs. PC arguments*** and I'm really not interested in that kind of semi-religious "discussion". What I am interested in is people's opinions as to whether or not this is a reasonable practice. Do any of my readers list citation statistics in their c.v.'s or biosketches? What are your thoughts on this? Do your respective departments take such things into account come annual review time (which is now for many of us)?

I don't list citation statistics in my c.v./biosketch (but might do so in the future if it seems advantageous). And my department doesn't formally consider such things, although I suspect some of the senior faculty spend some time on ISI's Web of Knowledge prior to annual reviews figuring out the stats on the more junior faculty.

Finally, I wouldn't recommend grad students and junior postdocs listing such stats unless they have a really highly cited paper or two. I have seen senior postdocs applying for TT positions list their stats. In some cases it helps. In others, not so much. It's a good idea to poke around and see how you stack up versus your peers before making the decision.







* Yes, in biosketches in grant proposals. At least in NSF and private foundation proposals.
** Personally I find number of publications, average number of citations per publication, plus h-index the most informative combination, but recognize even that has flaws.
*** Mac.

Tuesday, October 13, 2009

NSF and too much funding

Prof-like Substance has posted a nice summary of the NSF's funding stats for 2008. In it he writes:

"One thing that I found very surprising was the number of grants per PI. In the fiscal years 2006-08, 83% of PIs had one grant! That left 13% with two grants, 3% with three and 1% with four or more. As someone who has three very different projects that they are trying to get funded and has been talking with a colleague about a fourth, I'm not sure what to make of those numbers. If nothing else, it concerns me that reviewers might balk at a proposal just based on the number of grants held by a PI. Now, I'm not thinking that everything I am submitting will eventually get funded in the next year, but if these projects weren't fundable in my opinion, I wouldn't be wasting my time. Perhaps people who have served on a couple of panels (*cough* Odyssey? *cough*) might shed some light on the perception of when someone has "too much" funding."

I was going to reply in the comments but quickly realized this warranted a post all of it's own. Note that this is all based on my own observations and a few pieces of anecdotal evidence. As far as I know the NSF does not have any written policies regarding this stuff.

There are two issues here: holding more than one NSF grant concurrently, and what amounts to "too much" funding.

Firstly, let me address the comment "...reviewers might balk at a proposal just based on the number of grants held by a PI." Based on my experience on a couple of panels, that's rarely the case. A panel member might point out that someone is well-funded, but it doesn't seem to effect the review or panel scores. I believe it's the Program Directors who take current funding levels into account when making decisions as to who to fund.

As far as holding two NSF grants concurrently goes, the NSF stats reflect what I have observed over time. I have rarely come across someone who is PI on more than one NSF research grant. In fact I can only think of two instances. I do know of people who are PI on an NSF research grant and on a second, or even third, other type of NSF grant (e.g. REU site, equipment grant etc.). I would be one of those. So it happens, but it's rare. What's a PI to do? Call your Program Director and talk to them. Feel them out about the possibility of getting two NSF grants funded. One thing I do know however, submitting two proposals at the same time to the same panel is not received terribly well by the panelists. Or Program Director. Spread out your submissions.

So what has led to 83% of NSF-funded PI's holding just the one NSF grant? I have come to believe it's a function of the NSF's working philosophy. The Program Directors appear to view each grant funded as an investment. They want to "buy low", maintain the investment over the long term, and reap large returns. A well-established, well-funded investigator might be a "safe" investment, but often does not (appear to) give the same return per dollar over the long term as a riskier, young investigator.* What does that mean in practice? A senior person with one or more NIH R01's and no track record of recent NSF funding is unlikely to land an NSF grant. A young investigator with little or no other funding is in the running. Someone who landed an NSF grant early on, and subsequently pulled in other major funding while maintaining the NSF grant, remains in the running (the Program Directors want to hold their investments long term - as long as they continue to perform well on average).

I don't know whether this is fair or not. I have certainly benefited from this system. Keep in mind that the NSF's budget is a small fraction of the NIH's, and that they fund all non-biomedical science, plus math and engineering. Giving out multiple NSF grants to one investigator, or one to someone who is otherwise well-funded, means someone deserving misses out.** On the other hand, a single NSF grant is rarely enough to run a truly productive group...

Once again, the above are conjecture based on my own observations, nothing more.





* I would dearly love to see a study done on productivity/dollar. Many people, including myself, complain that investigators holding four or more R01's are not as productive per dollar as those with just one or two, but it's all based on anecdotal evidence on non-rigorous analysis of one or two mega-funded investigators.

** A Program Director recently told me the BIO Directorate at the NSF currently has a funding rate of ~15%. Better than NIH at the moment, but still lousy. A lot of really good grants are going unfunded.

Monday, October 12, 2009

Megacool faculty position

A colleague brought my attention to a job listing at Purdue University in Indiana. They're looking for someone in Molecular Pharmacology.

My colleague describes the Department thusly:

"As monocultural as my department looks on paper, everyone here is really cool people, we have a great atmosphere and a very friendly, down-to-earth departmental community. People here TRULY COLLABORATE without fearing for their independence. I have been welcomed without hesitation into the group and feel very at home here, and our department head is really fantastic. In general people here are just straight-up folks. We have a formalized junior faculty mentorship program as well as an informal weekly lunch together that I have found totally invaluable to getting on my feet. Our tenure requirements are very rigorous, but everyone seems to be doing their best to help each other make it through (rather than trying to turf each other out). All in all, I think this is an excellent place to start a career and I couldn't be happier with my choice to join this department."

And just in case you think you're not quite a molecular pharmacologist, check out a recent post by Comrade Physioprof. Now go sell yourself.

Wednesday, February 25, 2009

Oh dear...

As of this moment, my blog is the top hit for Google searches using:

"how many papers needed for tenure"
"papers needed for tenure"
"papers for tenure"

and number two for:

"how many papers for tenure"

Not that I care that people find my blog that way (I get 4-5 hits a day from people using those searches - and might even get more now with this post). It's more concerning that there are that many people who think they can find the answer on the internet.

Oh, and for those who find this post using such a search, read this.

Thursday, January 22, 2009

How Many Papers for Tenure?

The title of this entry comes from a Google search a recent visitor to my blog used.

Good question.

I can't answer it.

The only people who can give you some kind of answer to this are senior faculty in your department (and possibly college), and yourself.

But you absolutely must know the answer very early in the tenure-track process. Preferably before you officially start your position. At the very latest six months in.

So how do you find out how many papers you need? You need to do two things:

1) Ask. Ask early and often. Ask the senior faculty in your department. If you've met some, ask senior faculty in related departments within your college (e.g. within medicine, or within arts and sciences). You may not get a straight answer. You may get several different answers. Hopefully you will get some kind of answer.

2) Look it up. Find out how many publications the last few people who made tenure in your department had. No one tenured in the last few years? Look up the publication totals of recently tenured people in related departments within your college.

Once you've done both of the above, take the largest of the answers you've found (they may not match up).

That's the absolute minimum number of publications you are aiming for.

Absolute minimum. You want more. You may need more.

The answer to the question "how many papers needed for tenure?" is not set in stone.


[UPDATE] Do apply some common sense to the above. Let's say your senior colleagues provide you with a consensus estimate of X publications, and the last three people to get tenure in your department had (X+1), (X+2), and (X+10) publications. Take (X+2) as your minimum goal.

Tuesday, January 20, 2009

Dear Future Applicant for Tenure and Promotion

Your time on the tenure track is thundering its way towards the big decision. Soon you are going to have to put together that thick wad of documents known as your tenure packet/dossier/file. All of the documents in that packet are important, but some are more important than others. None are more important than your curriculum vitae. This document, your c.v., is a summary of almost everything needed to evaluate you for tenure and promotion. The other documents just provide the details.

So, dear applicant, please take the time and spend the effort to make your c.v. a document that will help those evaluating you come to the right decision. Because we really do want to see you be promoted with tenure. (Unless of course one of us is an obnoxious dickwad.)

You can ease our task by making all the information we need easy to find and read. Put the important stuff up front, and leave out the truly unnecessary.

And please don't use your c.v. to demonstrate your artistic nature. Please. Don't.

Do have a neat, logically organized c.v. And spell check it. A sloppy, disorganized c.v. makes you look... well, sloppy and disorganized. Not really what I want in a colleague.

Here are some further thoughts on some (not all) of the basics:

Background/Training/Education
My personal preference is for this to be in reverse chronological order, going from your current position back to your undergraduate schooling. Leave out where you went to high school* - really, we don't give a rat's rear end. And those perfect SAT/GPA/GRE scores you're so proud of?* Not of any interest to us when it comes to tenure decision time.

Publications
Reverse chronological order please. That Journal of Biological Chemistry paper you published while in elementary school? Very impressive, but not going to count towards tenure. Put the papers you've generated as an independent PI first. Those are the only ones that count. And do us a favor. Make it very clear what papers came out of which positions - I personally like subheadings denoting "Papers arising from my postdoctoral work", "Papers arising from my graduate work" etc. It's important to include these because they establish your history. But they won't count towards tenure.

And those manuscripts on your postdoctoral work you published while on tenure track? Sorry, they don't count towards tenure. They belong in the "Papers arising from my postdoctoral work" group. No, really, they don't count. Ever.**

What about papers "in preparation"? Not going to count. Don't bother with them.

Okay, if you really, really must. One "in preparation". Two at the very most. They still won't count. Three or four "in preparation"? That's asking for trouble. Unless you've published a gazillion papers while on tenure track - but they still won't count. If you're a little short on published papers and list three or four "in preparation"?* You've just given me the impression you have trouble finishing things, even with the tenure guillotine hanging over your head.

Ten "in preparation"?* You're a delusional fool. Granted, I've met some tenured delusional fools, but to a person they hid their delusional foolishness until after they got tenure.

Funding
Start with current/active funding. That's the most important by far. Actually it's really all that counts. Then list pending. If you have a revised grant pending that got a good score the last time it was reviewed, give us the score. Expired/previous funding comes last. Within each subgroup, reverse chronological order please.

Awards
You won a trophy for badminton at high school? How nice. Doesn't count. Please just list the relevant stuff. Preferably in reverse chronological order.

Professional Society Membership
Listing this doesn't count for much, but not listing it looks... odd.* It suggests that you're not involved in your field outside of your own research program.

Internal Service
Please indicate what level each committee is. A Graduate Curriculum Committee at the University level is a very different beast to one at the Department level. President of your undergraduate chemistry club? Doesn't count.

External Service
You do have some, right? List the journals you reviewed manuscripts for and the agencies you reviewed proposals for. Editorial boards. Professional society activities. These are important. To get tenure and promotion you need to demonstrate that you have national standing. Recent national standing.



Bottom line: Put the stuff that counts up front. You do know what counts at your institution, right?






* Yes, I have seen this in a c.v. within a tenure packet.
** This topic deserves a post all of it's own.

Monday, December 08, 2008

So you want a piece of the NSF pie? Some thoughts.

Some random thoughts to wrap up this series.

As before, disclaimers here.

1) The review process-

The NSF review process is very different to that of the NIH. I gather the different Directorates, and even organizations within Directorates, have some leeway in deciding how the review process works. What I'm about to describe is the process my own proposals go through at the BIO Directorate. Your mileage may vary.

Review is basically a two-stage process. First your proposal is sent out to a bunch (at least two, sometimes up to six or seven) ad hoc reviewers, plus at least two members of the review panel. These reviewers send in their reviews via Fastlane. The second step is the review panel. The panel considers all of the reviews (as many as eight or even nine), discusses the proposal and assigns a rank (not a score). The Program Director then takes the rankings and figures out what she can fund.

So you get a bunch of reviews. This is good and bad. On the plus side, you can survive a mediocre review if all the others are stellar. You also get a lot of (hopefully) useful feedback. On the minus side, if one of the panel members who reviewed your grant really didn't like it, your odds of being funded are not great even if all the ad hoc reviewers loved your proposal. As with NIH study sections, you need an advocate on the review panel.


2) Proposal rankings-

As I noted above, reviewers don't score NSF proposals per se. They give them a ranking. The reviewers assign a rank of Excellent, Very Good, Good, Fair or Poor (from memory). The review panel takes those and assigns an aggregate rank of Outstanding, Highly Meritorious, Meritorious, or Non-Competitive. The last two categories won't be funded. Sadly, it is often the case that not all of the proposals ranked as Outstanding can be funded...


WARNING! WARNING! ANECDOTAL STUFF FOLLOWS!

Okay, the following stuff is purely anecdotal - you've been warned. I'm posting it because I've heard the same things from multiple people (n > 6), leading me to think there might just be a grain of truth in each of these...

3) NSF doesn't want young people to fail-

NSF Program Directors have a lot of say over who gets funded and who doesn't. Clearly they can't over-ride the reviewers to much or too many times otherwise they would have a very hard time finding people willing to review proposals. But they can nudge proposals over the funding line if they feel it's warranted. What I have heard from multiple people is that Program Directors will sometimes do this in order to fund an otherwise unfunded young investigator on the verge of their tenure decision. Of course said investigator needs to have been productive enough to warrant this.

This is not something I would bet any money on. Or my tenure. It's obviously best to not to have to rely upon the largesse of a Program Director.


4) Once you're in you're golden-

By that I mean once you're funded by the NSF, as long as you're productive, your Program Director will try to ensure you maintain the ability to be productive. I am by no means suggesting that the Program Director will fund your proposals over higher scoring proposals. Rather that if you're on the funding edge and it's a choice between you as a previously NSF-funded, productive PI and someone else, you will get the nod (remember - this is anecdotal stuff).

I have brought this up hesitantly because it sounds like a mechanism for maintaining the status quo. I would like to think that's not the intent, rather that it's more a matter of Program Directors being loyal to their productive charges. Can it have the side effect of maintaining the status quo? Yes. The someone else is likely a new investigator... Please note that a) THIS IS ANECDOTAL, b) this is somewhat at odds with the previous anecdotal point in this post, and c) I'm not defending this.

Friday, December 05, 2008

So you want a piece of the NSF pie? Broader Impacts.

As before, necessary disclaimers can be found here.

The dreaded Broader Impacts... This is the place many of the proposals I've reviewed have significant weaknesses. It used to be you could just pay lip service to these. Half a page max at the end of the proposal would be plenty. Not anymore. The NSF has instructed its reviewers to take these very seriously. And I can assure you the Program Officers take them very, very seriously. So when you write a proposal destined for the NSF, you need to take the broader impacts very seriously.

Let's start with why NSF requires broader impacts - understanding this can help formulate some for your proposal. It is important to understand that the NSF will not give you a grant just to do research. Read their mission statement:

To promote the progress of science; to advance the national health, prosperity and welfare; to secure the national defense (NSF Act of 1950).


Note that it's promote the progress of science. That's much more than just funding research. The NSF's mission includes science education and training, and dissemination of scientific knowledge to the broader population. That's where the broader impacts criteria come from.

So what are broader impacts? The place to start is with the NSF Grant Proposal Guide. Find the section on review criteria and specifically that part dealing with the broader impacts. As you will see these are split into two categories:

  • Integration of Research and Education
  • Integrating Diversity into NSF Programs, Projects, and Activities


Basically it comes down to how you're going to tie education and training into your research activities and how you're going to go about improving diversity within science. The NSF has kindly put together a crib sheet describing how you might address these. It can be downloaded via at www.nsf.gov/pubs/2002/nsf022/bicexamples.pdf (for some reason I can't get Blogger to publish this as a link...). These are just suggestions and nobody in their right mind would propose to tackle all of them. Pick and choose those that work for your circumstances. Be creative and come up with new ones.

Here are some of my thoughts on how to address the broader impacts.

Integration of research and education:

This is the easier of the two criteria to deal with. It's important to understand here that "education" includes training, teaching and dissemination.

Training- In your proposal you want to talk about how you're going to involve trainees in your research. Trainees can include undergrads, grad students and postdocs. You could just say they will be involved, but it's much better to provide specific examples of how they will be involved. For example, what pieces of your project would be suitable fodder for undergrad researchers? Some verbiage describing how your trainees will be trained can also help.

Involving undergrads (and possibly high school students) is a very good thing to do (at least in NSF's view). And can be very rewarding for the PI as well. If you can, write an undergrad or two into each budget year. And specifically state that you will actively encourage even more undergrads to join your lab and that you will apply for REU supplements to support them (read up on these - it's easy money and really looks good when you go to renew your NSF grant). And don't forget to tout all the great work you've done with undergrads in the past.

Teaching- You can keep this as simple as stating that you will integrate the results of your research into your teaching (about the minimum in terms of addressing this, and really all I do), through to getting involved in teaching at K-12 schools. Another possibility is to host high school science teachers over the summer. The NSF has a whole program devoted to funding this kind of thing.

Dissemination- It's a given that you're going to publish and present your data at meetings etc. The difference here is that you need to explicitly state that. And describe how your trainees are going to be disseminating as well. Don't forget to budget funds for these activities, including funds to send trainees to meetings. It's important to back these things up with a real commitment - money.

If you have other opportunities to disseminate the results of your research (e.g. you've been invited to write a review or book chapter), talk about those. The book I recently edited is broader impact/dissemination fodder I count tout. Are you depositing stuff in publically-accessible databases? That's more dissemination stuff.

Diversity:

You can address this separately from the above, or integrated within it. Either works.

What the NSF wants here is some description of how you are going to try to involve people from traditionally under-represented (in science) groups in your research program. I've always found this the most difficult to address. You want to write something that you actually have a chance to succeeding at. If you read the NSF Broader Impacts crib sheet (www.nsf.gov/pubs/2002/nsf022/bicexamples.pdf) you can get some reasonable ideas. Collaborations with PI's who are, or who work with under-represented people count. As do collaborations with faculty at four-year colleges. The ultimate is to have members of under-represented groups working in your lab.

If you have any kind of track record of doing any of this, tout it loudly and clearly.



One last word of advice. Addressing the broader impacts sufficiently is going to require valuable real estate in your 15 page proposal. I don't know how much would be considered too much, but I can tell you less than a page will likely doom your grant. In my last two NSF proposals (both renewals, one that was funded in 2004 and one that has just been recommended for funding) I used at about two pages (not counting the space used to describe the broader impact work done with the prior period of funding).

Monday, December 01, 2008

So you want a piece of the NSF pie? The NSF is NOT the NIH.

I've decided to put down some thoughts of mine regarding obtaining funding from the NSF. This will likely end up being a series of posts...

First, the necessary disclaimer: These are my opinions only, shaped by my experiences as an NSF-funded investigator (in a College of Medicine), a reviewer of NSF proposals, plus the experiences of some friends and collaborators. Your mileage will almost certainly vary.

Second, some background: I was awarded my first NSF grant in 2001. I renewed that in 2004 and have recently heard that my second renewal has been recommended for funding. I am also PI on an NSF REU Site grant. I have reviewed many NSF proposals, most from the BIO directorate and some from MPS, on an ad hoc basis. Finally, I sat on an NSF SBIR review panel for two years.


Now, let's get down to business here. If you're in the biological sciences, please repeat after me:

The NSF is NOT the NIH.



Keep repeating this until you are firmly convinced of the truth in that statement.

Now you would think that that's obvious, right? Apparently it isn't to about 25% of the applicants whose proposals I've reviewed for the BIO directorate...

Here are some, but not all, major differences:

1) Budget-

The projected FY 2009 NIH budget is $28.7 billion for R&D expenditures. The NSF? $4.5 billion for R&D. This is under the current Continuing Resolution. See the AAAS September R&D Update to see where I got these figures. These numbers have a very profound effect on many aspects of NSF funding versus NIH...


2) Mission-

The mission of the NIH is "science in pursuit of fundamental knowledge about the nature and behavior of living systems and the application of that knowledge to extend healthy life and reduce the burdens of illness and disability."

The mission of the NSF "includes support for all fields of fundamental science and engineering, except for medical sciences." [Emphasis mine.]

The NIH funds biomedical research. The NSF funds all of the other sciences. Including social. Plus engineering. And mathematics. And the NSF mission includes a strong science education component (which I believe accounts for the disparity between the $6 billion total budget of the NSF versus the $4.5 billion it spends on R&D).

So, don't go proposing to solve cancer, or heart disease, or Alzheimer's in your NSF proposal. If you do I can pretty much guarantee it won't be funded. Basic biological science is fine (otherwise I wouldn't be funded), so there is some overlap between the NSF and NIH. But you need to be careful about how you sell your basic science to the NSF. Can't figure out how to sell your science without referring to the medical benefits of the research? Don't bother applying to the NSF.


3) Scope-

The scope (budget and period of funding) of an NSF proposal is very different to that of an NIH R01. The NSF keeps some interesting funding statistics. If you're considering applying to the NSF, go find the data for the last year or two for the directorate and organization (within the directorate) you are most likely going to send your proposal to. Study those numbers. Not the funding rates. The mean award duration and median annual award size. Your proposal needs to be in the same ballpark as those numbers (unless you're applying to a special program with special budget instructions). Sure, you can ask for more time and/or money, but you'd better do a very, very good job of justifying why you need more.

Oh yeah, one other thing. Those median annual award sizes? That's total. Direct plus indirect costs.


4) Proposals-

Aside from the fact that an NSF proposal is limited to 15 pages versus the (current) 25 page limit at NIH, there are other differences. I'm not going to go into great detail here. I'll probably cover some of that stuff in later posts. The main thing is to go study the NSF review criteria. And take them seriously. Intellectual Merit pretty much refers to the quality of the science proposed (and of the proposer). That Broader Impact stuff? Not something the NIH puts much weight on. The NSF, on the other hand, is very serious about it. I'm going to write a post devoted purely to Broader Impacts since this is where I've seen many proposals fail. Particularly those form new investigators.


5) Effect on tenure-

This is aimed at those of you in a College of Medicine. I got tenure based on my NSF funding. Here that's considered sufficient to satisfy the funding part of the tenure equation (assuming you've done very well on all other parts of the equation). That is not the case in all medical schools. There are Deans of medical schools who consider NSF money second class at best and will not approve tenure for someone with only NSF funding. Be sure you know what the ground rules are at your institution.

Wednesday, November 12, 2008

A week in the life of Dr. Odyssey

My last post was on having undergraduates do research. In the comments JLK asked:

Why be a professor at an MRU if you're not going to do your own research?

A simple question with a rather complex answer (or answers). The short answer is stuff happens. Read on for the more detailed answer.

I suspect the vast majority of us start our tenure-track positions at MRU's (Major Research University) fully intending to literally do our own research. Stand side-by-side with our trainees at the bench sweating over our own experiments. That was certainly my intent.

For the first few years it can be like that. But over time things change. We obtain new and more responsibilities. Grant writing. Publishing. Teaching. Committees. Reviewing (both manuscripts and grant proposals).

As we become more successful and better known the list grows. Study sections/review panels for grantmaking agencies. Traveling to give talks at other institutions. Meetings/conferences. Perhaps editorial duties at a journal. Service within scientific/professional societies. Even more grant writing. If you're lucky enough to gain "rockstar" professor status you can end up with even more of these responsibilities.

The time for actually doing our own research dwindles. I still manage to carve out some time to spend in the lab, but it's very limited. Instead we live vicariously through the efforts of the people in our groups. Instead of doing research we direct it. It's not that we don't want to do our own research. It's more that it's no longer in our job descriptions. By the time we hit mid-career (associate prof level - where I currently am) our job is to provide the environment, funding and intellectual background necessary for the research to occur.


Here is my week as an illustration (the current week, and just the weekdays). Note that my teaching load is very light compared to someone not in a College of Medicine.

Monday-
Morning: I got in late (mid-morning) after taking one of my daughters to the dentist... I am an officer in a subgroup within a scientific society. I spent over an hour Monday morning dealing with subgroup business. This was followed by time spent in the lab helping an undergrad debug an experiment. I updated my blog while eating lunch.
Afternoon: More subgroup business. Finished preparing an exam I was administering in a 2nd year graduate student-level class Tuesday morning. Spent an hour working on a manuscript. Spent an hour with a student asking questions regarding the exam. Attended a seminar given by a candidate for an open faculty position. Talked to my lab tech about the protein prep she was working on.

Tuesday-
Morning: Attended the chalk talk (future research presentation) given by faculty candidate. Proctored exam in grad-level class (we don't have TA's), met with the faculty candidate. Ate a sandwich before walking to other side of campus for...
Afternoon: Grad student committee meeting. Spent most of remainder of the day reviewing protocols submitted to the Institutional Biosafety Committee (IBC), of which I am a member. Talked to undergrad and lab tech about ongoing experiments.

Wednesday-
Morning: Continued work on manuscript. Planned out project for a new high school intern about to join the lab. Wrote this blog entry. Will walk to other side of campus for...
Afternoon: IBC meeting. This will probably take at least two hours. At least they feed us... Hope to work some more on manuscript. Check with lab tech on results of a gel. Meet with new high school intern.

Thursday-
Morning: Start reviewing student travel award proposals for scientific society. Teach in 2nd year grad student course. Continue reviewing travel award proposals (there are 36 to do). Talk with undergrads in the lab about their projects.
Afternoon: Maybe spend two hours in the lab doing some research! Hopefully also work with lab tech learning new technique. Review more travel award proposals. Attend student seminar.

Friday-
Morning: I try to spend Friday mornings working at home, mostly writing and reviewing. I'll try to get a manuscript review done and finish the travel award reviewing.
Afternoon: Meet with people in the lab. Attend weekly meeting held by a Center I'm part of. Get back to work on that manuscript.

Okay, so maybe I don't have 36 travel award proposals to review every week. I may have more manuscripts or grant proposals to review. Or other committee meetings. Or travel. And I haven't detailed any of the constant interruptions that occur during each day. You can see it's difficult to carve out big blocks of time to spend in the lab during the week.

Such is life.

I wouldn't trade it for anything.