Problem Statement Development: Evidence, Context and Researchable Need

Reader outcome

By the end of this guide, you should be able to turn a broad research concern into a problem statement that is specific enough to investigate and cautious enough to defend. The aim is not to make the problem sound dramatic. The aim is to show, with evidence, what is happening, what scholarship currently explains, what remains unresolved, and why a focused study is a reasonable next step.

A strong problem statement should also make the next parts of a proposal easier to evaluate. A reader should be able to see why the research question follows from the problem, why the proposed evidence is relevant, and whether the project appears feasible.

What a problem statement is, and what it is not

A research problem statement is a reasoned account of an issue that merits investigation. It normally combines three kinds of information:

1. the context in which the issue exists;
2. the current evidence or scholarly understanding of that issue;
3. the specific unresolved need that the proposed research will address.

This is different from a topic. “Student wellbeing” is a topic. “International postgraduate students experience challenges” is a broad concern. Neither tells a reviewer exactly what is unresolved, where the issue occurs, what evidence supports it, or what a feasible study could investigate.

A problem statement is also not the same thing as the purpose statement. The problem explains why investigation is warranted. The purpose explains what the study intends to do. The research question then converts that purpose into something that can be investigated through a defensible design.

A useful logic chain is:

Context and evidence → unresolved issue → researchable need → research question → feasible design

If one link is missing, the proposal can become difficult to assess. For example, a research question may sound interesting but still be detached from the evidence used to justify it.

Separate the practical problem from the scholarly gap

One of the most common reasoning errors is to treat a practical problem and a literature gap as if they were interchangeable.

A practical problem exists in a real setting. It may concern a process, population, policy, service, organization, technology, behaviour, decision, or outcome. Evidence for it might come from current administrative data, official statistics, institutional reports, policy documents, stakeholder records, or other credible primary material.

A scholarly gap concerns the state of academic knowledge. It might involve an underexplored population, an unresolved theoretical relationship, inconsistent findings, a methodological limitation, a missing context, or an unanswered question. Evidence for that claim must come from a topic-specific review of relevant scholarship.

The two can be connected, but the connection needs to be shown rather than assumed.

This separation prevents a persuasive writing style from replacing research logic.

Use literature to establish what is already known

The University of Washington Graduate School describes a literature review as a foundation and frame for a thesis or dissertation and emphasizes coherent synthesis rather than a source inventory. That distinction is central to problem-statement development.

A weak literature section often follows this pattern:

Study A found X. Study B found Y. Study C discussed Z. Therefore, there is a research gap.

The conclusion does not logically follow merely because several studies have been summarized.

A stronger approach asks what the literature collectively establishes. For example:

• What is consistently known?
• Where do findings disagree?
• Which populations, settings or mechanisms have been examined?
• Which explanations or theoretical relationships remain uncertain?
• What methodological constraints affect the conclusions?
• Does the literature itself identify unresolved questions?

Only after this synthesis should you decide whether a scholarly gap can be defended.

Generic proposal guidance cannot establish that your field contains a gap. It can tell you that the literature should position the research question. The actual gap still has to emerge from your topic-specific evidence search.

Build an evidence chain before writing the polished paragraph

Instead of beginning with a dramatic opening sentence, build the reasoning first. A simple evidence chain can prevent many unsupported claims.

1. Define the context

State where the issue exists and what part of that setting matters for the proposed study.

Depending on the discipline, relevant scope may include:

• country, region or institution;
• industry, organization or policy setting;
• population or participant group;
• case, dataset, text, archive, system or material;
• time period;
• theoretical or disciplinary boundary.

Not every project needs all of these dimensions. The goal is to make the problem specific enough that a reader can understand what is inside and outside the study.

2. Establish the substantive issue

Use current evidence to show what is happening in the selected context. If you use a statistic, record its date, source, population and definition. A number can become misleading when it is detached from the period or measurement it actually represents.

Do not keep an old statistic merely because it sounds persuasive. If the substantive problem depends on a changing condition, re-verify the evidence before publication or submission.

3. Synthesize current scholarship

Explain what the relevant literature already tells us. Focus on patterns, relationships, explanations, areas of agreement and areas of uncertainty.

The purpose is to establish the intellectual starting point for the study. A reviewer should not have to infer what is already known from a list of article summaries.

4. Identify the unresolved issue

Now state precisely what remains unresolved.

Useful unresolved issues can include:

• a relationship that has produced inconsistent findings;
• a mechanism that is not well explained;
• a population or context for which existing conclusions may not transfer;
• a methodological limitation that restricts current evidence;
• a theoretical question that remains unsettled;
• a practical need that scholarship does not yet adequately address.

Avoid phrases such as “no research exists” unless you have evidence strong enough to support that absolute statement. Usually, a narrower statement is more defensible, such as identifying a specific limitation in the available evidence.

5. Define the researchable need

A problem becomes researchable when the unresolved issue can be translated into a manageable inquiry.

University of Sussex and King’s College London proposal guidance both connect the research question with current scholarship, evidence or data needs, methodology and feasibility. Although their local application requirements should not be treated as universal templates, the underlying alignment principle is useful: the proposed inquiry should be capable of generating evidence that actually addresses the stated problem.

Ask:

• Can the required data, participants, texts, cases or materials realistically be accessed?
• Can an appropriate method answer the question?
• Is the population or setting defined clearly enough?
• Can the work be completed within the available time and resources?
• Are foreseeable ethics, access or governance issues manageable?

A problem may be important but still be too broad or inaccessible for the proposed project.

Keep significance specific

“This topic is important” is not a sufficient justification.

