D657 is the capstone of the Bachelor of Science in User Experience Design at Western Governors University.
WGU describes it as a course that gives students real-world applications to prepare for the product and experience design industry, by integrating the skills gained throughout the program while working with an organization on a design project.
Because it comes at the end of the degree, the course feels different from earlier ones. Instead of one narrow skill, you are expected to show research, design judgment, communication and professional self-presentation together.
Many students find the difficulty is less the design itself than documenting decisions clearly and telling a credible story about their own work.
Course at a Glance
| Item | Details |
|---|---|
| University | Western Governors University (WGU) |
| Course | D657, Design Applied Learning Capstone |
| Level | Undergraduate capstone |
| Program | B.S. User Experience Design |
| Competency units | 3 CUs, listed in the final term of the standard path (2024 program guide) |
| Typical work | An applied design project with an organization, plus portfolio and career materials |
What D657 Covers
WGU's program guide lists four competency statements for the course. In plain language they ask you to do the following:
| Competency (summarized) | What it means in practice |
|---|---|
| Agree a personalized course plan | Review your course planning tool report with your instructor and set a plan together |
| Use experiential learning to build career skills | Work on a real design project that builds the expertise you need for your chosen role |
| Narrate your educational and professional story | Explain your accomplishments and relate your skills to a professional role |
| Curate artifacts | Choose portfolio pieces and explain how each shows your qualifications |
The official description also names the power skills the capstone reinforces: giving, receiving and incorporating feedback, empathy and inclusive collaboration, planning within ambiguity and navigating complex problems.
Key Ideas Behind a Strong Capstone
A Case Study Is an Argument
A portfolio case study should show why you made each decision, not only what you made. Reviewers look for the problem, who it affected, the evidence you gathered, the options you rejected and what changed as a result.
Example: Instead of writing "I redesigned the booking page", write "Customers abandoned booking at the payment step, so I tested two layouts with five users, found the price summary was hidden on small screens, and moved it above the form." The second version shows evidence and reasoning in two sentences.
Working Within Ambiguity
Organization projects rarely arrive with a perfect brief. Writing down your assumptions, the questions you asked and how you narrowed the scope shows the planning-within-ambiguity skill that the course names.
Curating Artifacts
Quality beats quantity. Three well-explained pieces, each linked to a skill an employer wants, usually communicate more than a gallery of ten unexplained screens.
Building the Portfolio and Career Story
Two of the four competencies are about presenting yourself, so treat the portfolio as graded work, not an afterthought. Employers reading a design portfolio usually want three things: a clear problem, evidence of your process, and a sense of how you work with others.
| Portfolio element | What to include | Common gap |
|---|---|---|
| Project summary | Problem, your role, timeline, outcome | Role left vague in team work |
| Process evidence | Research notes, sketches, prototypes, test findings | Only polished final screens |
| Reflection | What you would change and what you learned | No honest limitations |
| Personal brand | Short bio, target role, consistent tone | Generic claims |
Be honest about what you did yourself. Describing a team's work as your own, or inventing results, damages credibility with both evaluators and employers.
Typical Work and How to Approach It
The exact tasks and rubric are in your course site, so follow those first. Capstone courses of this kind typically involve work like the following.
| Type of work | What it tests | How to approach it |
|---|---|---|
| Applied design project | Integrating research, design and testing | Agree scope early and keep a dated log of decisions |
| Project documentation | Clear reasoning and evidence | Link each design choice to user evidence |
| Portfolio curation | Selecting and explaining artifacts | Pair each piece with a short note on the skill it shows |
| Career narrative | Professional self-presentation | Match your story to one target role |
Where Students Get Stuck
- Showing the output but not the thinking. Screens alone do not demonstrate research or judgment. Add the problem, the evidence and the trade-offs.
- Waiting on the organization. Delays in feedback or access can stall a project. Raise questions early and keep a record of contact.
- Scope creep. A project that is too big cannot be finished well. Define what is in and out of scope in writing.
- A generic personal brand. A statement that fits any designer fits none. Tie your story to a specific role and the evidence you have.
Study Tips for D657
- Start the course planning tool conversation with your instructor early, since the plan sets your pace.
- Keep a running project journal from day one: decisions, screenshots, feedback received and what you changed.
- Draft your career narrative before the project ends, then refine it using what the project taught you.
- Check each rubric line against your documentation before you submit.
- Ask your instructor for feedback on an outline rather than waiting for a finished draft.
Final Checklist Before You Submit
- Every rubric line has a labeled place in your documentation.
- Each portfolio piece states your exact role and the skill it shows.
- Decisions are linked to research or testing evidence.
- Feedback you received is recorded, with what you changed in response.
- Your career narrative names one target role and supports it with examples.
- Images and text are free of confidential client information unless permission was given.
Read the whole submission once as an employer would, then once as an evaluator with the rubric. Gaps usually show up in the second read.
How We Help with D657
Send the task instructions, your rubric, any notes from the organization project and your draft. A writer with design and communication experience can edit your case study, explain how to structure it, or prepare a model example showing how a strong write-up is organized. See also our capstone help guide for general planning advice.
GradeEssays is independent and not affiliated with WGU. Our work is a study and reference aid: use it to learn, then complete and submit your own work under WGU's academic integrity policy. We do not log in to course portals. Orders are written from scratch, include free revisions within the scope of your original request, and are refunded in full if late.
Get Your D657 Case Study into Shape
Share your project notes, task instructions and feedback. We help you plan, edit and sharpen the write-up so your own work comes across clearly.
Start My D657 HelpFree revisions · Full refund if late · Written from scratch for your order
Frequently Asked Questions
It is the Design Applied Learning Capstone in the B.S. User Experience Design program, where students apply their skills on a design project with an organization.
WGU's description says students work with an organization on a design project. Your task instructions explain how that organization is found and what is expected.
Yes. WGU's description says students refine their portfolios and personal brand and plan strategically for their career.
The 2024 program guide lists 3 CUs, placed in the last term of the standard path. Check your own degree plan for current details.
Usually it lists deliverables without evidence. Reviewers want the problem, the research, the decisions and the outcome.
No. We help you plan, edit and understand the work, but the project and submission must be your own.