How should I structure my first dissertation tutorial to maximize feedback on my methodology chapter?

Bring a one‑page summary that pairs each research question with the exact method you’ll use to answer it, and flag the two or three points you’re most unsure about. Hand that sheet to your supervisor before the meeting so they can skim it, then spend the tutorial walking through the summary, pausing at the flagged issues for detailed feedback. This lets you get a quick overall check that your methods line up with your questions, while also giving you focused time to troubleshoot the specific data‑collection hurdles you anticipate. For example, if you’re planning semi‑structured interviews but aren’t sure how many participants you need for saturation, note that as a “key concern” and ask the supervisor to critique your sampling plan. By combining a brief pre‑sent document with a targeted discussion, you maximise the supervisor’s time and walk away with concrete revisions you can implement right away. This approach ensures both breadth and depth of feedback in a single session.

You’ll get the most out of that first tutorial if you give your supervisor a quick, focused snapshot of where you are and where you need help, then use the meeting time to dig into the tricky bits. A good practice is to email a one‑page “cheat sheet” before the session: list each research question, the corresponding method you plan to use, and a short note on any assumptions you’re making (sample size, instrument design, access to participants, etc.). Highlight two or three items that you’re least confident about—those become the natural springboard for detailed feedback. When you walk into the tutorial, hand over the sheet (or have it open on your laptop) and spend the first few minutes walking your supervisor through it, pausing at the flagged concerns. That way they can see the big picture quickly and then focus their comments on the specific data‑collection challenges you’re wrestling with, like recruitment strategies, ethical approvals, or how to pilot your instrument. If you’ve already run a tiny pilot or have any preliminary results, bring those along too; concrete examples make it easier for your supervisor to spot gaps or suggest tweaks. By combining a brief pre‑read with a targeted, question‑driven discussion, you’ll turn the tutorial into a focused problem‑solving session rather than a vague overview, and you’ll walk away with clear, actionable steps to tighten your methodology. Good luck—you’ve got a solid plan, and this approach will help you fine‑tune it efficiently.