How to Pass WGU D479 Task 1 Without Revisions
Student Guide to WGU D479 Task 1 User Experience Design
You opened the D479 Task 1 instructions. You read them twice. Maybe three times. And you still feel like you’re missing something — like there’s a secret version of this assignment that other students somehow got access to and you didn’t.
You’re not alone. WGU D479: User Experience Design is one of the most concept-heavy courses on the WGU IT and Business programs. Task 1 in particular trips students up because it combines UX design theory, a realistic Figma prototype, a persona profile, a full usability testing report, and accessibility documentation — all in a single submission.
The problem is that most guides online are either incomplete, outdated, or just a raw file dump with zero explanation of what actually earns a passing score.
This guide is different. Here you’ll find a section-by-section breakdown of exactly what WGU evaluators expect, why students get sent back for revisions, and how to build a submission that passes the first time.
And if you’re short on time or need expert support, Gradevia’s D479 assignment specialists are available 24/7 to help you get it done.
What Is WGU D479 Task 1?
WGU D479: User Experience Design is a project-based course built around the UX design process. Task 1 is the first of two performance assessments and covers the foundational design phase: research, persona creation, wireframing, prototyping, and usability testing.
This is not a traditional essay or multiple-choice exam. It is a design portfolio submission that demonstrates your ability to apply UX methodology to a realistic client scenario — typically involving a mobile app or web product redesign.
What You Are Expected to Submit
While WGU updates rubrics periodically, D479 Task 1 typically requires students to produce all of the following:
- A UX project timeline with defined phases and milestones
- A persona profile based on user research findings
- Low-fidelity wireframes showing early design concepts
- A high-fidelity interactive prototype (usually built in Figma)
- A usability testing plan and results report
- Accessibility documentation referencing WCAG standards
- Written UX justification for design decisions
Each of these components is evaluated against a detailed rubric. Evaluators are not grading on creativity alone — they are checking that your submission demonstrates understanding of UX principles, research methodology, and design thinking. Every section must be explicitly addressed.
WGU D479 Task 1 Rubric Explained (Section by Section)
The rubric is your blueprint. Students who fail D479 Task 1 almost always do so because they misread or ignored what individual rubric sections actually require. Below is a plain-English breakdown of the main rubric areas and what evaluators are specifically looking for.
1. UX Timeline
The timeline section asks you to document the phases of your UX project, including research, design, prototyping, and testing. This is not just a calendar — evaluators want to see that you understand the iterative nature of UX work.
What earns full credit: A timeline that clearly labels UX phases (discovery, ideation, prototyping, testing, iteration), shows logical sequencing, and includes realistic timeframes. Connecting the timeline to specific deliverables in your submission strengthens this section considerably.
What earns revisions: A vague timeline with no phase labels, a simple table of dates with no UX framing, or a timeline that doesn’t align with the rest of your submission.
2. Persona Profile
The persona is a fictional but research-informed representation of your target user. Most students know what a persona is, but many lose points because their persona is too generic or not grounded in actual research.
What earns full credit: A persona with a name, photo (even a stock illustration), demographic information, goals, frustrations, behaviors, and a short narrative that explains why this user would engage with your product. The persona should feel like a real person, not a bullet list.
What earns revisions: A persona that reads like a marketing demographic summary, no connection between the persona and usability test participants, or missing frustrations and motivations sections.
3. Low-Fidelity Wireframes
Lo-fi wireframes demonstrate your early ideation phase. These are intentionally rough and should show structural layout decisions, not visual polish. Evaluators want to see that you iterated on your designs before jumping into Figma.
What earns full credit: At least 3–5 distinct screens showing key user flows, annotation explaining design rationale, and visible evolution between lo-fi and hi-fi versions.
What earns revisions: Wireframes that look like finished mockups (skipping the lo-fi phase conceptually), missing annotation, or a single screen with no context.
4. High-Fidelity Figma Prototype
This is the centerpiece of D479 Task 1 and the section that causes the most confusion. Students are required to produce a working interactive prototype in Figma that demonstrates a complete user flow.
What earns full credit: A prototype with multiple interconnected screens, realistic UI components, interactive hotspots that simulate navigation, and design choices aligned to your persona’s needs. Include your Figma share link in the submission and make sure it is set to “viewable by anyone with the link.”
What earns revisions: A static Figma file with no interactivity, a prototype that is not navigable from start to finish, broken links, or a private Figma link that evaluators cannot access.
5. Usability Testing Plan and Results
Usability testing is a formal UX research method, and WGU evaluators take it seriously. This section requires both a plan (what you intended to test) and a results report (what you actually found).
What earns full credit: A testing plan that identifies specific tasks participants were asked to complete, the criteria for success, and participant recruitment information. The results section should document participant feedback, usability issues found, and how those issues informed your design revisions.
What earns revisions: Testing that sounds theoretical rather than conducted, results with no specific findings, or a results section that simply says all participants were satisfied with no supporting detail.
6. Accessibility Documentation
Accessibility is not an afterthought in this course. Task 1 expects you to demonstrate awareness of WCAG (Web Content Accessibility Guidelines) and explain how your prototype addresses accessibility requirements.
What earns full credit: Specific references to WCAG 2.1 principles (perceivable, operable, understandable, robust), examples of accessibility features in your prototype (color contrast, alt text equivalents, keyboard navigation considerations), and a brief written rationale.
What earns revisions: Generic statements like “my design is accessible” with no WCAG reference, or an accessibility section that is clearly copy-pasted without connection to your actual prototype.
7. UX Design Justification
Throughout your submission, evaluators expect written justification for your design decisions. This is your chance to demonstrate that you understand UX principles and applied them intentionally.
What earns full credit: Specific explanations that connect design choices to user research findings, persona goals, usability test results, or recognized UX heuristics (Nielsen’s 10 are commonly referenced). Each major design decision should have a written rationale.
What earns revisions: Vague statements like “I chose this layout because it looks clean,” or justification sections that are thin and underdeveloped relative to the rest of the submission.
Why Students Fail WGU D479 Task 1 (And How to Avoid It)
Getting sent back for revisions on D479 Task 1 is incredibly common, and almost always avoidable. Here are the top patterns that lead to a failed submission.
Mistake 1: Submitting a Static Figma File
This is the single most common reason for revisions. Students design beautiful screens in Figma and submit a link to the file — but the prototype has no actual interactivity. Evaluators cannot click through it. There is no simulated user flow.
Fix: Before submitting, open your Figma prototype in presentation mode and walk through it as if you are a user. Every primary screen should be reachable through clicks. If you get stuck, you have broken links to fix.
Mistake 2: Generic, Unresearched Personas
A persona named “Sarah, 32, Marketing Manager who likes efficiency” is not a persona. It’s a demographic sketch. Evaluators want to see that your persona came from actual research — interviews, surveys, competitive analysis, or secondary sources.
Fix: Include a brief note on your research methodology when presenting your persona. Even stating that you conducted informal interviews with 5 people in your target demographic shows the evaluator that the persona is grounded in something.
Mistake 3: Skipping the Lo-Fi Phase
Some students jump straight to Figma and then try to reverse-engineer lo-fi wireframes to put in the submission. Evaluators can usually tell. The wireframes look like downgraded versions of the final design rather than genuine early ideation.
Fix: Start with pen and paper or a whiteboard sketch before opening Figma. Take photos and include them. Real lo-fi wireframes show messy thinking — that’s the point.
Mistake 4: Fabricated or Superficial Usability Testing
Usability testing is one of the most commonly under-developed sections. Many students write a plan that sounds thorough and then produce a results section with no real data. Evaluators probe for this.
Fix: Conduct actual testing, even informally. Asking three classmates, family members, or colleagues to complete tasks in your prototype and recording their feedback is legitimate usability testing. Document what they struggled with and show how you responded.
Mistake 5: Accessibility Section With No WCAG Reference
Writing that your design “considers users with disabilities” and leaving it there will not pass. The rubric expects engagement with recognized accessibility standards.
Fix: Look up WCAG 2.1 Level AA and reference at least 2–3 specific success criteria that your design addresses. Mention color contrast ratios, text sizing, or tap target sizes if applicable to your prototype.
Mistake 6: A Private Figma Link
This one sounds obvious, but evaluators regularly receive Figma links that require a login or request access before viewing. They will not request access. The submission goes back.
Fix: Set your Figma prototype sharing settings to “Anyone with the link – can view” before you finalize your submission document.
How to Use Figma for WGU D479 Task 1
Figma is the industry-standard UX design tool and the platform WGU expects students to use for D479 Task 1. If you have never used Figma before, the learning curve is real — but it is manageable with the right starting point.
Setting Up Your Figma Account
Figma is free for individual users with limited project storage. Go to figma.com, create a free account using your email, and start a new Design file. You do not need any paid features to complete D479 Task 1.
Building Your Prototype Screens
Start with frames (not artboards) sized for your chosen platform — typically iPhone 14 (390×844) or Desktop (1440×1024). Each frame represents a screen in your user flow. Design your UI using Figma’s built-in shapes, text tools, and component library.
Do not try to design every screen at once. Map your user flow first — write out the steps a user takes to complete a core task — and build one screen per step.
Making Your Prototype Interactive
Interactivity in Figma is added through the Prototype tab on the right panel. Select an element (a button, a nav link, an icon), then drag the connection arrow to the destination frame. Set the interaction to “On Click → Navigate to.”
Test your prototype by pressing the Play button (triangle icon, top right) and clicking through it. The evaluator will do exactly this — make sure every critical path works.
Sharing Your Figma Link
Click the Share button (top right). In the share settings, change access from “Only people invited” to “Anyone with the link.” Copy the link and paste it into your submission document. Double-check that it opens correctly in an incognito browser window before submitting.
Key UX Concepts You Need to Know for D479 Task 1
D479 uses UX vocabulary throughout the rubric. If these terms are new to you, this section gives you working definitions that are sufficient for the level of engagement the rubric expects.
User Persona
A persona is a semi-fictional profile of your ideal user, built from research. It typically includes a name, photo, age, occupation, goals, frustrations, and a behavioral summary. The purpose is to keep the design team focused on real user needs rather than assumptions.
User Journey / User Flow
A user journey maps the steps a user takes to complete a task within your product, including their emotions and pain points at each stage. A user flow is more technical — it maps the decision points and screen transitions a user encounters. For D479, you will typically need both.
Wireframe vs. Prototype
A wireframe is a low-detail structural sketch that shows layout and content hierarchy without visual design. A prototype is a higher-fidelity simulation of the final product that allows interaction. In D479, you need both: lo-fi wireframes showing your early thinking, and a hi-fi Figma prototype demonstrating your final design.
Usability Testing
Usability testing involves observing real users as they attempt to complete tasks with your product. The goal is to identify friction points, confusion, and errors in the design before launch. For D479, you need a testing plan (what you will test and how) and a results report (what you found and what you changed).
WCAG Accessibility Standards
WCAG (Web Content Accessibility Guidelines) is an internationally recognized framework for making digital products accessible to people with disabilities. WCAG 2.1 organizes requirements around four principles: Perceivable, Operable, Understandable, and Robust. For D479, referencing specific success criteria (such as 1.4.3 Contrast Minimum or 2.5.5 Target Size) will strengthen your accessibility section.
Heuristic Evaluation
Heuristic evaluation involves reviewing a design against a set of recognized usability principles — most commonly Jakob Nielsen’s 10 Usability Heuristics. These include principles like “Visibility of system status,” “Error prevention,” and “Recognition rather than recall.” Referencing heuristics in your UX justification demonstrates evaluator-level understanding.
How Long Does WGU D479 Task 1 Take?
This is one of the most searched questions about D479, and the honest answer is: it depends on your prior UX experience and how familiar you are with Figma.
| Student Background | Estimated Time for Task 1 |
| No UX or Figma experience | 25–40 hours |
| Some design experience, new to Figma | 15–25 hours |
| Prior UX coursework or professional experience | 10–18 hours |
The Figma prototype typically consumes the most time, especially for students who are new to the tool. Budget at least 5–8 hours for the prototype alone.
Working adults with full-time jobs often need 2–3 weeks to complete Task 1 comfortably. If you are approaching your term deadline, prioritize completing the rubric sections in order of complexity: prototype first, then usability testing, then supporting documentation.
Step-by-Step: How to Complete WGU D479 Task 1
Use this sequence to work through D479 Task 1 efficiently and avoid the most common errors.
Step 1: Read the Rubric Before You Start
Download the official D479 Task 1 rubric from your WGU student portal and read it in full before beginning any design work. Highlight the exact language evaluators use for each section. This language should appear in your written submission.
Step 2: Choose Your Product Scenario
D479 Task 1 typically provides a client scenario or allows you to define your own. Choose a product that is specific enough to design for but not so complex that you create unnecessary scope. A mobile app for a local service (scheduling, ordering, booking) is an ideal scope.
Step 3: Define Your Persona
Based on your chosen scenario, define who your primary user is. Conduct at least informal research: look at app store reviews for similar products, read Reddit threads from your target audience, or interview 2–3 people. Use what you learn to build a persona grounded in real data.
Step 4: Map Your User Flow
Identify the core task your user needs to complete — for example, booking a service, finding information, or completing a transaction. Map the steps they will take and the screens they will encounter. This becomes the backbone of your wireframes and prototype.
Step 5: Sketch Lo-Fi Wireframes
Draw low-fidelity wireframes on paper or in a free tool like Balsamiq or even Figma using basic shapes. Focus on layout and content hierarchy, not visual design. Create at least one wireframe per major screen in your user flow.
Step 6: Build Your Figma Prototype
Using your wireframes as a guide, build your high-fidelity prototype in Figma. Add realistic UI components, color, typography, and imagery. Then connect all screens with interactive hotspots using the Prototype panel. Test it thoroughly before moving on.
Step 7: Conduct Usability Testing
Recruit 3–5 participants who roughly match your persona profile. Give them specific tasks to complete in your Figma prototype (run it in presentation mode on your screen and let them navigate). Record their behavior and note where they hesitate, misclick, or express confusion.
Step 8: Document Accessibility
Review your prototype against WCAG 2.1 standards. Use a color contrast checker (Figma has plugins, or use WebAIM’s free tool) to verify your text meets Level AA contrast ratios. Document 2–3 specific WCAG success criteria your design addresses.
Step 9: Write Your UX Justification
For each major section, write 1–2 paragraphs explaining why you made the design decisions you made. Reference your persona, usability test findings, or UX heuristics. This is the glue that ties your submission together.
Step 10: Compile and Review Your Submission
Assemble all components into your submission document following WGU’s formatting requirements. Verify your Figma link is public and working. Read through the rubric one final time and confirm every criterion is addressed.
💡 Want an expert to review your D479 Task 1 before submission? Gradevia offers pre-submission reviews with revision guarantees.
Frequently Asked Questions: WGU D479 Task 1
Is WGU D479 hard?
D479 is one of the more demanding courses in WGU’s IT and Business programs, primarily because it is project-based rather than knowledge-based. There is no exam to pass by memorizing content — you must produce a substantial UX design portfolio. Students with no prior design or Figma experience find the learning curve steep. However, the course is completable for students who engage with the material systematically.
How many pages should WGU D479 Task 1 be?
There is no strict page requirement for D479 Task 1, but thorough submissions typically run 15–25 pages including wireframe images, the persona profile, and written justification sections. The Figma prototype link supplements but does not replace the written documentation.
Can I use Figma for WGU D479 Task 1?
Yes. Figma is the recommended tool for WGU D479 Task 1. It is free for individual use, browser-based (no install required), and industry-standard for UX design. WGU evaluators are familiar with Figma and expect to receive a Figma prototype link as part of your submission.
What happens if I fail WGU D479 Task 1?
If your Task 1 submission does not meet rubric requirements, evaluators will send it back with written feedback identifying the specific sections that need revision. You can resubmit. There is no limit on the number of resubmissions, but revisions consume your time and can create pressure as your term deadline approaches.
How do I create a UX persona for D479?
A D479 persona should include: a name and photo (use a free stock image), age, occupation, and location; a short backstory describing the user’s context; 3–5 goals related to your product scenario; 3–5 frustrations or pain points; and a behavioral summary. The persona should feel specific and human. Generic templates from the internet will not score well.
What is usability testing in D479?
Usability testing in D479 refers to a formal UX research method in which you observe real users interacting with your prototype to identify usability problems. For Task 1, you need both a testing plan (participant criteria, tasks to be tested, success metrics) and a results report (actual findings, patterns observed, and design changes made in response).
How do I share my Figma prototype with WGU?
In your Figma file, click Share (top right corner), then change the access setting to “Anyone with the link – can view.” Copy the link and include it in your submission document. Always test the link in an incognito window before submitting to confirm access works without logging in.
Do I need to reference sources in D479 Task 1?
Yes. While D479 is a design portfolio assignment, evaluators expect academic grounding. Reference UX frameworks (Nielsen’s heuristics), accessibility standards (WCAG 2.1), and any secondary research sources you used to develop your persona. APA 7 format is standard across WGU performance assessments.
How Gradevia Helps WGU D479 Students
Gradevia is an academic assistance service built specifically for WGU and online learning platform students. Our specialists understand the WGU performance assessment format, the evaluator rubric expectations, and the specific challenges of project-based courses like D479.
What We Offer for D479 Task 1
- Prototype guidance and Figma review
- Persona development support
- Usability test planning and results documentation
- Rubric walkthrough and gap analysis before submission
- Full Task 1 drafting and customization
- Pre-submission review with written feedback
- Revision support if your submission is returned
Why Students Choose Gradevia
We work exclusively with WGU and online program students. Our team includes former WGU coursework specialists and UX professionals who understand both the academic requirements and the design standards evaluators expect. Every engagement is confidential, original, and built around your specific submission.
We offer transparent pricing, a preview before final delivery, and free revisions if your submission is returned by WGU evaluators.
Ready to Pass D479 Task 1 the First Time?
D479 Task 1 is a substantial project, but it is absolutely passable — even for students with no prior UX experience — when you understand what the rubric actually requires and approach the submission with a clear plan.
Use this guide as your reference throughout the process. Walk through every rubric section systematically. Test your Figma prototype before you submit. Conduct real usability testing with real participants. Reference WCAG explicitly. Write UX justification for every major design decision.
And if you need expert support at any stage — from building the prototype to reviewing the final document — Gradevia’s D479 specialists are available now.
