Introduction | For first-year master's students choosing a thesis topic, the most painful part is not a lack of intelligence, but the information gap—the direction is unfamiliar, the literature is overwhelming, the gaps are hard to find, and the proposal report is hard to start. These four things are actually one chain. Once the chain is straightened out, proposal preparation can be compressed from a month to a few days.
1. The four difficulties of proposal development are actually one chain
If you list the difficulties first-year master's students face when choosing a topic, there are usually four: an unfamiliar direction (not knowing what the field is debating), massive literature (there is already a huge amount from the past five years alone), difficulty finding a gap (after looking through everything, you still don't know where the problem is), and not knowing how to start writing (you can't produce a structure for the proposal report).
They are not four independent problems. An unfamiliar direction leads to random reading, random reading leads to more chaos the more you search, and the more chaotic it gets, the harder it is to find a gap—so in the end, naturally, you can't start writing.
| Common bottlenecks in proposal development | Where it gets stuck | How to get past it |
| Unfamiliar direction | Not knowing what the field is debating | First gather top-journal papers from the past 5 years and see where the debate is |
| Massive literature | The more you search, the more chaotic it gets; you can't finish reading or let it go | Structure it into a literature library, then talk about what to keep and what to discard |
| Can't find a gap | Can't distinguish "no one has done it" from "it has been done but no one recognizes it" | Lay out existing work and see what positions remain |
| Don't know how to start writing | You have ideas but can't turn them into a document | First produce a framework and draft PPT, then revise step by step |
The four difficulties are one chain. Each time you fill one link in the chain, the pressure later on decreases a little.
2. Step one: gather top-journal literature from the past 5 years all at once
The first link in the chain is "being able to see clearly." When exploring on your own, this step usually requires repeatedly trying keywords and reading abstracts one by one. Two or three days pass, and you are still not sure whether you missed anything.
This step can be appropriately delegated to tools. MuchSci's "Paper Search" supports batch retrieval of top-journal literature in the field from the past 5 years, extracts each paper's research question, core method, and conclusions, and verifies citation sources. What it mainly saves is the time spent repeatedly trying keywords and reading abstracts one by one.
The result is a list you can use directly: what questions in the field are being repeatedly studied, who has answered each question and with what methods, and whether these citations are real and traceable. The first layer of the information gap—"I don't know what work exists"—is flattened somewhat in this way.
3. Step two: locate research gaps from the pile of literature
Once you have the list, a new problem immediately appears: with so much work, where is there still room?
"Paper Sailor" is suitable for taking on this step: quickly locating research gaps, building a domain literature library, and generating a draft literature review. These three things have different value at the proposal stage—
• Research gaps: directly answer the most critical question, "What can I do?"
• Domain literature library: store the retrieved literature in a structured way, ready to use later when writing the thesis;
• Draft literature review: the hardest part of the proposal report, the "state of research," at least no longer starts from a blank page here.
A gap is not invented; it is what remains after laying out existing work. This is also the fundamental reason it is more effective than "reading another hundred papers."
4. Step three: build the framework and turn it into a proposal report
Once you have a gap, you still need to explain "how to do it." The place where this step most easily gets stuck is: you have ideas in your head, but you can't turn them into a structured document.
"Personal Agent Assistant" is used to wrap things up: coordinate and organize the thesis framework—research questions, methodological route, innovation points, and schedule—and generate a draft proposal report PPT.
The output of this step is something that can be viewed and discussed: a framework and draft PPT that you can take to a group meeting or go over with your advisor. What first-year master's students need most for proposal development is exactly this kind of thing—it doesn't have to be perfect, but it must be discussable.
5. How the three stages connect
There is a clear order among the three stages: only with verifiable information can we talk about gaps; only with gaps can we talk about a framework.
If you skip the first step and look directly for gaps, it is easy to mistake "what others have done" for a gap. If you skip the second step and build a framework directly, it is easy to write a proposal report with no footing, and it often gets sent back at the mid-term review.
These three stages correspond respectively to MuchSci's Paper Search, Paper Sailor, and Personal Agent Assistant. Each handles one stage, linked end to end, and you do not need to reorganize the data in between—what is saved is the time spent moving information back and forth.
6. Three tasks, and who handles each
From "gathering literature" to "choosing a topic," each stage has clear outputs and also clear judgments left to you: after the list comes out, judge relevance; after gap clues come out, judge whether they are worth doing; after the framework comes out, judge whether it fits your advisor's direction and project conditions.
Tools are responsible for flattening the information gap; judgment is left to you. The hardest part of first-year proposal development is not not knowing, but that no one has organized "what is already known."
7. Which steps cannot be skipped
After the information gap is flattened, proposal development enters its real part. There are four things you still have to do yourself:
1. Judge whether a gap is worth doing—whether no one has done it, or whether it has been done but no one recognizes it; the difference between the two is huge;
2. Align with your advisor and project conditions—no matter how good the topic is, if it can't be done, it doesn't hold;
3. Recheck citations and data—the sources have already been checked, but the final signer is you;
4. Clearly state where the contribution lies—the core of the proposal report is not workload, but "why this question is worth answering."
8. Three days, from information gap to discussable material
Exploring on your own, digging through literature, and trying directions, four weeks or more is normal; following the three stages—gathering literature, finding gaps, building a framework—you can produce a discussable document in about three days.
What is saved is not reading volume, but the time to turn "knowing what" into "being able to judge what." For first-year master's students, the earlier this information gap is closed, the easier the next two years will be: you spend time on judgment, not on searching for materials.
Proposal development is essentially answering one question: in this field, is there something worth spending two years of your life on? No matter how complete the materials you find are, they cannot answer it for you; they can make the question a little clearer—but the answer is always in your own hands.