More proposals get rejected for a weak problem statement than for any other single reason. A statement that describes a topic rather than a problem reads as unfocused — and an unfocused problem statement makes every chapter that follows harder to defend.
| Component | What It Answers |
|---|---|
| The gap | What is genuinely unknown or unaddressed in the existing literature? |
| The population | Who specifically is affected by this gap? |
| The consequence | What happens — practically or theoretically — if the gap stays unaddressed? |
| The evidence | What citations show this gap actually exists, rather than being assumed? |
A statement missing any one of these four reads as incomplete to an experienced committee member, even if the writing itself is polished.
A useful structure: "While [what is known/established], little is known about [the specific gap], particularly for [population/context]. This matters because [consequence], and this study addresses it by [your approach]." Filling in every bracket with something specific — not generic — is most of the work.
Gap, population, and consequence, backed by literature — written to survive committee scrutiny.
Usually it means the population or context isn't specific enough, or the gap could be addressed by ten different studies rather than just yours. We narrow it until your specific study is the only reasonable answer to the statement as written.
Yes — an unsupported claim that something is unknown is an assumption, not evidence. We anchor each claim in your problem statement to literature you'll expand on in your review chapter.
This is common. Send us the specific committee feedback along with your draft, and we address exactly what was flagged rather than rewriting from a blank page.