How to write a problem statement in one move: name the gap between the ideal and the actual situation, prove both sides with evidence, and state the consequence of leaving the gap unstudied. Everything else — the background, the significance, the research questions — hangs off that spine. This guide gives you the four-part formula, example sentences you can adapt, and the tests your supervisor will silently apply before approving Chapter 1 of your FYP or thesis.
Step 1: Understand What the Problem Statement Must Do
The problem statement is the two-to-five paragraph argument in Chapter 1 that justifies your study’s existence. It is not the background (which sets context), not the significance (which sells the benefits), and not the research questions (which operationalise it). Its single job is to convince a sceptical reader that a specific, researchable gap exists and that ignoring it has costs. When supervisors write “problem not clear” on a draft, they almost never mean the sentences are ungrammatical — they mean the draft describes a topic, not a problem. “Social media use among students” is a topic. “Universities invest in e-learning platforms whose completion rates remain low, and the reasons are undocumented for Malaysian polytechnics” is a problem.
Step 2: Build the Four-Part Formula
Draft one paragraph (or one to two sentences each) for four moves, in order:
- The ideal: how things are supposed to work, anchored in policy, theory or best practice. “National digitalisation policy positions cashless payment adoption as a pillar of small-business competitiveness.”
- The reality: the documented situation that falls short. “Field observations and industry reports indicate that many micro-enterprises that register for e-wallet services stop using them within months.”
- The gap: what is not known — the research-shaped hole. “While adoption intention has been studied extensively, the post-adoption abandonment of cashless systems among Malaysian micro-enterprises remains largely unexamined.”
- The consequence: what it costs to leave the gap open. “Without evidence on why usage lapses, intervention programmes will continue to optimise sign-ups while the underlying attrition remains invisible.”
Read the four sentences together — they already form a miniature problem statement. Your full version expands each move with evidence, but the skeleton keeps you from drifting back into topic-description.
Step 3: Evidence Both Sides of the Gap
An unevidenced problem statement is an opinion. Two rules keep yours solid. First, the reality needs data: statistics from official sources, findings from prior studies, or documented observations from your preliminary work — each with a year and a citation. Second, the gap needs literature: you can only claim something is “largely unexamined” after a real search, and the claim should cite the closest existing studies while stating precisely what they did not cover. This is where the problem statement and your literature review lock together — the review’s synthesis produces the gap sentence, and the problem statement previews it. If your gap sentence cannot survive the question “how do you know nobody has studied this?”, return to your search log before your supervisor asks it.
Be precise with claim strength: “no study has examined X in Malaysia” is falsifiable by a single counterexample, while “X has received limited attention in the Malaysian context, with existing work focusing on Y” survives scrutiny and is usually more accurate.
Step 4: Scope the Problem Down to What You Can Study
First-draft problems are usually three sizes too big. “Why do SMEs fail?” is a research programme; a thesis needs one bounded slice: which failure factor, which population, which context, which timeframe. Scope by asking what you can actually access — data, respondents, timeframe — and let the answer trim the problem. A precisely scoped problem also writes your boundaries for you: the population, variables and context you name here become the delimitations section, and they must match what your methodology chapter later operationalises. A problem about “Malaysian university students” studied through one faculty’s respondents is a mismatch examiners catch instantly; name the population you will really reach — and if your instrument is a survey, check now that the population is one you can sample, as covered in designing a questionnaire for your FYP.
Step 5: End with Research Questions That Trace Back
Close the section by converting the gap into two to four research questions (and objectives, if your faculty separates them). The traceability rule: every question must point back to a sentence in the problem statement, and nothing in the problem statement should raise an issue no question addresses. A quick self-check that takes two minutes: put the problem statement and the questions side by side and draw arrows. Orphan questions (“interesting, but where did that come from?”) and orphan problems (“you raised this and never followed up”) are the two most common Chapter 1 corrections — and both are visible before your supervisor ever sees the draft.
Step 6: Run the Supervisor Tests
Before submitting, apply the three tests your reader will. The so-what test: read the consequence paragraph aloud; if the honest response is “so what?”, the stakes are too vague — name who is affected and what it costs them. The novelty test: could a reader believe this study already exists? If yes, your gap sentence needs the precision of Step 3. The solvability test: could data you can realistically collect actually address this problem? A perfect problem you cannot study is a worse Chapter 1 than a modest problem you can. Problems that pass all three tests get approved in one round far more often than beautifully written statements that fail one.
Common Mistakes That Trigger Rewrites
- Topic dressed as problem: paragraphs of context with no gap sentence anywhere. Fix by writing the four-move skeleton first.
- The missing ideal: jumping straight to complaints about reality; without the ideal, the reader cannot see why reality is a problem.
- Unevidenced drama: “many students struggle”, “companies are losing millions” — every quantifier needs a source or needs deleting.
- A gap your study does not fill: claiming a qualitative-understanding gap, then running a purely descriptive survey. The gap and the design must match.
- Solving instead of studying: promising to “improve” or “solve” the problem. Research produces understanding and evidence; implementation is a different deliverable — know which one your programme expects.
Chapter 1 approved in fewer rounds. Tesify helps you structure the problem statement, keep every claim attached to its citation, and carry the same framing consistently into your questions, scope and methodology — while the thesis stays 100% written by you. Used by 9,000+ students. Draft Chapter 1 in Tesify.
FAQ: Problem Statements
What is a problem statement in research?
A short, evidence-backed argument that a specific researchable gap exists between the ideal and the actual situation, and that the gap has consequences — leading directly to your research questions.
How long should a problem statement be?
Commonly two to five paragraphs within Chapter 1. Your faculty handbook may specify a range; sharpness matters more than length, and padding dilutes the problem.
What is the difference between a problem statement and background of study?
Background sets the wider context and narrows toward the issue; the problem statement is the pointed argument that a gap exists and matters. Background prepares the reader — the problem statement makes the claim.
How is it different from research questions?
The problem statement argues the gap; the questions operationalise it. Every question should trace to a problem-statement sentence, with no orphans on either side.
Do I need statistics in my problem statement?
You need evidence — statistics where they exist, prior findings or documented observations where they do not. Every empirical claim carries a source and year; unevidenced drama is the fastest route to a rewrite.
Can the problem come from my workplace or personal observation?
Yes — practical problems make strong studies — but the observation must be triangulated with literature or data to show it generalises beyond one office, and framed as a knowledge gap rather than a complaint.
Should the problem statement mention my solution?
No. Announcing a solution before studying the problem inverts the logic of research. State what is unknown; let the study produce the answers.
How specific should the population and context be?
As specific as what you can actually access. The population named here becomes your sampling frame in the methodology — mismatches between the two are among the most common examiner catches.
Can I revise the problem statement after data collection?
Refining wording and scope is normal as understanding deepens; replacing the problem after collecting data is not — it breaks the chain from problem to questions to instrument. Substantive pivots need your supervisor’s sign-off.
Is the problem statement the same for an FYP and a masters thesis?
The structure is identical; the expected contribution differs. An FYP may address an applied, local gap, while postgraduate work must position the gap against the scholarly field. Match the ambition to your level.
My supervisor says my problem is “too general” — what exactly do I change?
Add boundaries, not words: name the specific population, the specific variable or relationship, the specific context and timeframe. “Too general” almost always means the problem could still describe a hundred different studies; boundaries make it describe exactly one — yours.