D300 Identifying Learner Needs and a Research Problem, catalog number LXD 6053, is the three-CU first course of the learning experience design capstone sequence, and it covers the opening two phases of design-based research: analysing the learning problem and reviewing the literature around it. Nothing gets built here and nothing gets tested. What you produce is a problem worth three courses of work, defined tightly enough that somebody else could tell whether you had solved it. Students who rush this course pay for it twice, because a loose problem produces a research question that cannot be answered and a solution that cannot be evaluated.
A practical problem and a research problem are different objects
Everyone arrives with a practical problem. Our onboarding takes too long. Pupils cannot use the reading platform. Nurses skip the refresher module. Those are real and they matter, and none of them is a research problem yet.
A research problem adds three things. It names what is not known, not merely what is going badly. It is bounded to a population and a setting rather than stated about the world. And it is stated so that evidence could settle it, which means somebody could in principle show you were wrong.
The conversion usually runs through a why. Onboarding takes too long is a symptom; the research problem sits at whichever explanation you cannot currently choose between. If new hires might be failing because the sequence is wrong, or because the material assumes knowledge they lack, or because nobody has time to practise, then you have a genuine unknown and a study that could resolve it. Writing that sentence properly is most of D300, and rubric aspects covering problem statement quality are scored on precisely this move.
Design-based research shapes the framing further. It is not a study of a phenomenon in the abstract; it is an iterative attempt to improve a real situation while producing knowledge about how the improvement works. Your problem therefore has to be one you can act on, in a setting you can reach, within the time the capstone allows. A magnificent problem in a school you have no relationship with is not a capstone, and the earlier that reality lands the better.
Turning the rubric aspects into a proposal plan
WGU keeps the scoring detail for D300 inside your Course of Study rather than in the public catalog. Open it before writing, because capstone rubrics tend to be longer than course rubrics and the aspect list is effectively a chapter outline. Each aspect scores independently against a three-point scale and each needs a 2.
Write to the aspects with headings in their own language. Capstone documents are long, and an evaluator who has to search for your significance argument inside a section called Background will read less generously than one who does not.
The word budget, worked. Assume nine scored aspects and directions asking for roughly 3,500 words. Reserve 250 words for an introduction that states the setting and 150 for a closing that says what the next capstone course will do. That leaves about 3,100 for scored content, or 345 an aspect. Then weight it deliberately. The literature synthesis aspect and the problem statement aspect are the two that carry the rest of the capstone, and both deserve more. Take 70 words from each of the six remaining aspects and add 210 to each of those two. Nothing in the total changes and the two load-bearing sections get the room they need.
A caution about the literature. A review that is organised source by source is a summary, and summaries are scored low in graduate research work. Organise by theme, so that each paragraph makes a claim and cites several sources supporting or complicating it. If a paragraph opens with an author's name, it is probably a summary paragraph.
A structure that fits a problem and literature deliverable
Where the task directions or a supplied template specify the structure, follow them exactly. Where the arrangement is yours, this order matches the way design-based research proposals are usually assessed.
| Section | What belongs in it | What earns the aspect |
|---|---|---|
| Setting | The organisation or school, your access to it, and the constraint you work inside | Usually unscored, but feasibility judgments rest on it |
| Problem context | The practical situation, with data showing it is real rather than perceived | Scored for evidence; an anecdote is a starting point, not a warrant |
| Needs analysis | Who was consulted or observed, how, and what emerged | Scored for method as much as for findings |
| Problem statement | The bounded, evidenced statement of what is not known and for whom | The aspect the whole capstone rests on; vague statements return |
| Significance | Who benefits if this is resolved, and what changes for them | Scored for specificity; an appeal to general importance meets little |
| Literature synthesis | Thematically organised review of what is already known and where it disagrees | Scored for synthesis; source-by-source structure reads as a summary |
| Gap | What the literature does not settle for your population or setting | Scored for following from the review rather than being asserted |
| Ethical and access considerations | Permissions needed, data handling, participant protection, timeline for approvals | Scored where named; late permission planning derails capstones |
| References | APA, current, weighted toward peer-reviewed work | Scored where citation quality is named |
Keep one population throughout. Capstone problems drift when the needs analysis covers one group and the literature review covers a broader field, and the gap claim then does not follow from either.
Evidence craft in a problem definition
The evidence at this stage is a mixture of local data and published research, and the two have to be kept visibly distinct.
- Show the local data. Completion rates, error counts, help desk volume, assessment results: something countable that establishes the problem exists outside your impression of it.
- Report how you gathered needs information, including how many people and how they were selected. A convenience sample is acceptable and unstated method is not.
- Weight the literature toward peer-reviewed sources and recent work, and say when you rely on an older source because it is foundational.
- Include studies that complicate your position. A review where everything agrees usually means the search was too narrow.
- Plan permissions early. Organisational approval and any institutional review required by your task directions take time you have not budgeted.
- Anonymise everything: no participant names, no employer identifiers where policy restricts them, no pupil information at all.
The sentence that marks a strong proposal is the one bounding the claim. Your problem exists in your setting, and whether it generalises is an open question. Saying that explicitly makes the later evaluation easier to write honestly.
What separates Competent from a submission sent back
Aspects score independently, and the return in D300 is nearly always the problem statement or the gap.
- Every scored aspect has a heading using the rubric's noun.
- The problem is bounded to a population and a setting and rests on local evidence.
- The needs analysis reports its method, not only its conclusions.
- The literature review is organised by theme and makes claims rather than reporting studies in turn.
- The gap follows visibly from the review.
- Permissions and data handling are planned with a timeline rather than mentioned.
Performance assessment work at WGU can be revised and resubmitted with no grade penalty, so a return is a delay rather than a mark. In a six-month flat-rate term the delay is the cost, and a capstone course that cycles twice tends to push the whole sequence into another term.
Where D300 sits alongside a proctored objective assessment, we prepare only, never sit an assessment, and never ask for portal credentials.
Six mistakes that cost time in D300
- Choosing a problem you have no access to. Design-based research needs a setting you can work in for the rest of the sequence. Enthusiasm cannot substitute for permission.
- Stating a solution as the problem. We need a microlearning app is a preference. What it would fix, for whom, and why the current approach fails is the problem.
- Summarising the literature source by source. The synthesis aspect is scored on whether you built an argument from many sources, not on whether you read them.
- Claiming a gap the review did not establish. If nothing in your review shows the question is open, the gap sentence is an assertion and will be treated as one.
- Leaving permissions to the next course. Approvals have their own timelines, and a capstone waiting on consent is a capstone not progressing.
- Scoping a problem no three courses could resolve. Ambition here becomes an impossible study later. Bound it now while bounding is cheap.
How support works on this course
Send the rubric from your Course of Study, the task directions and whatever you know about the setting and the problem. What comes back is aspect-mapped: a problem statement bounded to a population with evidence behind it, a needs analysis with its method visible, a thematically organised synthesis, a gap that follows from the review, and a permissions timeline that will not ambush you in the next course.
Getting this right is the highest-leverage work in the sequence. A precise problem makes the research question in the second capstone course nearly write itself, and it makes the evaluation in the third one honest and straightforward.
Questions students ask about D300
Is D300 the same course as LXD 6053?
How do the three capstone courses fit together?
Can I change my problem later if it is not working?
Problem statement not tight enough yet?
Send your Course of Study rubric, the task directions and what you know about the setting. You get a bounded problem, a thematic synthesis plan and a permissions timeline.
Where D300 sits in WGU's programs
The July 2026 catalog places this code in 3 current WGU programs. Open a program page for the complete standard path and term positions. The live Degree Plan remains authoritative after transfer credit, substitutions, and mentor planning.
The assessments, one by one
The public catalog does not publish this course's PA/OA identity or task count. WGU Tutors publishes at most one PA manual per course and only from a WGU-controlled public rubric. Until that source exists, PA help begins from the student's real Course of Study and OA support remains preparation only.