How-to · Step-by-step
Problem statement
A problem statement is a concise passage that defines the specific issue your research will address and explains why it is worth solving.
The step most authors miss
Doing CRediT right? Don’t stop at the statement.
A CRediT statement credits you inside one paper. The recognition CRediT was built for happens when those roles are tied to you, persistently. Sign in with your ORCID — free — and claim your CRediT contributions on casrai.org, the home of the standard. They become a verified, portable part of your identity, not a line that disappears into one PDF.
Free: claim your contributions, then export a journal-ready CRediT statement, schema.org structured data, JATS XML, CSV or BibTeX — and preview your public profile. A membership publishes that profile publicly and verifies the journals you serve.
Step by step
How to do it
1.Describe the ideal situation
Begin by establishing what should be happening — the goal, expectation or desired state in your field, practice or context. This gives the reader a benchmark against which the problem becomes visible.
2.Contrast the current reality
Set out, with evidence, how things actually are and where they fall short of the ideal. Grounding the gap in real findings or observations makes the problem concrete rather than assumed.
3.Pinpoint the gap
Name the specific problem — the discrepancy between the ideal and the reality — precisely and narrowly. A focused, researchable gap is far more useful than a sweeping concern that no single study could resolve.
4.Explain why it matters
State the consequences of leaving the problem unaddressed, and who is affected — researchers, practitioners, policymakers or the public. This relevance is what justifies the research.
5.State the aim
Close by stating what your research will do about the gap — its overall aim or purpose. This connects the problem directly to your study and leads naturally into your aims, objectives and research questions.
A worked example
A practical problem statement might read: "Effective handover of patients between hospital shifts is essential to safe care (the ideal). In practice, recent audits show that critical information is frequently lost during handover, contributing to avoidable errors (the reality and the gap). If unaddressed, this continues to put patient safety at risk and increases costs (why it matters). This study therefore aims to evaluate a structured handover protocol and its effect on information transfer (the aim)." Notice how each part builds on the last, moving from an agreed goal to a specific, evidenced gap and then to a clear research aim — without overclaiming or inventing figures it cannot support.
Common questions
FAQ
How long should a problem statement be?+
Short and focused — often a single paragraph, sometimes a little more for a larger project. Its job is to define the problem and its significance clearly, not to review the literature or describe methods. If it runs long, it is usually drifting into territory that belongs in the introduction or literature review; tighten it back to the gap and why it matters.
What is the difference between a problem statement and a research question?+
The problem statement describes the issue and why it matters; the research question turns that problem into something specific and answerable. The statement establishes the gap ("information is lost during handover"); the question asks how you will investigate it ("does a structured protocol improve information transfer?"). The question follows directly from, and is narrower than, the statement.
Should a problem statement include solutions?+
No — it defines the problem, not the answer. Proposing solutions belongs later, in your aims, methods or discussion. The statement’s purpose is to make a convincing case that a specific, researchable problem exists and is worth solving. Stating your aim at the end is fine; detailing how you will solve it is not part of the problem statement.
Going deeper