State what kind of significance you mean. Depending on the project, this may be:

• scholarly significance, because the research addresses a clearly evidenced limitation in current knowledge;
• practical significance, because the findings could inform a defined professional or organizational problem;
• policy significance, because the study examines evidence relevant to a specific decision or implementation challenge;
• theoretical significance, because the study tests, extends, compares or clarifies an explanatory framework;
• methodological significance, because the study addresses a limitation in how a phenomenon has been investigated.

Do not promise that the study will “solve” a problem unless the design can genuinely support that claim. Most thesis projects make a bounded contribution rather than resolving an entire field-level or social problem.

A practical problem-statement planning matrix

Before writing prose, complete a small matrix like this:

If one row is empty, that is usually a sign that the polished problem statement is being written too early.

A hypothetical example

Consider this deliberately weak statement:

International students face many difficulties at university. Their academic performance is important, and there is not enough research on their problems. Therefore, this study will investigate international students.

Several problems are hidden inside this paragraph. “International students” is an enormous population. “Many difficulties” is undefined. No country, institution, programme or time period is specified. No evidence establishes the practical problem. The phrase “not enough research” is an unsupported gap claim. The proposed study also has no clear research question or feasible evidence plan.

A stronger reasoning process would begin by narrowing the setting. Suppose the intended project concerns supervisor communication among international master’s students within one programme or institution. The researcher would then need to establish, from appropriate current evidence, whether a substantive communication problem exists in that context. Separately, the researcher would synthesize relevant scholarship on supervision and international postgraduate experience.

If that evidence reveals a defensible unresolved issue, the problem statement could then explain the specific context, what prior scholarship establishes, what remains insufficiently understood, and why a focused study of that population could add useful evidence.

Notice what has not happened: the research gap was not announced before the literature was examined. The evidence determines the problem framing, not the other way around.

Turn the reasoning into a paragraph sequence

There is no universal problem-statement template. Disciplines, programmes and supervisors may expect different structures. However, the following sequence is often useful as a drafting check.

Paragraph 1: establish the context

Introduce the specific setting and substantive issue. Use evidence rather than broad claims about importance.

Paragraph 2: position current knowledge

Synthesize the relevant scholarly understanding. Show what is established and where the current evidence has limits.

Paragraph 3: define the unresolved issue

State the precise problem that remains. Distinguish practical need from scholarly gap where both are present.

Paragraph 4: establish the researchable need

Explain why a focused investigation is warranted and what part of the problem can reasonably be addressed by the proposed project.

Transition to the research question

The next sentence or section should make the resulting aim or question feel inevitable rather than unrelated.

This sequence is a reasoning aid, not a required heading structure. Always follow the current requirements of the programme, faculty, journal, funder or supervisor that controls your submission.

Test the link between the problem and research question

A useful audit is to place the final problem statement beside the research question and compare their key terms.

If the problem concerns a particular population, context and relationship, the research question should not suddenly introduce a different population, broader context or new outcome. Likewise, if the problem is about an explanatory mechanism, a purely descriptive question may not address it.

Ask:

1. Does the question investigate the unresolved issue I actually established?
2. Is the population or context consistent?
3. Does the proposed method generate the kind of evidence required?
4. Have I narrowed the problem enough for the available time and access?
5. Have I avoided promising an outcome that the design cannot establish?

Alignment is more important than ambitious wording.

Common problem-statement failures

Starting with the gap you want to find

If you decide in advance that “there is a gap” and then search only for evidence that supports it, the literature review becomes confirmation rather than investigation. Let the evidence determine the gap.

Using absence of search results as proof of absence

A weak search, narrow database, poor keywords or access limitations can all produce few results. None proves that no relevant research exists.

Mixing practical and scholarly evidence

A government report may establish a real-world condition without proving a literature gap. An academic review may establish a scholarly limitation without proving that a local operational problem exists. Keep the evidence roles distinct.

Relying on stale numbers

If a claim depends on a rate, count, prevalence estimate, market value, policy status or institutional figure, verify its date and scope before using it.

Writing a universal template

Problem statements vary across disciplines. A laboratory study, qualitative case study, policy analysis, historical project and engineering design project may frame research problems differently. Use the logic, but respect disciplinary conventions.

Confusing a large problem with a feasible thesis

A thesis does not need to solve the entire social or organizational problem. It needs a researchable question that makes a bounded contribution to understanding it.

Claiming originality too early

“No one has studied this before” is a demanding claim. Often, the defensible contribution is narrower, such as examining a relationship in a new context, testing an explanation under different conditions, comparing approaches, or addressing a specific methodological limitation.

Supervisor-ready review questions

Before sending the problem statement to a supervisor, review it with these questions:

A supervisor can then respond to the actual research logic rather than spending the meeting trying to discover what the problem is.

Final checklist

Before treating the problem statement as ready, confirm that you can answer yes to the following:

• I can state the problem in one or two precise sentences without exaggeration.
• I know what evidence establishes the practical or substantive issue.
• I have synthesized the literature relevant to the scholarly problem.
• I have not manufactured a gap from a convenient absence of sources.
• I have separated practical need from scholarly gap where necessary.
• I have identified the population, setting, case or material closely enough for feasibility to be assessed.
• Any statistics or institutional claims are dated and sourced.
• I have avoided unsupported claims of originality, urgency or absence of prior research.
• The research question follows directly from the unresolved issue.
• The proposed evidence and methodology can realistically address that question.
• The structure follows the requirements that actually govern my project.

A defensible problem statement is not the paragraph with the strongest adjectives. It is the one in which the evidence, scope and research question fit together clearly enough that another reader can inspect the logic.