D291 Learning Experience Design Foundations I, catalog number LXD 5068, is the three-CU entry point to learning experience design at WGU, and it introduces the field as a deliberate merger of instructional design and user experience design aimed at human-centered learning. The course works through the opening phases of the design thinking process, which means the deliverable is almost never a finished course. It is understanding: who the learner is, what they are actually trying to do, and what problem is worth solving. Candidates who arrive from teaching or from corporate training routinely lose aspects here by producing a solution before they have produced a defensible problem statement.
What learning experience design borrows from each parent field
Instructional design brings a heritage of analysis, objectives, alignment and evaluation. It is strong on whether the content is correct and whether the assessment measures the objective. It is historically weak on whether anyone wants to be there.
User experience design brings research methods for finding out what people do rather than what they say, plus an insistence that the artefact be usable, accessible and appropriate to the moment of use. It is strong on empathy and on evidence from observation. Left on its own it can produce something delightful that teaches nothing.
D291 sits at that intersection, and the assessed work reflects it. A submission that reads as pure instructional design, all objectives and alignment tables, will look thin on the empathy and definition aspects. A submission that reads as pure user research, all personas and quotes, will look thin wherever the rubric asks what the learner will be able to do. The candidates who score cleanly are the ones who keep both halves in every section: this is what we observed, therefore this is what the learner needs to be able to do, therefore this is the design implication.
One vocabulary point saves confusion. A learner is not a user in the ordinary sense. Users generally want the task to be effortless; learners sometimes need effort, because difficulty in the right place is what produces durable learning. Any design decision that removes struggle should be justified against learning, not only against convenience, and rubric aspects covering design rationale are often where that distinction is tested.
Turning your scored aspects into a section plan
WGU keeps the scoring detail for D291 inside your Course of Study rather than in the public catalog, so open the rubric before drafting. Each aspect is scored independently on a three-point scale and each one needs a 2. Nothing averages, so a superb persona will not lift a problem statement that never names a measurable gap.
Turn the aspect list into headings using the rubric's own nouns. Design deliverables are read for evidence rather than for narrative flow, and an evaluator scoring a research aspect should not have to find it inside a section called Background.
The word budget, worked. Suppose your rubric shows six scored aspects and the directions call for a design report of roughly 2,000 words. Reserve 180 words for a framing opening that names the context and the audience, and 120 for a closing that states what happens next. That leaves about 1,700 for scored content, or 285 an aspect. Then redistribute on purpose. In a foundations task the two aspects that most reward length are the one asking how your research findings led to your problem definition, and the one asking you to justify your method choice. Both are chains of reasoning. Take 60 words from each of the three most descriptive aspects and add 90 to each of those two.
A rule that prevents the classic D291 return: any aspect containing the word evidence is asking for something you gathered, not something you assumed. If your persona has no observation, interview or data behind it, it is a character sketch and will be scored as one.
A structure that fits a foundations design report
Where the task directions specify a template or an artefact type, follow it exactly. Where the arrangement is left to you, this order matches the way early design thinking aspects are usually written.
| Section | What belongs in it | What earns the aspect |
|---|---|---|
| Context and audience | The organisation or setting, the learner group, the constraint you are designing inside | Usually unscored, but every later claim about fit is checked against it |
| Research approach | Who you spoke to or observed, how many, why that method suited the question | Scored for justification; sample of convenience is fine if you say so and say why |
| Findings | What you actually heard and saw, separated from your interpretation of it | Scored for grounding; findings with no source read as invention |
| Learner representation | Persona, journey map or equivalent, each element traceable to a finding | Scored for traceability rather than for polish |
| Problem definition | The gap stated as a measurable difference between current and desired performance | The aspect that fails most often; a topic is not a problem |
| Design implications | What the definition rules in and rules out before any solution is chosen | Scored for showing that the research constrained the design |
| Ethics and access | Consent, data handling, accessibility needs surfaced by the research | Scored where the rubric names ethics or inclusive design |
| References | Design and learning sources in APA | Scored where citation is named; unsourced method claims are a common miss |
Resist the pull toward a solution. If your report ends with a recommended module, a platform and a run time, you have answered a question the course has not asked yet. That work belongs in the second foundations course.
Evidence craft in an empathy-stage submission
The evidence problem in D291 is that most of it comes from people rather than from literature, which candidates handle less confidently.
- Report what was said, then interpret separately. A quotation followed by your reading of it is two pieces of evidence. A paraphrase blended with your opinion is neither.
- Say how many and who. Three interviews is a legitimate sample at this stage. Three interviews described as our research is not, because the reader cannot weigh it.
- Anonymise participants. Role and context only, no names, no employer identifiers, no recordings attached without consent.
- Cite the method, not just the finding. If you ran a contextual inquiry or a card sort, cite a source for how that method is meant to be run and note where you deviated.
- Ground learning claims in learning research. Statements about attention, cognitive load or motivation need a source, because they are the load-bearing walls of your later design.
- Keep quoted material short and attributed. WGU scans submissions for similarity, and design writing is full of quotable definitions that are easy to overuse.
What reads as senior work is naming the limitation of your own research before the reader does. Two participants from one department cannot represent an organisation. Saying that, then stating what a second round would sample, is a strength rather than an admission.
What separates Competent from a submission sent back
Aspects score on their own, so returns here are usually about one section. The most frequent cause is a problem statement that describes a topic instead of a gap.
- Every scored aspect has a heading in the rubric's language.
- Every element of the persona or journey map points back to something observed.
- The problem is stated as a difference between what happens now and what should happen, with something countable in it.
- Method choice is justified rather than reported.
- Ethics and accessibility appear as design inputs, not as a closing paragraph.
- Every claim about how people learn carries a citation that is used in the argument.
Performance assessment work at WGU can be revised and resubmitted with no grade penalty, so a return is a scheduling cost. It is a real one in a six-month flat-rate term, where the figure that decides your effective cost per course is how many courses you close before the term ends.
Where D291 sits alongside a proctored objective assessment, the boundary is fixed: we prepare only, and we never sit an assessment or ask for portal credentials.
Six mistakes that cost time in D291
- Designing the solution in the discovery report. The strongest signal of an inexperienced designer is a needs analysis that already knows the answer, and evaluators reading the definition aspect see it immediately.
- Building a persona from assumptions. Age, job title and a stock frustration invented at the desk is a template exercise. Every attribute needs a source.
- Confusing a symptom with a problem. Low completion rates are a symptom. The problem is whatever makes completion rational to abandon, and finding it is the point of the empathy phase.
- Treating accessibility as a later step. Access needs surfaced in research are design constraints from the start, and rubrics that name inclusive design check whether they shaped the definition.
- Writing findings and interpretation as one paragraph. Evaluators need to see which is which; blending them costs the grounding aspect even when the conclusion is right.
- Leaving the method unjustified. Choosing interviews over observation is a decision with consequences. Saying why is often its own scored aspect.
How support works on this course
Send the rubric from your Course of Study, the task directions and whatever research you have gathered so far. What comes back is aspect-mapped: a draft answering each scored aspect under its own heading, a problem statement written as a measurable gap, a persona whose every line traces to a finding, and a method justification that will hold up.
The reasoning transfers. D291 sets the pattern the rest of the learning experience design sequence repeats, so understanding why the definition was written the way it was makes the second foundations course substantially faster to draft.
Questions students ask about D291
Is D291 the same course as LXD 5068?
How does D291 relate to D292?
I have no design background. Is that a problem?
Stuck on the problem definition in D291?
Send your Course of Study rubric, the task directions and your research notes. You get an aspect-mapped draft with a measurable problem statement and a persona that traces to evidence.
Where D291 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.