Reading Our Own Rejections Out Loud: The Lab Meeting Where Nobody Wins

A Ritual That Started With a Bad Study Section

Three years ago, our lab's flagship R01 resubmission came back with a score that made the principal investigator close her laptop and walk around the building twice. The obvious response would have been to absorb the criticism privately, sanitize it, and present the lab with a tidy plan for revision. Instead, she did something unusual: she brought the summary statement to lab meeting and read it aloud, word for word, including the sentence about the preliminary data being "unconvincing to the point of distraction."

The room was silent. Then a second-year undergraduate asked a question that changed how we operate: "Wait—you're allowed to show us that?"

That question became the foundation of what we now call the Rejection Reading, a quarterly meeting in which any lab member who has received negative feedback on a grant, manuscript, fellowship application, or abstract can share it with the group. Attendance is voluntary. Reading your own review is not required—anyone can volunteer a past rejection from their files. But the discussion afterward is mandatory for everyone present, because the point is not catharsis. It is instruction.

What Undergraduates Actually Think About Funding

Most students arrive at a research lab with a mental model of science shaped by textbooks and Nobel lectures: ideas are tested, good ones prevail, and careers advance accordingly. Nothing in that model prepares them for a study section summary statement, with its numbered critiques, its administrative notes, and its peculiar final line—an impact score that compresses months of work into a single integer on a nine-point scale.

When students see a real rejection for the first time, two things typically happen. First, they are startled by how specific and, often, how reasonable the criticism is. Reviewers are not villains; they are tired scientists reading at their kitchen tables, and their objections frequently identify genuine weaknesses. Second, students notice that the rejected grant was not garbage. It was a serious proposal by serious people that fell short in identifiable, fixable ways. That distinction—between rejection and worthlessness—is arguably the most important lesson a young scientist can learn before their first fellowship deadline.

We have watched students who barely spoke in meetings raise their hands to ask why the reviewers flagged the sample size, or what a "resubmission" means in practice. The document on the screen is no longer an abstraction. It is evidence that failure is a routine part of the job, delivered by people they know and respect.

The Rules We Set for Ourselves

The Rejection Reading works because of guardrails, not despite them. We follow a short list of conventions:

• No names of reviewers or study sections. Summary statements are shared as written, but identifying details stay out of the room and out of any notes.
• Critique the critique. After a review is read, the group spends ten minutes deciding which points are fair, which reflect reviewer error, and which are simply matters of taste. Learning to triage feedback is a skill in itself.
• No rescue narrations. The person sharing the review may not immediately explain how they fixed everything. The story of the successful resubmission, if there is one, comes later or not at all.
• Everyone contributes to the triage. The most junior person in the room speaks before the most senior one, without exception.

The last rule matters more than it sounds. In most lab meetings, hierarchy determines who talks first and whose interpretation sticks. Here, an undergraduate's reading of a reviewer's statistical objection carries the same weight as the PI's. Several of our best revisions have come from students who had no stake in defending the original application.

What We Have Learned From Our Own Failures

Across roughly a dozen sessions, patterns have emerged that no amount of private reflection would have surfaced. Manuscript rejections tend to hinge on framing rather than data—reviewers rejected what they thought the paper was about more often than what it actually said. Grant critiques cluster around feasibility language: applications that described what we hoped to do fared worse than those that described what we had already done and what came next. And fellowship applications from our own students were consistently dinged for the same reason—proposals written as if the reviewer already knew the literature.

None of these lessons appears in a methods section. All of them transfer. Students who sat through a Rejection Reading in their first semester have, in at least two cases we know of, cited the experience directly when writing their own successful applications years later.

Why We Think Other Labs Should Try It

There is a reasonable objection: isn't this performative vulnerability, a lab-culture trend that costs morale more than it builds? We considered it. What we found instead is that the ritual costs very little—ninety minutes a quarter—and pays off in a currency that is hard to acquire any other way: shared calibration. When a new rejection arrives, nobody in this lab wonders whether they are the only one. They have seen the evidence, read aloud, in a room full of colleagues.

Academic science already runs on failure. The choice is whether that failure is private, isolating, and mysterious, or whether it is examined in the open where the next generation can learn from it. We chose the second option. The laptop-closing walks around the building still happen, of course. But now, fewer of us take them alone.