WGU D300: Identifying Learner Needs and a Research Problem

Where the Capstone Sequence Actually Begins

D300, Identifying Learner Needs and a Research Problem, is the first of three capstone courses in WGU's Master of Education in Education Technology and Instructional Design. WGU's official program guide describes it as an introduction to design-based research that focuses on the first two phases of that process: identifying and analyzing the learning problem, and reviewing the literature. The program guide lists the course at 3 competency units and names Learning Experience Design Lab as its prerequisite.

Direct answer: You pass D300 by narrowing your focus to one specific, observable instructional problem in a real setting you can actually access, documenting that problem with evidence rather than opinion, and supporting it with a focused review of scholarly sources. Write directly to each rubric aspect in the evaluator's own language, then submit early enough that a first round of feedback still leaves you time to revise.

Most students who reach D300 are working adults already embedded in a learning environment: classroom teachers, instructional coaches, corporate trainers, and nurse educators. That matters, because unlike a lecture-and-exam course, D300 asks you to bring your own context to the table. Your workplace, your learners, and your access to data are the raw material of the assessment.

The course also matters more than its 3 units suggest. Everything you build in the two capstone courses that follow rests on the problem you frame here, and a statement that is too broad, too vague, or built on a setting you cannot return to will follow you through the rest of the sequence.

What D300 Officially Asks You to Demonstrate

WGU's program guide lists three competencies for this course, and they are the clearest map you will get of what your work has to show:

• Defining an instructional problem based on learner analysis. Not a hunch and not a technology wish list, but a documented gap between how your learners currently perform and how they need to perform, grounded in an actual analysis of who those learners are.
• Defining the purpose of the research and the questions it sets out to answer. This is where a messy situation becomes a researchable question narrow enough that one study in one setting could genuinely address it.
• Conducting a literature review to inform potential learning solutions. Finding, evaluating, and synthesizing scholarly sources that speak to your problem and to plausible directions for a solution, so the next course does not start from a blank page.

The program guide also notes that D300 continues the Design Thinking work from earlier courses: you empathize with your learners and define the instructional problem your research will help you understand and address. If Design Thinking felt like a vocabulary exercise earlier in the program, this is where it starts doing real work.

D300 is assessed by performance assessment rather than a proctored exam. WGU describes performance assessments generally as scored tasks such as projects, essays, and research papers, evaluated against a rubric, with the option to revise and resubmit any aspect that does not yet meet the standard. Check your course of study for the exact task breakdown, since assessment structures are revised periodically.

How Hard D300 Is and How Long It Really Takes

Compared with statistics-heavy courses, D300 is not conceptually brutal; the reading load is manageable and the ideas are approachable for anyone who has worked with learners. The difficulty lives somewhere else entirely: in scoping, writing, and revision. Deciding what to leave out is harder than understanding design-based research.

A reasonable planning estimate for a working student is roughly three to five weeks of steady part-time effort, in the range of six to ten focused hours per week. Treat that as a planning figure, not a promise. If you arrive already knowing your setting and your problem, and you write comfortably at the graduate level, it can move considerably faster. If you are still deciding between three possible topics in week two, expect it to stretch. Writing stamina matters more than exam technique here, and the literature review is usually the longest single piece of prose you produce.

Plan for at least one revision cycle. Because an evaluator returns any aspect that does not yet meet the standard, a first submission coming back marked for scope or for thin evidence is a normal outcome rather than a bad one, and the rewrite is usually quicker than the original draft. Treating a revision request as part of the process, rather than a verdict on your ability, is one of the most useful mental adjustments you can make in a performance-assessed course.

A Four-Week Plan for Building a Defensible Problem

Week one: choose your ground. Before you write anything formal, draft a single paragraph naming the setting, the specific learners, the gap you observe, and how you know it exists. If you cannot fill in that last part, the topic is not ready. Test two or three candidate problems this way and keep the one with the strongest evidence trail, not the one that sounds most impressive.

Week two: gather the evidence and lock the vocabulary. Collect the artifacts that show the gap is real: score distributions, course completion patterns, survey comments, coaching notes, whatever your context genuinely produces. In parallel, use active recall on the methodology itself. Close your course materials and write from memory what each phase of design-based research does and how it differs from a traditional experimental study. Whatever you cannot reproduce, reread and try again the next day. Short, spaced repetitions across the week beat one long session, and this vocabulary reappears in every later capstone course.

