How to Write a Problem Statement
and Purpose Statement
Liberty University’s Research Concept Paper (Task 1) trips up more doctoral candidates than any other single assignment. This guide walks through exactly how to structure the general problem, support sentences, specific problem, and purpose statement — so your instructor approves it the first time.
🎓 Stuck on your Research Concept Paper? Our doctoral writing specialists work with DBA and DSL candidates daily.
Get Expert Help →What Task 1 of the Research Concept Paper Actually Requires
Task 1 of Liberty University’s Research Concept Paper (BMAL 785 / BUSI 885) asks you to develop two things: a Problem Statement — a single paragraph of under 250 words that establishes a real, current, documented leadership or business problem — and a Purpose Statement that clearly states what your study will do about it. Both must follow rigid sentence-level formatting and be supported by peer-reviewed sources published within five years of your anticipated graduation date.
Most candidates underestimate this task. It looks short — one paragraph for the problem, one for the purpose. But the instructor’s comment sheet for Task 1 runs several pages long, covering sentence structure, citation currency, alignment, hedging language, and annotated bibliography format. Getting it right means understanding exactly what each component must and must not do.
One thing to settle upfront: Task 1 is not a literature review. You are not explaining the background of the topic, exploring solutions, or providing recommendations. You are proving — with current evidence — that a problem exists and that it has consequences. That framing shapes every sentence you write.
Do Not Move to Task 2 Until Task 1 Is Approved
The Research Concept Paper is sequential. Each task builds directly on the last. Submitting Task 2 before Task 1 is approved creates compounding revision work. The instructor posts a grade of “1” to signal approval — that is your green light, not a comment saying it looks good.
The General Problem Sentence: Structure, Requirements, and What Gets It Wrong
The general problem sentence is the first sentence of your problem statement paragraph. It has a fixed opening phrase — no exceptions — and a required consequence clause. Here is the architecture:
General Problem Sentence — Required Structure
Every element below is mandatory · Nothing can be removed
This exact phrase is required. Do not paraphrase it, reorder it, or add words before it.
State one or two broad, clear negative outcomes of not addressing the problem. This is consequences, not causes. Example: …resulting in the inability of organizations to make critical changes.
The general problem to be addressed is the challenges leaders face gaining employee support for new initiatives resulting in the inability of organizations to make critical changes.
▸ Correct:
The general problem to be addressed is the lack of formal leadership development programs for frontline managers resulting in reduced organizational performance and increased employee turnover.
▸ Wrong — phrased as a question:
The general problem to be addressed is why leaders are ineffective resulting in…
▸ Wrong — states cause, not problem:
The general problem to be addressed is that leaders are not receiving adequate training, which causes poor retention resulting in…
That last wrong example is one of the most common errors. Stating the cause (“not receiving adequate training”) is not the same as stating the problem. The problem is the observable, documentable situation — the cause is what you might explore in your research. Keep those separate.
How to identify your general problem
Ask yourself: what is the observable, documented gap or failure that exists in organizations in my cognate area? Not “why” it exists. Not “how to fix it.” Just: what is the bad situation that is happening — and what goes wrong because of it? One clean sentence. That is your general problem.
The Three Support Sentences: Proving the Problem Exists
After your general problem sentence, you need three support sentences. Each one cites a peer-reviewed scholarly source published within five years of your anticipated graduation date. Their job is simple: prove that the problem you described is real and is currently happening.
Each support sentence is one sentence long. Each should demonstrate one consequence of not addressing the problem — and that consequence should align with what you stated in the general problem sentence. Think of them as three independent witnesses all confirming the same crime.
Support Sentence Structure
One per sentence · Active voice · Consequence-focused
Keep it to one sentence, under 40 words. Combine shorter assertions if needed.
Smith (2024) stated that many high-level leaders struggle with effectively projecting an engaging vision for a new initiative, which makes it difficult to gain employee buy-in.
▸ Support sentence 2 (demonstrates problem → consequence 2):
Jones (2023) found that employee buy-in was the most critical determining factor in projecting the future success of organizational change initiatives.
▸ Support sentence 3 (bridges to the specific problem area — optional “bridge”):
Herbert (2024) supported these findings by explaining that the ability of an organization to carry out critical strategic changes is directly related to the leader’s capacity to foster organization-wide support.
▸ Bridge sentence (optional — narrows toward specific problem):
Adams (2023) found that the inability to gain employee support was a particular challenge in the retail clothing industry.
Notice how each sentence focuses on the problem and its consequences — not solutions, not recommendations, not background explanation. The bridge sentence (optional but useful) takes the reader from the broad problem toward the narrow focus of your specific problem. It makes the paragraph flow without requiring a logical jump.
The most common support sentence rejection reason
Introducing consequences in your support sentences that don’t appear in your general problem sentence. If your general problem mentions “reduced performance,” your support sentences should demonstrate the problem resulting in reduced performance — not introduce new consequences like turnover or safety incidents. Stay within your own scope.
The Specific Problem Sentence: Narrowing to Your Single Case Study
The specific problem sentence closes the problem statement paragraph. It is a narrowly focused subset of your general problem — one that is realistic to study within the ADRP’s single case study format. Two things make it structurally different from the general problem sentence:
First, it must include the phrase “within the selected single case study organization.” This connects your study to the program’s methodology requirement. Second, it must use hedging language — words like “possible,” “potential,” “might,” or “could” — because you have not yet proven the problem exists in that specific narrow context. That is what the research is for.
Specific Problem Sentence — Required Structure
Mirrors the general problem · Narrowed · Hedged · No citation
Start with this. The hedging word (potential/possible/possible challenges) goes right here.
This phrase is mandatory. If you know a specific industry, identify it here too: e.g., “within the retail industry within the selected single case study organization.”
The consequence must mirror or subset the consequences in the general problem sentence. Same outcomes, just narrowed. The hedging word “possibly” or “potentially” is required here too.
After the specific problem sentence, add a single sentence (not a heading) that explains how this study relates to your DBA cognate. Keep it under 40 words. Start with: “This proposed research concept is related to the [cognate name] cognate because it focuses on…”
Writing the Purpose Statement: Intent, Design, and Knowledge Gap
The purpose statement is a single paragraph under 250 words. Its job is to state what your study will do — how it will fill the knowledge gap created by the problem. It does not describe the problem again, introduce new topics, or propose solutions.
Purpose Statement — Required Structure
Under 250 words · One paragraph · Aligned to problem statement
This exact phrase opens the purpose statement. It names the methodology (qualitative single case study) and transitions to the exploratory intent.
The alignment test for your purpose statement
Read your general problem sentence. Then read your specific problem sentence. Then read your purpose statement. Can you draw a straight line from one to the next? If the purpose statement introduces anything not present in the problem statements — a new population, a new consequence, a new topic — revise it. Every word in the purpose statement should be traceable back to the problem.
The Straight Line: How All Four Elements Must Connect
Liberty University’s guide refers to “concept alignment” — the requirement that a reader can trace a straight line from the general problem through the specific problem, purpose statement, and eventually to the research questions and methodology. Misalignment is the single most common reason Task 1 gets returned for revision.
General Problem
Overarching problem proven to exist through current literature. Broad, cognate-aligned, consequence-included.
Specific Problem
Narrowed subset of the general problem. Includes hedging language. Targets a single case study organization. Same consequences as general problem.
Purpose Statement
Describes the intent to explore or understand the specific problem. Names the qualitative single case study design. Identifies the knowledge gap.
Research Questions (Task 2)
Derived from the problem and purpose. Address the specific problem directly. Use qualitative framing (how/why/what). Follow the required RQ formats.
Alignment breaks most often at the transition between the general and specific problem. Students narrow the population or industry in the specific problem but accidentally keep the same broad consequence phrasing — or they flip it the other way, with the specific problem using a totally different consequence than the general. Keep the consequences consistent and simply tighten them as you narrow the focus.
The problem statement is the cornerstone of the research proposal. Everything that comes after — the purpose, the research questions, the methodology, the framework — rests on it. If the cornerstone is crooked, nothing else will line up correctly.
— Moore, E.M. (2024). Effective Problem Statements & Research Questions. Liberty University School of Business.The Annotated Bibliography: What 200 Words Per Source Actually Means
Task 1 requires an annotated bibliography in Appendix A for each reference used in your problem statement support sentences. Not every source in the paper — only the ones cited in the problem statement. If you add more sources in later tasks, you do not annotate them.
Each annotation is a minimum of 200 words and must cover three specific things:
Why the source is credible
Describe the author(s) — their credentials, institutional affiliation, or field expertise. Identify the publication — is it a peer-reviewed journal, a scholarly monograph? Note the date and why its recency matters for your problem.
Summary of the article
Summarize the main argument, methodology, and findings of the source. This is not a quote — it is your paraphrased summary demonstrating you have actually read and understood the article. Aim for four to six sentences here.
How it supports your general problem
Explicitly connect the source to the existence of the problem you stated in your general problem sentence. Discuss how its findings demonstrate the problem is real, current, and consequential. Reference the specific consequence from your general problem sentence by name.
Smith, J. A. (2024). Leadership communication and employee buy-in during organizational change. Journal of Organizational Behavior, 45(2), 112–134. https://doi.org/xxxxx
▸ Annotation begins indented 0.5 inches (same as block quote):
Smith (2024) is a peer-reviewed article published in the Journal of Organizational Behavior, authored by a researcher at [institution] with expertise in… [Why credible]. The study examined… [Summary]. These findings are directly relevant to the general problem because they demonstrate that [specific consequence named in your general problem sentence] is occurring in organizational settings, thereby supporting the assertion that leaders face measurable challenges gaining employee support… [How it supports your problem].
Annotated Bibliography Quick Rules
- Annotations only for problem statement support sentence sources — no others
- Minimum 200 words each — not 190, not “approximately 200”
- Entries in alphabetical order
- Reference entry uses hanging indent; annotation indented 0.5 inches from left margin
- All DOIs or journal URLs must be active hyperlinks
- No textbooks — primary scholarly sources only
Mistakes That Get Task 1 Returned — And Exactly How to Fix Them
| ❌ The Mistake | Why It Gets Returned | ✓ The Fix |
|---|---|---|
| Stating the cause of the problem in the general problem sentence | “Leaders are ineffective because they lack training” describes a cause, not the problem itself. The instructor will note this immediately. | State only what is happening and what goes wrong because of it. The cause is for your framework in Task 3. Keep it out of the problem statement entirely. |
| Missing “within the selected single case study organization” in the specific problem | This phrase is mandatory. It connects your study to the ADRP’s single case study methodology. Without it, the submission is non-compliant. | Copy the phrase verbatim and position it in the specific problem sentence. Add an industry or sector identifier alongside it if known: “within the healthcare sector within the selected single case study organization.” |
| No hedging language in the specific problem sentence | Stating the problem as confirmed in the specific context introduces bias — you haven’t studied it yet. The instructor will flag this as a formal requirement violation. | Use “possible,” “potential,” or “possibly resulting in” in the specific problem sentence. Both the problem and the consequence need hedging words. |
| Support sentences older than five years from graduation | Outdated sources suggest the problem may no longer exist or may have been resolved. The program requirement is clear on currency. | Calculate your five-year window from your expected graduation date — not today’s date. Replace any out-of-window sources with current equivalents before submitting. |
| Purpose statement introduces topics not in the problem statement | This breaks alignment. If the problem is about leadership communication and the purpose drifts into culture change strategies, the instructor will note the misalignment. | After writing the purpose statement, read it against both the general and specific problem sentences. Remove anything that was not already present in the problem. |
| Purpose statement uses quantitative framing (“determine,” “test,” “measure”) | The ADRP is a qualitative single case study. Quantitative verbs are wrong framing for a flexible design. | Replace with “explore” or “understand.” If you find yourself reaching for measurement language, it is a signal your problem may be oriented toward quantitative inquiry — which is not permitted in this program. |
| Problem statement exceeds 250 words | The program specifies “less than 250 words.” This is not a suggested guideline — the instructor will mark it as non-compliant. | Write the five required components (general problem, three support sentences, specific problem), then word-count. Trim support sentences to one sentence each. The bridge sentence is optional — cut it if you are running long. |
| Annotated bibliography includes sources not used in the problem statement | The instruction is explicit: annotate only problem statement support sentence sources. Extra annotations signal the candidate did not read the guide carefully. | Count your problem statement citations. Write exactly that many annotations. If you later add sources in Task 2 or beyond, do not annotate them — the bibliography does not grow. |
One more thing worth flagging: the Change Matrix. When your instructor returns Task 1 with a grade of “0,” all their comments go into a Change Matrix document. As you address each comment, you log a brief description of what you changed. This document travels with every resubmission. Missing the Change Matrix is treated the same as ignoring the feedback — do not skip it.
FAQs: What DBA and DSL Candidates Ask About Task 1
The Problem Statement Is the Cornerstone — Get It Right Before Moving On
Task 1 is not the longest assignment in the Research Concept Paper sequence. But it is the most structurally sensitive. Every sentence has a defined role. Every element has a format requirement. And everything that comes in Task 2, 3, and 4 is built on what you establish here.
The candidates who breeze through the ADRP are the ones who slowed down on the problem statement, got alignment right the first time, and used their instructor’s Change Matrix feedback as a precision tool rather than a frustration. That is the approach worth taking.
For verified external guidance on research methodology in qualitative case study design, the SAGE Encyclopedia of Case Study Research provides peer-reviewed foundational definitions that can support your methodology discussion in Tasks 2 and beyond.
For hands-on help writing your problem statement, purpose statement, annotated bibliography, or any component of the Liberty University Research Concept Paper, the team at Smart Academic Writing includes doctoral-level writers with direct experience in DBA and DSL programs. See our DBA assignment help, dissertation support, and dissertation coaching pages for available options.
Task 1 Pre-Submission Checklist
- General problem sentence begins with exact required phrase and includes a “resulting in” consequence clause
- Three support sentences — each one sentence, each citing a different source within five years of graduation
- Support sentence consequences align with the general problem’s stated consequences
- No causes, backgrounds, solutions, or recommendations appear anywhere in the problem statement
- Specific problem sentence includes “within the selected single case study organization” verbatim
- Specific problem uses hedging language (possible/potential) in both the problem and consequence
- Cognate relationship sentence added after specific problem (not a heading, under 40 words)
- Purpose statement begins with exact required phrase and uses “explore” or “understand”
- Purpose statement aligns entirely with the problem statement — no new topics introduced
- Annotated bibliography entries exist for each and only the problem statement citations
- Each annotation is 200+ words covering credibility, summary, and connection to the general problem
- All DOIs and URLs are active hyperlinks in the reference list