Research Is Not Homework
Chapter 0 Episode 1
Your entire academic life before stepping into research may look roughly like this: for every course you take, the instructor introduces a new topic every week, assigns a problem set as homework, you complete it by the deadline, and the cycle resets the following week. Whether or not the topic interests you, the syllabus was decided before the semester began, and the course structure carries you forward. More importantly, the answers to your homework questions are unchanging, and the instructor knows the correct answers to most, if not every, question a student might raise about the course material. Your only duty is to demonstrate that you have learned the material the way you are instructed.
If you are considering a research career, or have just started one, or simply want to try it out, the most important thing I want to share is that research breaks this familiar cycle. Recognizing how and why research differs from the conventional academic life is the first step toward the joy of research, because researchers who carry the “coursework” mental model into research can struggle and get lost in predictable ways.
Nobody Has the “Gold” Answer
In a typical course, the instructors know the answers to the problem sets before assigning them to you; otherwise, I don’t see a feasible way to assess your work quantitatively and objectively. Research works in the opposite way. The whole point of research is to investigate a question that nobody has solved, which means the entire community, including your advisor and me, does not have a definitive, gold answer. And if it turns out that someone has already solved your exact question, you are reinventing the wheel, and the novelty that makes the work worth doing is gone.
What does that mean in practice? It means you cannot hand your solution to your advisor and expect them to check it against a gold answer, nor does your advisor have the answer to “Is this right?” In fact, this question is often the wrong question to bring to research. The question that actually matters is whether your work is valid, for instance, whether your reasoning holds up, whether your method genuinely addresses the question you posed, and whether someone skeptical would be convinced. Validity is argued and defended, not verified against a solution sheet, and learning to distinguish between the two is one of the first real shifts you will make as a researcher.
As you continue to build up your knowledge and expertise in a specific research domain, you will gradually become one of a small number of people who deeply understand what has been accomplished and what remains open. Even for a single research project, the effort you have spent searching, identifying, and reading relevant literature will pay off in a way that shifts the dynamic between you and your advisor. Your advisor likely knows less about the fine-grained details of your research topic than you do. They may have read the same papers, but they did not invest comparable time and effort into your specific research question beyond the weekly project meeting.
What an experienced advisor can contribute to your project and to your personal development is a different kind of value. They bring familiarity with related work from adjacent or even distant fields that you may not have encountered, experiences (often learned through failures) about which research directions tend to be productive, and the capability to critique the rationales behind your plan from a reviewer’s perspective.
For prospective researchers with no prior research experience, this shift in mental model about research can feel disorienting and sometimes frustrating. You may find yourself asking for clear to-do tasks, only to realize they never come, or feeling anxious that you are doing it wrong because nobody has confirmed your direction. I want to reaffirm that the anxiety is very normal, and it fades rapidly as you develop confidence through active research engagement. I have seen many researchers who felt anxious at first but later found genuine enjoyment in independent exploration, precisely because they discovered the joy of investigating things that no one has explored before, and learned to treat the “failures” along the path as guidance rather than setbacks.
The Coursework Trap
The most common failure mode I see among new researchers follows directly from everything above, and I call it the coursework trap. A researcher in the coursework trap treats each project milestone as an assignment to complete under time constraints, optimizing for the minimum effort or the easiest path to meet the bar, and then waits for the next assignment. They do exactly what was asked or agreed upon in a project meeting, nothing more, and arrive at the next meeting expecting new orders.
The person closest to the problem, which is you, is the only one positioned to generate the next step, even if that step turns out to be wrong and needs revising. Therefore, when you wait passively for guidance on what to do next, the project simply stalls. And the longer you wait, the more stuck you feel.
More importantly, you are not in the middle of nowhere with nothing by your side. The knowledge you need is indeed out there waiting quietly, which includes papers published in top-tier venues in your area, classic works and theoretical foundations that shaped the field, and the studies relevant to your specific research question. In all my years of advising, no student has ever come to me and said, “Arthur, I have read every paper in my research domain.” And since that sentence is almost never true, its companion, “there is nothing I can do, so I will just wait for instructions,” is almost never true either. Whenever you feel stuck, the literature is the first place to go, and it will almost always hand you a thread to pull.
I will discuss much more in the coming posts about what genuinely motivates researchers to escape this trap, why the rewarding mechanism in research is so different from the one you grew up with, and how the habit of driving your own work compounds over time.