The Researcher's Restart: A Systematic Reading and Writing Plan for New Researchers

<p>These are the ten failures that recur most often in the first year, in roughly the order I see them.</p> <ul> <li><strong>Reading without writing.</strong> You read 200 papers and can produce no argument. Fix: stop at pass one for anything that is not core, and write one sentence per paper. If you cannot write the sentence, you have not understood it and the paper needs a second pass.</li> <li><strong>The tool rabbit hole.</strong> You spend three weeks configuring Zotero collections or Obsidian plugins. Fix: write down the minimum setup, do it in one 90-minute session, and forbid yourself from changing it for six months. The tool is never the problem.</li> <li><strong>The topic too big.</strong> Your question covers a whole field. Fix: apply the scoping question test, and if it fails on bounded, pick one population, one region, one period, or one outcome.</li> <li><strong>Waiting for a perfect dataset.</strong> You are designing your study around data that might arrive. Fix: start with what you already have, write the limitation honestly, and treat the ideal dataset as the discussion's future work.</li> <li><strong>The supervisor avoidance spiral.</strong> You delay sending updates because you have not done enough. Fix: send the update anyway, honestly. A short honest update is worth more than a silence that hides a problem for six weeks.</li> <li><strong>Perfect prose, no argument.</strong> Your paragraphs are beautiful and say nothing new. Fix: write one claim per paragraph, and delete any paragraph where you cannot state the claim in a single sentence.</li> <li><strong>Ignoring the 80 percent.</strong> You spend all your time on three papers. Fix: triage ruthlessly and accept that most of your reading list will only ever be a citation, and possibly not even that.</li> <li><strong>Never asking anyone to read it.</strong> You write for months without showing a human. Fix: put a draft in front of a peer in week 6, not week 14. Every project that stalled late had a peer reading available earlier.</li> <li><strong>Treating a rejection as a verdict on you.</strong> Fix: re-read the reports, make the three lists, and act on the fixable list within two weeks.</li> <li><strong>Starting the methods too late.</strong> You cannot write the discussion without the results. Fix: reverse the order of work: method, analysis, results, literature, introduction, abstract.</li> </ul> <blockquote><p>The most common mistake is treating research as a series of big decisions. It is a series of small ones, taken weekly.</p></blockquote> <h3>Getting out of the worst one</h3> <p>If you read that list and recognised yourself in six items, do not change your topic. Change your system for two weeks: one triage session, two deep reading blocks, one writing block, one Friday consolidation, every week, no exceptions, and nothing else changed.</p> <p>Two weeks of that will do more than six months of thinking about it. Most stalled projects are not stalled because the question is wrong. They are stalled because nothing has moved for weeks and the researcher has started believing the project is the problem.</p>