WGU D652: Design Applications

What D652 Design Applications Really Is

WGU D652: Design Applications is a hands-on course in the Bachelor of Science, User Experience Design program in WGU's School of Business. It builds directly on the earlier Foundations of Design course, so you arrive already knowing how to research users and frame a design problem. In D652 you move from thinking about design to actually making it: you translate a concept into storyboards, then into a digital wireframe, and finally into a working low-fidelity prototype using industry-standard visual design tools. The deliverables you produce are meant to be real portfolio artifacts, not throwaway coursework.

Direct answer: D652 is passed by completing a performance assessment, not a multiple-choice exam. Read the task instructions and rubric line by line before you design anything, build your storyboard, wireframe, and low-fidelity prototype so each rubric point is obvious to the evaluator, and revise against that rubric before you submit. There is no cramming here; the work is the test.

You will take this course as part of the UX Design degree, usually around the middle of the program once foundational design and research courses are behind you. It matters because it is where abstract user-centered design principles finally become something you can click through and show an employer. The skills you practice here, wireframing, prototyping, and defending your design decisions, are the same ones you will be asked about in UX interviews.

Topics the Assessment Covers

Because D652 is project-based, the "topics" are really the competencies your submitted work must demonstrate. Based on WGU's official course description, expect to be evaluated on your ability to:

• Use storyboards to turn a design concept into a visual sequence or narrative.
• Create a digital wireframe using simple shapes to lay out structure and hierarchy.
• Build a low-fidelity digital prototype with industry-standard visual design tools.
• Apply user-centered design principles, including balance, thematic consistency, and visual aesthetics.
• Account for interactivity and usability so the prototype behaves the way a real user would expect.
• Weigh ethical considerations in your design choices.

The through-line is user-centered design: every visual and functional decision should trace back to what an actual person needs from the product. Evaluators are looking for that reasoning as much as for a polished screen.

How Hard It Is and How Long It Takes

Difficulty in D652 is less about intellectual density and more about craft and tool fluency. If you are comfortable in a design tool and you read rubrics carefully, many students report it feels approachable and even enjoyable compared to heavier theory courses. The friction usually comes from learning a new prototyping tool and from matching a creative deliverable to an exact rubric, two things that reward patience over speed.

Time to completion varies widely because it depends on your prior design experience and how many revision cycles your submission needs. Many students report finishing performance-assessment courses like this one within a few weeks of steady effort, and some move faster when they already know their tool. Rather than chasing someone else's timeline, budget enough time for at least one full revision after your first submission, since evaluator feedback is a normal part of the process, not a sign of failure.

A Study Plan That Fits a Project Course

The usual exam tactics still help here, but you apply them to producing a deliverable rather than memorizing facts. Try this sequence:

• Reverse-engineer the rubric first. Before opening a design tool, copy every rubric row into a checklist. Active recall works here as "can I point to where my prototype satisfies this exact line?" If you cannot, you are not done.
• Pick one tool and commit. Learn a single industry-standard visual design tool well rather than sampling three. Spread short, spaced practice sessions across several days so the interface becomes muscle memory instead of a distraction on submission day.
• Storyboard on paper before you go digital. Sketching the flow first is fast, cheap iteration. It keeps you from polishing pixels on a layout you will scrap.
• Prototype for the user, not for beauty. A low-fidelity prototype is supposed to look rough. Spend your energy on structure, interactivity, and usability, and let the fidelity stay low on purpose.
• Practice-test your own work. Click through your prototype as if you were a first-time user, or hand it to a friend. The confusion they hit is exactly what an evaluator will flag.
• Write your design rationale. Many rubric points reward explaining why you made a choice. Draft short justifications tied to user-centered principles as you build, not the night before you submit.

Mistakes That Cost Students Time

A few patterns show up again and again in this course, and all of them are avoidable:

• Designing before reading the rubric. Building a beautiful prototype that misses required elements guarantees a revision. The rubric is the assignment.
• Over-polishing a low-fidelity prototype. Adding real colors, final copy, and pixel-perfect styling wastes hours and can actually work against the "low-fidelity" requirement.
• Skipping the storyboard. Jumping straight to wireframes often produces a layout with no clear user flow, which then has to be rebuilt.
• Ignoring the "why." Submitting artifacts without explaining how they serve users or reflect ethical considerations leaves easy rubric points on the table.
• Treating revision as failure. Evaluator feedback is normal. Read it carefully, address each item specifically, and resubmit rather than starting over from scratch.

If you are strengthening your broader business and design judgment alongside this course, guides like D081 Innovative and Strategic Thinking and D175 Consumer Behavior pair naturally with the user-centered mindset D652 asks for, and C717 Business Ethics reinforces the ethical-considerations thread that appears in this course.

D652 Readiness Checklist

Before you submit, work through these self-checks. If you can honestly answer yes to all of them, you are ready.

• Can you restate each rubric requirement in your own words and point to where your work meets it?
• Can you produce a storyboard that shows a clear sequence or user flow for your concept?
• Can you build a digital wireframe using simple shapes to establish layout and hierarchy?
• Can you create a low-fidelity prototype in your chosen tool without fighting the interface?
• Can you demonstrate interactivity so the prototype responds the way a user expects?
• Can you explain how balance, consistency, and visual aesthetics show up in your design?
• Can you name at least one ethical consideration your design accounts for?
• Can you click through your own prototype and confirm a new user would not get lost?

FAQ

Is D652 an OA or a PA?

D652 is assessed by a performance assessment. You submit design deliverables, typically a storyboard, wireframe, and low-fidelity prototype, that are evaluated against a rubric. There is no proctored multiple-choice exam to sit for this course.

How many competency units is D652 worth?

According to WGU's official User Experience Design program guidebook, Design Applications is worth 3 competency units. Because it is project-based, plan your time around building and revising deliverables rather than around study hours for a test.

What tools do I need for D652?

The course calls for industry-standard visual design tools to build wireframes and low-fidelity prototypes. WGU provides guidance on approved software, so confirm the current tool in your course materials before you buy or install anything, and focus on learning one tool well.

Do I need to be an artist to pass?

No. D652 rewards clear structure, usability, and sound user-centered reasoning more than artistic flourish. A low-fidelity prototype is meant to look simple, so effective communication of your design beats decorative polish.

What if my submission comes back for revision?

That is a normal part of WGU performance assessments. Read the evaluator's comments closely, address each flagged item specifically, and resubmit. Revisions are feedback, not a verdict, and most students who respond carefully clear the task.

How does D652 fit into the UX Design degree?

It is a core design course in WGU's School of Business B.S. in User Experience Design, building on Foundations of Design and feeding into later prototyping and iteration courses. The artifacts you create are designed to go straight into your professional portfolio.

For more study guides, browse the School of Business hub or the full index of WGU course guides. You can also confirm current course details on WGU's official User Experience Design program page.