How to write a problem statement

By Dr. Rafiq Muhammad, MD, PhD · Updated June 2026

The problem statement is the hook the whole proposal hangs on. In one to three paragraphs it has to convince a reviewer that there is a specific gap, that the gap matters, and that something bad follows if it’s left unaddressed. Get it right and the aims write themselves; get it vague and nothing downstream can save the proposal.

The gap-to-significance structure

A strong problem statement moves through four beats, narrowing as it goes:

1. Context. The broad area and why it’s important — one or two sentences, no more.
2. What’s known. What the literature has established — briefly, with citations.
3. The gap. The specific thing that is missing, unresolved, or contradictory — this is the core, and it must be evidenced, not asserted.
4. The consequence. What it costs to leave the gap open — for theory, practice, or a population. This is the significance.

A fill-in template

It’s deliberately plain. Reviewers don’t reward ornate problem statements; they reward ones where the gap is unmistakable and the stakes are clear.

Problem statement vs research question

They’re not the same. The problem statement describes the gap and its significance in prose; the research question is the focused, answerable question that targets it. The problem says why the study is needed; the question says what it will answer. The question should flow directly out of the problem — if it doesn’t, one of them is off.

The two most common mistakes

1. Describing a topic, not a problem. “AI in radiology” is a topic. A problem names what is missing or wrong within it. 2. Asserting a gap with no evidence. “No one has studied this” is a claim that needs the literature to back it up — reviewers check, and an unsupported gap reads as an unread field.