D657 Design Applied Learning Capstone, catalog number DES 4100, is the three CU capstone of the WGU School of Business design sequence, delivering a real world product and experience design project. Every stage the sequence taught separately has to run end to end here on a single problem, and the report has to show the connections rather than the stages in isolation.
The through line is the assignment
A design capstone is returned far more often for a broken chain than for a weak artefact. The chain runs from research to insight to definition to concept to prototype to test to iteration, and each link has to be visible. A submission where the final design is excellent but nobody can trace which research finding produced it has failed the thing the capstone exists to assess.
The practical implication is that documentation is not a write up phase at the end. It is a continuous activity, because the reasons for decisions are only accurately available at the moment they are made. Capstones written from memory in the final fortnight produce vague justifications, and vagueness is precisely what an aspect scores down.
The second scored theme is scope. Design projects expand without resistance, because every insight suggests another feature and every feature suggests another screen. A capstone covering one journey properly, tested and iterated, demonstrates every competency in the sequence. One covering an entire product superficially demonstrates none of them, and it arrives late.
Third, the real world element carries weight. Real users, real constraints and real feedback are what distinguish this from an exercise, and evidence of them should be present in every section rather than concentrated in one.
Turning scored aspects into a section plan
Capstone rubrics live in your Course of Study and carry more aspects than ordinary courses. Count them before choosing a project, because the aspect list tells you what evidence the work has to generate and therefore how narrow the scope can afford to be. Each aspect is scored independently against a three point scale and each needs a 2, so a strong prototype with a thin research section is a returned capstone.
Capstones arrive in stages with approval checkpoints. Treat the approved scope as binding and record any change with its reason at the time.
The word budget, worked. Assume nine scored aspects and a report near 3,400 words alongside the artefacts. Reserve 220 words for an opening and 160 for a close, leaving about 3,020, near 335 per aspect. Then rebalance: the research and testing aspects go to roughly 450 each, funded by trimming the visual description aspects to 250. Design capstones consistently over describe what things look like and under evidence why they are that way.
A structure that fits a design capstone
Your capstone directions and any template take precedence. Where the shape is yours, this ordering carries the through line.
| Section | What belongs in it | How it gets read |
|---|---|---|
| Executive summary | Problem, approach, outcome and evidence it works, in one page | Written last, checked line by line against the body |
| Problem and users | Who has this problem and how you know, with research method stated | The foundation every later aspect is judged against |
| Research and insight | Findings, synthesis and the insight that drove the design | Insight rather than theme is what the aspect wants |
| Definition and scope | The problem statement and what was deliberately excluded | Explicit exclusions read as control |
| Concepts | Directions explored and the criteria that selected one | A single concept suggests the exploration step was skipped |
| Prototype | The design at appropriate fidelity, including non ideal states | States are what fidelity means at capstone level |
| Testing and iteration | Sessions, findings with severity, changes with before and after | The evidence that the design was validated rather than asserted |
| Outcome and next steps | What the final design achieves, what remains untested, what you would do next | Naming what is unresolved reads as maturity |
Build the through line explicitly. A short table mapping each research finding to the design decision it produced answers several aspects at once and takes an hour.
Evidence craft across a long project
A capstone runs for months and is written in weeks, which makes collection habits decisive.
- Keep a dated design journal with decisions and reasons. Most of the justification writing is transcription from it.
- Save every version of every artefact with a label, so before and after pairs are available later.
- Capture session notes within an hour of testing, before observations become conclusions.
- Anonymise participants consistently and confirm what may appear in an academic submission.
- Cite frameworks and principles throughout; a capstone does not lower the academic standard.
- Use APA and build the reference list continuously rather than reconstructing it at the end.
Include the direction you abandoned. A capstone that shows a concept explored, tested and dropped for a stated reason demonstrates the method far better than one where the first idea happened to be right.
What separates Competent from a submission sent back
With more aspects in play, the odds that one is thin rise accordingly.
- Every design decision traces to a research finding or a test result.
- Testing involved real people and the report says how many, when and how.
- Iteration is shown as before and after rather than described.
- Scope exclusions are stated as decisions with reasons.
- The executive summary matches the delivered work, including the numbers.
Capstone performance assessment work can be revised and resubmitted with no grade penalty, but capstone queues are the longest in the sequence. Terms run six months at a flat rate, so a capstone that slips into a second term doubles the tuition cost of a three competency unit course.
Six mistakes that cost time in D657
- Scope that keeps growing. Every additional journey is another thing to research, prototype, test and document.
- Research after the concept. It shows in the writing, because the findings never contradict anything.
- Testing with people who know the design. Friends who have heard about the project cannot produce first use data.
- Undocumented iteration. A final design with no version history loses the aspects about process entirely.
- Writing the report at the end. Reasons recalled months later are vague, and vagueness is scoreable.
- Starting in month four. Recruitment, testing and evaluation queues are all outside your control.
Scoping a capstone you can finish and defend
The decision that determines whether a design capstone goes well is made in the first fortnight, and it is almost always a decision to do less.
Choose one journey rather than one product. A single end to end task that a real person needs to complete gives you everything: a research question, users to talk to, a definition, concepts, a prototype with real states, and something testable. A whole product gives you a surface, and surfaces cannot be validated.
Test the scope against the aspect list before committing. For each aspect, write the sentence you expect to place in the report and ask whether the project as scoped will generate the evidence for it. If an aspect requires testing with users and you have chosen a domain where you cannot reach any, the scope is wrong regardless of how interesting the problem is, and month one is a much better time to learn that than month four.
Prefer a domain you can access over a domain you find exciting. Access means people who will speak to you within days, a context you can observe, and constraints you can discover rather than invent. Excitement without access produces a capstone built on assumptions, and assumptions are exactly what a design rubric is built to detect.
Then write the exclusions down at the start and keep them visible. Every idea that arrives later goes on a next steps list rather than into the project, and that list becomes a legitimate section of the final report rather than an admission of incompleteness.
How support works on this course
Send the rubric from your Course of Study, the capstone directions and any template. What comes back is aspect mapped and staged: help scoping to one journey, research and testing protocols, a through line table connecting findings to decisions, and a report structure that keeps the chain visible. The research, the testing and the design decisions stay yours, because a capstone is assessed on evidence you generated.
Terms are six months at a flat rate, and a capstone is the course most likely to overrun one. Starting recruitment in week one is worth more than any later effort.
Questions students ask about D657
Is D657 the same course as DES 4100?
Does the capstone need a real client?
Can you design the capstone project for me?
Where D657 sits in WGU's programs
The July 2026 catalog places this code in 1 current WGU program. 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.