Deliver What You've Promised. How Hard Could It Be?
Chapter 3 Episode 2
If you ask me what characteristics I appreciate in my collaborators, I can tell you a lot. They reason rationally and think critically, they absorb information rapidly, their vision is thoughtful, and they always consider diverse perspectives comprehensively before making a decision. But if you ask me which characteristic I care about the most, the answer is simpler than you might think: they are always reliable.
It is hard to believe how rare such people are in the research community, and to make sure the argument I am conveying can be uniformly understood by everyone, I need to define “reliable” first. From my perspective, reliability has a few concrete components, and none of them are complicated.
What Makes a Person Reliable (And Vice Versa)?
The first is delivering what you committed to, on time and at the quality you promised. To clarify, I am not talking about “try not to miss the paper submission deadline,” because that is common sense and needs no repetition. What I mean by this lies in your day-to-day work. Research is almost always a team effort, meaning that you need to constantly communicate and coordinate with your teammates, delegate tasks, and sync up regularly. It also means that many activities are very likely interdependent, stacked on top of one another like tiles. If you cannot deliver something on time as promised, the team’s progress could be delayed. For example, if you said the figure drafts would be done by Thursday, everyone on your team is going to arrange their tasks around this timeline, so you should deliver the figures by Thursday, barring anything unexpected. Your word is your commitment.
That said, things can go wrong unexpectedly, and no reasonable collaborator expects perfection from their peers. For instance, experiments fail, code breaks, analyses take longer than expected, and sometimes life outside the lab demands much more of your attention than you would have anticipated.
None of these would damage your reliability if you communicate early when you cannot deliver, which is the second component of reliability. What damages trust is silence — when the time you promised passes and your collaborator hears nothing. Do not wait until the last minute to let your collaborators know you cannot make it. A very, very common example concerns the weekly project meeting. Understandably, things sometimes come up that prevent a student from hosting the meeting, but many students wait until midnight before the meeting to send a cancellation email, even when they could have done so much earlier. It may not sound significant, but it is an indicator of your work ethic and of how reliable a collaborator you are; and unsurprisingly, people prefer to work with someone who demonstrates a good work ethic. So next time, let your teammates know as soon as you realize there will be changes to your commitments. Give your collaborators the information they need to adjust, and propose a realistic new timeline.
The third component of reliability is about the quality of what you hand off, which directly extends the first episode of this chapter. To reiterate, this is not asking for perfection, because there is no perfection in research, and everyone knows that. Nevertheless, the difference between a draft you send the moment you finish typing, without any scrutiny, and a draft you read through and revise several times is not just about the quality of the content itself. From your collaborators’ perspective, if they can easily identify mistakes caused by carelessness, it tells them you do not value their time and effort, and perhaps the collaboration itself, because you did not bother to look for and address these mistakes before handing the deliverable to your teammates. At the same time, it indicates that you do not hold yourself to a high standard, and the consequences of that were clearly articulated in the previous episode.
Why Reliability Matters the Most?
As I mentioned before, reliable people do not constitute the majority, and to some extent, they are rare. Continuously adhering to your commitments and maintaining a high standard for everything you deliver requires significant effort and dedication, day after day, year after year. You will find many junior researchers energetic in the first couple of years of their careers, but many of them lose that enthusiasm over time, hampered by life outside the lab, or leave the community entirely as the years pass.
This also means that the core research community is small. Although the community has grown quite significantly in recent years because of the AI hype, the majority of the people who make up the community are PhD students, and most of them leave academia after graduation. You may meet many junior PhD students at conferences, and you will find that many of them do not return year after year. However, the small number of people you bump into at every conference will also be the ones who serve on program committees with you and potentially work alongside you for decades. Your reputation for reliability thus forms early and travels far.
More immediately, your reliability determines the kinds of opportunities that come to you. Advisors reach out first to the students they trust for the highest-stakes, most visible projects, because that work cannot afford unreliable contributors. Conference organizers invite the people who consistently deliver strong work. Grant collaborations favor those with a track record of completing what they commit to. Most importantly, none of this is formal or announced, and that is exactly what makes it powerful: the decisions happen quietly, and by the time you notice the pattern, it has been shaping your trajectory for years.
The commitment runs in both directions. You will also be the person waiting for a co-author’s draft, waiting for feedback from your advisor, or waiting for a labmate’s component that blocks your progress. When that happens, you will understand viscerally why reliability matters, and you will remember which collaborators communicated early and which ones went silent. Use that experience to hold yourself to the same standard you wish others would hold themselves to, because the frustration you feel when someone else misses a commitment is the same frustration you create when you miss yours.