Overcoming the Dissertation Wall: 5 Strategies to Write a High-Scoring Research Proposal
There is actually a sort of stuck that occurs just prior to dissertation writing. You've narrowed your research to a general area of interest, read a few papers and then nothing. The proposal just won't come together. Where you are now is the place that most post-graduates, at some point in their Post-graduation journey, come up against what most of them come to call “the dissertation wall” and as one of the most usual and frequent “walls” that people encounter before they have actually started writing their dissertation.
What's important to remember is that a research proposal isn't a mini dissertation. It's closer to a blueprint. It's all about making your committee feel good about asking your question, that no one else has thought of it, and that you can do it in the allotted time.
But whether you are working on an MBA project, a Master's thesis, or a final year undergraduate dissertation, the key is 5 things done well instead of 50 things done half done. Here are the tips for handling each.
What Committees Are Actually Looking For
Before diving into strategy, it helps to know what's being judged. Every proposal, regardless of discipline, gets evaluated against four questions:
- 1. What specific problem or phenomenon are you investigating?
- 2. Why does it matter, and what gap in the existing research does it fill?
- 3. How will you collect and analyse your data?
- 4. When will each stage of the project actually happen?
The key thing to understand: committees reward feasibility over ambition. A tightly scoped project that's clearly achievable will consistently outscore a broad, impressive-sounding idea that nobody — including the student proposing it, has fully thought through.
Define a Narrow, High-Impact Research Question
interesting but far too wide to actually research — and a broad topic makes data collection unmanageable and pushes the whole project toward vague, descriptive writing instead of real analysis.
A useful way to pressure-test your question is the SMART framework:
● Specific — one variable, one industry, one clearly defined group
● Measurable — you can actually gather empirical or qualitative evidence for it
● Achievable — the data, participants, or archives you need are realistically accessible
● Relevant — it connects to a live academic debate in your field, not a settled one
● Time-bound — it fits inside your semester or academic year, not a five-year research programme
Too broad
"The impact of digital marketing on business success."
Properly scoped
"Evaluating the impact of short-form video ads on consumer purchasing behaviour among UAE university students."
Notice what changed — not just the wording, but the amount of actual work implied. The second version has a defined population, a specific medium, and a measurable outcome. That's the difference a committee is looking for.
Use Your Literature Review to Find the Gap — Not Just Summarise It
A lot of students treat the literature review as a book report: here's what Author A said, here's what Author B said, repeat. That approach tells your committee you've read the field. It doesn't tell them you understand it, and it definitely doesn't tell them why your project needs to exist.
The literature review's real job is to expose the gap: the question nobody's properly answered, the population nobody's studied, the method nobody's tried. A simple way to structure this is the 3-C approach:
- Compare — where do existing studies agree? What's the established consensus?
- Contrast — where do they disagree, and why? Different methods, different samples, conflicting results?
- Critique — what's actually missing? Outdated data, narrow geography, a methodological weakness your study can address?
Once you can clearly name the gap, your research question almost writes itself — because it's now positioned as the answer to something specific, not just "more research on this topic."
Justify Your Methodology With Precision
This is the section evaluators read most carefully, because it's where they judge whether you can actually execute what you're proposing — not just whether the idea sounds good on paper.
Be explicit, not vague, about three things:
Research philosophy. Are you working within a positivist paradigm (testing hypotheses, numbers, statistical patterns) or an interpretivist one (understanding meaning, experience, context)? This choice shapes everything downstream, so name it clearly and justify why it fits your question.
Data collection. Spell out your sampling approach — random/probability sampling versus purposive sampling, for instance — and your actual collection tools: structured surveys, semi-structured interviews, secondary datasets, whatever applies. Vague phrases like "I will collect data from participants" don't hold up under scrutiny.
Data analysis. Name the specific tools or techniques you'll use — SPSS or R for quantitative statistical testing, NVivo or manual coding for thematic analysis on qualitative interviews. Committees want to see that you've thought past "collect data" to "here's what I'll actually do with it."
A quick note if referencing your own sources here still feels shaky: it's worth revisiting the fundamentals — see our Harvard referencing guide — since even a strong methodology section loses credibility if the citations backing it are inconsistent.
Build a Realistic Timeline
A brilliant question with an impossible timeline still gets rejected. Committees need to see, at a glance, that your project fits inside the time you've actually got. A simple week-by-week breakdown (or a Gantt chart, if your department expects one) does this job well:
|
Weeks |
Milestone |
|
1–3 |
Literature gathering and theoretical framework |
|
4–6 |
Survey design, pilot testing, ethics approval submission |
|
7–10 |
Primary data collection and field interviews |
|
11–13 |
Data coding, statistical analysis, draft writing |
|
14–16 |
Final proofreading, referencing check, submission prep |
Adjust the weeks to your own programme length, but keep the structure — it shows you've actually thought through sequencing, not just listed tasks in no particular order.
Eliminate Grammatical Errors and Formatting Inconsistencies
It's frustrating, but true: a genuinely strong research idea can still get sent back over avoidable presentation issues. A few things worth double-checking before submission:
- Keep the tone objective. Academic writing avoids informal language and unsupported subjective claims — stick to clear, critical, evidence-based phrasing.
- Audit every citation. Every source you've cited needs to actually appear in your reference list, formatted according to whatever style your university requires — Harvard, APA, OSCOLA, or otherwise. Mismatches here are one of the most common — and most easily fixed — reasons proposals get flagged.
- Get a second pair of eyes on it. A supervisor, peer, or experienced academic reader will often catch logic gaps you've stopped being able to see after reading your own draft for the twentieth time.
None of this reflects the quality of your research idea — but it absolutely affects how that idea is received.
Bringing It Together
A high-scoring proposal isn't the one with the most ambitious idea. It's the one that proves — clearly, specifically, and on paper — that you know exactly what you're investigating, why it matters, how you'll do it, and when each piece happens. Narrow your question, use your literature review to locate a real gap, be precise about your methodology, build a timeline your committee can actually believe, and give the whole document one last careful pass before it goes anywhere near a submission portal.
Get those five things right, and the dissertation wall stops being a wall. It's just the next step.
Need Expert Support With Your Dissertation Proposal?
Getting past this stage takes time, sharp critical thinking, and a fair amount of technical precision — and it's completely normal to want a second opinion before you submit.
At Writexa, our academic specialists work with Master's, MBA, and PhD candidates on exactly this stage of the process, including:
- Proposal structuring and review — sharpening your research question, methodology, and literature gap
- Statistical and software guidance — support with SPSS, NVivo, and quantitative modelling
- Thorough proofreading — making sure your proposal meets your university's formatting and referencing standards before it's submitted
Chat with Writexa on WhatsApp for guidance on getting your proposal approved on the first try.
References
Bryman, A. (2016) Social Research Methods. 5th edn. Oxford: Oxford University Press.
Creswell, J.W. and Creswell, J.D. (2018) Research Design: Qualitative, Quantitative, and Mixed Methods Approaches. 5th edn. Thousand Oaks: SAGE Publications.
Saunders, M., Lewis, P. and Thornhill, A. (2019) Research Methods for Business Students. 8th edn. Harlow: Pearson Education.
Sekaran, U. and Bougie, R. (2016) Research Methods for Business: A Skill Building Approach. 7th edn. Chichester: John Wiley & Sons.