How to Identify a Genuine Research Gap
A framework for testing whether what you've found is a real, defensible research gap — or just something you personally haven't come across yet.
Read GuideYou got your draft back. Somewhere in the comments — maybe the only comment on the whole methodology chapter — is some version of "this needs more work" or "improve your methodology." No further explanation. You reread the chapter and genuinely don't know what to change.
This is one of the most common pieces of feedback in thesis supervision, and one of the least specific. That's not necessarily your supervisor being unhelpful — there are real reasons this feedback tends to arrive vague.
Supervisors are often deliberately not prescriptive about how to fix a methodology chapter, because doing so risks crossing into doing the thinking for you — which raises real questions about whose work the thesis actually is. They're pointing at a symptom and expecting you to diagnose and treat the underlying cause yourself, partly because that diagnostic process is itself part of what a thesis is meant to demonstrate you can do.
The unhelpful part is that "improve your methodology" is shorthand for several genuinely different problems, and the fix is completely different depending on which one you actually have.
You've described what you did, but not why it was the right choice given your research questions. Every methodological decision — sample, method, analysis approach — needs an explicit line connecting it back to what you're trying to find out, not just a citation to a methods textbook.
Every method has weaknesses. A methodology chapter that presents its approach as flawless usually reads as naive rather than confident. Supervisors often mean: where's your honest account of what this approach can't tell you, and what you did to mitigate that?
A surprisingly common issue: the chapter claims one paradigm or method — say, a strictly qualitative, interpretivist approach — but the actual procedure described reads as something else, like structured, quantifiable coding. This mismatch undermines the whole chapter's credibility, even if each half is individually fine.
A methodology chapter isn't a lab manual. "First I did X, then Y, then Z" describes a procedure but doesn't make a case for why that procedure was the right one. The strongest methodology chapters read as an argument for the approach, with the steps as supporting detail, not the main event.
There's a difference between citing sources about your topic and citing sources about your method. If your reference list is full of the former and nearly empty of the latter, your methodological choices look asserted rather than grounded in the wider scholarly conversation about how to study things like this.
If the feedback genuinely doesn't tell you which of the five applies, don't guess — but also don't ask "what do you mean?", which puts all the diagnostic work back on your supervisor. Ask a specific, narrowing question instead:
"When you said the methodology needs improvement, is that more about how I've justified my choices, or about the limitations section, or something else?"
This kind of question is easy for a supervisor to answer quickly, because you've done the categorising work for them and they just need to confirm or redirect.
Share your methodology chapter and the feedback you received — we'll help you work out exactly what needs to change.
Run your methodology chapter through the self-audit above. For whichever item you can't confidently check off, that's very likely the specific thing your supervisor meant — draft a short paragraph addressing it before you touch anything else in the chapter.
Tell us what feedback you received and where you're unsure — we'll help you figure out exactly what to change and why.