Grant Writing: Lessons from the Trenches
Nobody's First Grant Is Pretty
I want to say something that every funded investigator knows but few say out loud: writing grants is brutal. It is one of the most time-consuming, ego-testing, rejection-heavy parts of an academic medicine career. And yet, for faculty on a research track, it is also non-negotiable.
Most of the physicians I coach have a similar story. They finished training, joined a department, inherited a vague expectation to "get funded," and received almost no structured guidance on how to actually do it. They read an NIH formatting guide, pulled up a template, and started writing — often in isolation, often under deadline pressure, and almost always from scratch.
There is a better way to approach this.
Start With the Science, Not the Application
This might sound obvious, but it is the most common mistake I see. Faculty sit down to write a grant and immediately open the SF-424 or the specific aims template. Before you touch any form, you need to be able to answer one question clearly: What is the problem, and why does your approach matter?
Robert Lefkowitz, the Nobel laureate, has talked about how the best science starts with a question that genuinely bothers you. Grant writing works the same way. If you cannot explain your central question in two or three sentences to a colleague outside your subspecialty, the application is going to struggle. Reviewers read dozens of proposals. Clarity is what cuts through.
Spend time on the idea before you spend time on the paperwork.
Specific Aims: The One Page That Carries Everything
If there is one piece of advice I could give every early-career physician writing a grant, it is this: spend a disproportionate amount of time on your Specific Aims page.
The Specific Aims page is the most read part of any NIH application. Many reviewers form their initial opinion of your proposal based on this single page alone. It needs to do several things at once: establish the problem, explain why current approaches fall short, introduce your solution, and outline what you plan to do — all in roughly one page.
David Bhatt's advice in his widely cited piece on writing a successful grant application in Circulation is worth reading carefully. He emphasizes that the aims page should function as a standalone argument. Someone should be able to read only that page and understand the significance, the innovation, and the approach.
Get feedback on your aims page from at least five people before you write the rest of the proposal. Not five people in your lab. Five people across different levels and disciplines. If they do not understand it, the study section will not either.
Significance Is Not the Same as Background
A section I see faculty struggle with is Significance. Many physicians treat it like a literature review. They summarize what is known. They cite fifty papers. They write three pages of background and then add a paragraph at the end that says, essentially, "and that is why this matters."
That is backward. Significance should lead with the gap. What do we not know? What is the consequence of not knowing it? Who is harmed by the status quo? Then bring in just enough literature to frame that gap convincingly.
Think of it this way: the background is the scaffolding. The gap is the building. Reviewers want to see the building.
Your Preliminary Data Is a Trust Exercise
Preliminary data is not about proving your hypothesis before you test it. It is about showing reviewers that you have the tools, the access, the expertise, and the feasibility to do what you are proposing.
For early-career faculty, this is often the hardest section. You may not have a lot of data yet. That is okay. What you need is enough to show three things: you can recruit or access the population you are studying, your methods work in your hands, and your team has the relevant expertise.
If you are light on preliminary data, be honest about it and compensate with a strong approach section and clear feasibility arguments. Reviewers can tell when someone is overselling thin data, and it erodes trust fast.
Resubmission Is Part of the Process
Here is a number that should make you feel better: the success rate for R01 applications at the NIH hovers around 20 to 25 percent, depending on the institute and the year. That means the majority of funded investigators were rejected at least once before they got their award.
Getting a scored but unfunded application is not a failure. It is a data point. The summary statement you receive from the study section is one of the most valuable documents you will ever get in your career. Read it carefully. Read it again a week later when the sting has worn off. Then build your resubmission strategy around the specific concerns raised.
The faculty I work with who ultimately get funded share a common trait: they treat the review process as a conversation, not a verdict. Each resubmission is a chance to address concerns, strengthen the approach, and show the reviewers you listened.
Build Your Grant Team Early
Writing a grant is not a solo sport, even though it often feels like one. The strongest applications I have seen come from faculty who assembled their team before they started writing — not after.
That means identifying co-investigators who complement your expertise, a biostatistician who can strengthen your analysis plan, a mentor or senior collaborator who has been funded and can review drafts, and ideally someone who has served on a study section and knows how proposals are evaluated from the inside.
If your institution has a grants office or a research development team, use them. They exist to help with budgets, formatting, compliance, and sometimes even editorial review. Too many faculty treat these offices as an afterthought. The ones who engage early write stronger proposals.
Protect Your Writing Time
Academic medicine is relentless with its demands on your calendar. Clinic, teaching, committees, email — all of it conspires against the deep, focused work that grant writing requires.
I coach faculty to block dedicated writing time weeks before a deadline and to treat those blocks as inviolable. Not "I will write if nothing comes up." Actually protected time. Close the door. Turn off email. Tell your team you are unavailable.
Robert Boice, whose research on academic writing productivity is foundational, found that faculty who wrote in brief, regular sessions were significantly more productive than those who tried to write in long marathon sessions close to a deadline. His book Professors as Writers remains one of the most practical resources on this topic. The lesson applies directly to grant writing: steady effort beats last-minute heroics every time.
The Grant Is a Story About the Future
At its core, a grant application is a narrative. It is a story about a problem that matters, a team that is equipped to address it, and a plan that is credible and well-designed. The mechanics matter — formatting, compliance, budget justification — but they are not what gets you funded. What gets you funded is a compelling, clear, well-supported argument for why this work should happen and why you are the right person to do it.
If you are preparing to write your first major grant, or if you have been through the process and want to sharpen your approach for a resubmission, I am happy to help you think it through. Faculty Coaching works with physicians in academic medicine on exactly these kinds of high-stakes career moments. Reach out any time.
