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

<p>Most new researchers do not fail because they cannot read. They fail because they read for six months and then discover that reading is not writing. A literature does not get smaller when you consume it. It becomes a room you are standing in, with walls you cannot see past.</p> <p>This guide assumes you are in the first six months of a project, or that you are restarting one after a break, a failed funding round, or two years away from it. You have a broad area, a supervisor, and a deadline somewhere in the distance. You probably do not have a research question yet. Most people do not, and pretending otherwise wastes months.</p> <h3>The first six months are for narrowing, not producing</h3> <p>The standard advice to spend a year reading is bad advice for anyone with a funding review, an annual review, or a supervisor who asks what you did this month. The first six months have one job: turn a broad area into a question small enough to answer in a year.</p> <p>Reading is not the job. Reading is the tool that does the narrowing. If you cannot tell what a given paper changed for you, you are not narrowing anything. That single test — what did this change — is what separates a research reading system from a pile of PDFs and guilt.</p> <blockquote><p>A reading list without a question is just a queue of guilt.</p></blockquote> <h3>Write down what you already believe</h3> <p>Before you open a single database, spend twenty minutes writing half a page about what you currently believe about the field. What is the central disagreement? What do your colleagues argue about at coffee? What is the finding that everybody mentions and nobody explains?</p> <p>This takes twenty minutes and it builds the most useful reading filter you will ever own. Once you hold a position, you can read for it, and reading for a position is roughly three times faster than reading in order to be informed.</p> <p>Keep the half-page. Put a date on it and paste it at the top of your notes. Read it again at week six and again at week twelve. The distance between what you believed in January and what you believe in June is your first research finding, even if you never publish it.</p> <h3>Three things to have at the end of month six</h3> <ul> <li><strong>A one-page scoping memo.</strong> The question in one sentence, why it matters in three sentences, and a paragraph on what already exists that you have checked.</li> <li><strong>A triage list of forty to sixty papers.</strong> Every paper you looked at, each with a one-line verdict: core, useful, background, or irrelevant.</li> <li><strong>A two-page proposal.</strong> The question, the method, the data, the timeline, and the two risks you think will kill it.</li> </ul> <p>Do them in that order. You cannot write a defensible proposal before you know what has already been tried, and you cannot triage before you have a question to triage against.</p> <h3>A six-month map</h3> <table><thead><tr> <th>Month</th><th>Focus</th><th>You should have</th><th>Hours per week</th> </tr></thead><tbody> <tr><td>1</td><td>Orientation</td><td>Half-page belief note, 25 triage papers, supervisor meeting 2</td><td>20</td></tr> <tr><td>2</td><td>Scope</td><td>Scoping memo, triage list at 60, three candidate questions</td><td>22</td></tr> <tr><td>3</td><td>Focus</td><td>One question chosen, 15 core papers read properly</td><td>25</td></tr> <tr><td>4</td><td>Method</td><td>Two-page proposal, data and method sources identified</td><td>25</td></tr> <tr><td>5</td><td>Evidence</td><td>Evidence ledger with 25 mapped claims, notes on one pilot dataset</td><td>28</td></tr> <tr><td>6</td><td>Write</td><td>Introduction draft, 1,200 words, supervisor meeting 8</td><td>30</td></tr> </tbody></table> <h3>A note on the projects that go wrong</h3> <p>Some projects will not have a question by month six, and that is a supervision problem rather than a personal failure. The signal is that your supervisor asks what you did, and you cannot answer in one sentence. If that happens three times in a row, book a longer meeting and bring your scoping memo and your triage list. Bring evidence of effort, not an apology.</p> <p>The other common wrong turn is a supervisor who has already decided the question and expects you to confirm it. That can be a good arrangement. It can also be a bad one. You will know which within the first two months, and the difference in your output over a year is enormous.</p>