Week three: build a synthesis matrix, not a stack of summaries. Search the WGU Library for peer-reviewed work on your problem area. Instead of writing one paragraph per article, build a simple table with sources as rows and recurring themes as columns. When you fill it in, the patterns write your literature review for you: this cluster of studies agrees on X, this one disagrees, and here is where your context sits. Aim for depth on a narrow question rather than a shallow tour of educational technology in general.

Week four: score yourself before the evaluator does. In a performance-assessed course, self-testing means reading the rubric aspect by aspect and asking, in the evaluator's words, where exactly in my document is this demonstrated. Highlight the sentence that satisfies each aspect. Any aspect you cannot point to is a revision request waiting to happen. Then read the whole thing aloud once for coherence and submit. The same rubric-first habit pays off across the program, including in D293 Assessment and Learning Analytics, which sits earlier in the same degree.

Where D300 Submissions Usually Come Back

• Leading with a solution. Writing that your school needs a new learning platform is a solution in search of a problem. D300 wants the gap first; designing the solution belongs to the next course.
• A problem the size of a school district. "Student engagement is declining" is not researchable. One grade level, one course, one measurable behavior is.
• Opinion dressed as evidence. Phrases such as "teachers feel" or "it seems clear" will not carry an evidence aspect. Name the source, the data, and the timeframe.
• Annotated bibliography syndrome. Consecutive paragraphs each summarizing one article is not a literature review. Organize by theme and let the sources speak to each other.
• Weak sources. Vendor white papers, blog posts, and news articles rarely satisfy a scholarly-source requirement. Filter for peer-reviewed work in the library databases.
• Choosing a setting you will lose access to. If you change jobs or the class ends, your later capstone courses stall. Pick ground you will still stand on months from now.
• Sloppy citation. Formatting and attribution errors are avoidable and they cost you a resubmission cycle. Check the style guidance in your specific course of study before you submit.
• Waiting until the work feels perfect. An evaluator's feedback is more useful than another week of solo polishing. Submit when it is honestly complete, not when the anxiety stops.

D300 Readiness Checklist

• Can you name your setting, your target learners, and your instructional problem in two sentences without hedging?
• Can you point to concrete evidence that the gap exists, and say where that evidence came from?
• Can you explain design-based research from memory, including what its first two phases accomplish?
• Can you state your research question narrowly enough that a single study in one setting could address it?
• Can you show that your problem is a gap in learning or performance, not a preference for a particular tool?
• Can you connect your problem back to a genuine learner analysis rather than to your own convenience?
• Can you group your sources into themes and describe where scholars agree and disagree?
• Can you confirm every source you rely on is peer-reviewed and retrieved through the library rather than a search engine?
• Can you highlight, aspect by aspect, the exact place in your document where each rubric requirement is met?
• Can you still access this setting and these learners for the next two capstone courses?

D300 FAQ

Is D300 an objective exam or a performance assessment?

It is a performance assessment. You submit written work that an evaluator scores against a rubric, with the option to revise and resubmit any aspect that does not yet meet the standard. There is no proctored multiple-choice test to schedule.

How many competency units is D300 worth?

WGU's official program guide for the M.Ed. in Education Technology and Instructional Design lists it at 3 competency units. Always confirm against your own degree plan, since program structures are periodically revised.

What comes before and after D300?

The program guide names Learning Experience Design Lab as the prerequisite. D300 is then followed by D301 Developing an E-Learning Solution and Research Methodology and D302 Implementing and Evaluating E-Learning Solutions, which together carry your problem through design, implementation, and evaluation.

Do I need my own classroom or workplace to complete it?

You need a real learning context you can describe and gather evidence about. That is often your own classroom or training program, but students in other roles work from a setting they have legitimate access to. Talk with your course instructor early if your situation is unusual.

What if my submission is returned for revision?

That is a normal part of performance-assessed courses, not a failure. Read the evaluator's comments against the rubric, fix what was flagged plus anything that flag exposes elsewhere, and resubmit. Most revisions are far shorter than the original effort.

Where should I look for related courses and study material?

Start with the School of Education guide hub or browse the full library of WGU course guides. Program details and the official course description live on the WGU program page.