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

<p>Your supervisor is a resource with finite time and their own pressures. Almost all supervisor friction comes from one of two mistakes: turning up without a document, or bringing a topic instead of a decision.</p> <h3>Bring a document, not a topic</h3> <p>Every meeting should have a one-page document you send at least four hours in advance. It should contain the meeting's date and a three-line agenda, a progress list covering what you said you would do and whether you did it, a decision list showing what you need decided and your recommended option, a problem list giving a specific obstacle and the two options you have already considered, and a brief notes section with anything you want in writing rather than in memory.</p> <p>Send it by email, not a chat message. Email creates a record, allows them to think before replying, and can be read at 11pm on a Friday.</p> <table><thead><tr> <th>Meeting type</th><th>Length</th><th>Focus</th><th>Your output afterwards</th> </tr></thead><tbody> <tr><td>Regular, weekly</td><td>30 minutes</td><td>Decisions and blockers</td><td>A one-line summary you send before the next meeting</td></tr> <tr><td>Direction, monthly</td><td>60 minutes</td><td>Question, method, scope</td><td>Updated scoping memo</td></tr> <tr><td>Draft review</td><td>60 to 90 minutes</td><td>Specific sections, line by line</td><td>Written list of changes with deadlines</td></tr> <tr><td>Crisis, as needed</td><td>45 minutes</td><td>What is going wrong</td><td>An agreed recovery plan with dates</td></tr> </tbody></table> <h3>Decide what you need from each meeting</h3> <p>Before the meeting, write one sentence: what do I need to leave this meeting with? Sometimes it is a decision. Sometimes it is information only they have. Sometimes it is permission to stop pursuing something. Write that sentence at the top of your agenda. It converts a vague conversation into a transaction, and it stops the meeting ending with you both agreeing to think about it.</p> <h3>When you disagree</h3> <p>Disagreement with a supervisor is normal and often productive. The failure modes are avoidance and capitulation. Avoidance means you nod at a plan you know is wrong. Capitulation means you agree publicly and then quietly do something else.</p> <p>Both are worse than a clear disagreement, because both destroy trust in the one thing you need: their ability to advise you. The workable version is to bring evidence rather than doubt. Write two lines: what I think, and the specific evidence that made me think it. If they disagree and you are not persuaded, say so, and record what you will do. Follow it for a month, then bring new evidence.</p> <blockquote><p>Bring the disagreement on the page. An unrecorded disagreement becomes a grievance nobody can answer.</p></blockquote> <h3>Managing when they are unavailable</h3> <p>If your supervisor is away for two weeks or more, or for the first three months because of travel, illness, or a heavy teaching load, you need a second reader. Ask your department for a co-supervisor or a mentor. This is normal, not a complaint about the first supervisor. Say it as: I would like someone to read my first draft by the fifteenth, so that I get feedback while it still matters.</p> <p>You will also want a peer group. Three or four other early-career researchers who meet for one hour every second week to present work in progress is worth more than most writing groups and costs nothing. Set a rule: each meeting, one person presents and the others ask questions for twenty minutes.</p>